"No changes during iteration" and agile development product version Planning

Author: Chen Yong

Source: blog.csdn.net/cheny_com

 

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 look at this issue from the perspective of Product Version planning.

 

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 this, you should confirm which features should be included in this version as early as the product version planning, rather than in iteration plan meetings or iterations. 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 ).

 

Summary:

 

Product ----------------------------------------- at this time, we will roughly plan the line chart of the way out, how far it will take, and where it will go.

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

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

Daily Work ------------------------------- what it looks like and can be changed at any time, but it will not be discarded or changed.

Sprint2

......

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

 

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