How do the product manager for iteration planning version, and sometimes there will always produce powerlessness, or is difficult to determine the plan down, either go on to develop a good plan can not be executed because the issue is very complicated. Early in the project, we lack a global concept and overall grasp of the product, difficult to unify the views of the interior; furthermore, do not have a complete user experience or value stream-oriented, can not reasonably be customized for each iteration of the incremental deliverables.
Before we talked about how to build a roadmap way, the road map can give PO overall direction and guidance of the team, but the more specific content, require the user to map story, through horizontal and vertical frame of the task, a complete product showcase come out. Then, through the story point estimate and priority ranking to determine the version of the iteration plan.
Iterative version is actually a road map, which shows the expected date of completion of these features and functions to be implemented. Usually follow the team at their own pace, some a a Release Sprint, Sprint and some will be more classified as a Release in, as shown below. There are released immediately after the completion of each function, which is also commonly referred to as continuous deployment or continuous delivery. Product development according to the policy, it can be driven by function, once the target is expected to develop a functional module to publish; or is driven by a date, and after a predetermined inspection point on the release.
Specifically, how to do it? We can divide this step to complete.
1. Create a user story map
Together with the customer, clarify the role of the user of the product, and write things down as much as possible the user's behavior, and the behavior of each user needs to do, from left to right and then follow user behavior storytelling. When you can think of their own story maps are put up, and then merge changes in the story, the story will eventually form a two-dimensional map.
2. Construction product release roadmap
The whole story map will contain a lot of story points, but at a certain time to complete all the functions is not possible, the team should consider the commercial value, the market situation, the difficulty of implementing aspects and other factors, determine what the next few published, and each Posted expected to produce results.
3. Rapid estimates
After a user story is created, we can quickly estimate for all tasks map in order to be able to know that we want to publish the entire Release desired product probably workload. Unlike the Sprint estimates of the story, where coarser and more quickly, the story can point or T-shirt size (S, M, L, XL) to develop standards our estimates.
4. Develop Release Plan
After the work is completed in front of our overall product development time and there will be a rough estimate, it can be designed to Release plan. We can according to our estimates, which features needed to design a Release issued and includes several Sprints, Release program example below shows.
The story then sort each Sprint put back in, you can use some iteration planning online tool, as shown to the right of the contents of the Product Backlog, Sprint freedom drag to the left in accordance with the priorities and values.
5. Product Release Calendar
After the planning meeting to finalize the details, make any final adjustments, and then shared with all stakeholders in the product release calendar.
Worktile official website: https://worktile.com/
Author: kaya
article first appeared in " Worktile official blog ", please indicate the source.
