Product Management Series II of agile development: Product Version Planning

This is the second article in the agile development product management series. (Preface and set up iteration goals, product version planning, product user group planning, new product R & D, prediction meetings, product servant, product owner team, and product line management)

This article is an old article, formerly known as "no change during iteration" and agile development product version planning. Because it conforms to the content of this series, it is modified and re-arranged.

No changes during iteration?

Support school said: Yes. If it changes frequently, how can we develop it.

The opposition said: No, agile development cannot come up to confirm the demand. What is needed is to gradually understand the demand in development. How can it remain unchanged.

This problem is only available at the development level. Let's standProduct Version PlanningIn height.

Product Version planning based on business objectives

What functions should be provided in the next product version (or next iteration? What are the most important functions? What are the most basic functions? What functions can be implemented currently? Functions that have been clarified?

These perspectives are based on technical activities rather than market goals and all have their limitations.

In fact,The version of each product is a step-by-step move for enterprises: at a certain time, some features are released to meet certain needs, obtain some customers, defeat some competitors, and replace some products.

If you agree with thisAs early as the product version planning, we should confirm which functions should be included in this version, instead of being confirmed in the iteration plan meeting or iteration, and will not change in the middle of the iteration..

In this case, "no change during the iteration" refers to: "It should not be until iterative development has started, and it is not clear what functions should be developed" (what problem), rather: "The requirements should be clarified before iteration, so don't change them once the development is done" (how problem ).

Product Version planning steps

Product initiation ------------------------------------------- at this time, we will roughly plan the way out line chart, how far, how long, and where to go

V1.0 --------------------------------------- at this time, define the functions required for this version (not necessarily the granularity of the story point)

Sprint1 plan will be --------------------------------- at this time, the granularity of the story points will be reached, and the technical point of view will be considered after what can be done first

Daily Work ----------------------------- what it looks like at any time, it can be changed at any time, but basically it won't be thrown away or replaced with any function.

Sprint2 project meeting

......

Sprint release ----------------------- at this time, regardless of the Technical order, all the functions of V1.0 have been completed.

V2.0 V2.0 ------------------------------------- adjust the product roadmap based on market feedback

V3.0 --------------------------------------- continue

From this point, the goal of Agile Product Version planning is the same as the original intention of setting iteration goals:Balance between "pre-planning to prevent rework" and "Random Response to prevent too much useless thinking" to reduce waste.

 

 

Click to download the free agile development textbook: Martian agile development manual