Agile development with tools-8

I have a rough idea about demand management, but I guess you will ask, after talking so much about it, how does it feel like it has nothing to do with agility? Well, as I have said before, although agile development is "AGILE", it will not bypass the entire software development process, just as Sun Wukong cannot escape. As a very important part of software development, we are absolutely unable to get around, and even super agile development is not available, so I have to give it a closer look.

Now, with the knowledge of demand management, I can really talk about the point of direct association with agility. As mentioned before, scrum is actually an incremental iteration, that is, to implement some functions in each iteration cycle, and there will be a usable build. After several iteration cycles, the functions are much completed, the product is almost complete. The requirement management, that is, the management of function points, is just mentioned above. Even if the function points are available, we will start to explain how to implement the function points in each iteration.

Our company's product manager, Project Manager, designers and sales staff are constantly communicating with customers, and then they are constantly researching and finally designed many functions, but to be honest, there are no limits on functions, and new functions may appear every day. However, a product is limited. At least the time is limited, it is impossible for you to implement unlimited functions at this limited time, and you need to take into account the future. What will happen in the next version if all the functions are completed? Therefore, for each version of the product, we always need to select some functional points that need to be done. In scrum, this is called product backlog.Product orderBut I think it isProduct Function poolIt may be better. This pool is filled with the functions required for this version of the product. If you have done one, there will be one missing, and the product will be ready for release. Of course, agile development advocates changes. Therefore, you can add new functions to this pool anytime and anywhere during the development process, or modify the original functions, you can even remove a feature and put it in the next version. These can be changed according to actual needs, so they are called agile. If all functions are defined in the waterfall model, they cannot be changed during development.

For product backlog (product function pool), devspec is implemented in this way. You can create a folder on the product function tree to store the features required by each product, then, put the function points that need to be completed in the current version into the product backlog. The product backlog is called the "list to be developed" in devspec, which is also concise, however, I still like [product function pool ]. To deepen your impression, let's talk about this product backlog.