Some best practices, upcoming product listings

The list of measures that can be taken is a productThe upcoming Product list corresponds to the project backlog, also translated as "Product-do list", which is problematic for harmless products and a list of upcoming developments. In Scrum guide, the product backlog is a sorted list of what is needed for all products and the only source of changes in product requirements.

The product owner is responsible for the content, availability, and priority of the product backlog list. The Product Backlog list is always incomplete, and the initial version number simply lists the most initial and well-known requirements. The product to-do list evolves based on changes in the product and development environment. The to-do list is dynamic, and it often changes to identify what is necessary to make the product reasonable, competitive, and practical. Only the product exists. The Product Backlog list exists.

The product to-do list lists all of the features, functions, requirements, improvements, and fixes for future releases of the product.

Product to-do list entries include descriptive narrative, order, and estimation features.

What's in the product to-dos list?

Product to-do list another translation product to-do list shows the backlog of items to be included in the product backlog.

The To-do list includes all of the features, functions, requirements, improvements, and fixes for future product changes.

Common to-dos are expressed in the form of user stories.

How do I maintain a product to-dos list?

In Scrum guide, the product backlog is usually sorted by value, risk, priority, and necessity.

The top Product Backlog list entry needs to be developed immediately.

The higher the sort, the more urgent the product backlog is, the more careful it is. And the more consistent the opinion of its value. The higher the order, the more clear and detailed the Product backlog list entry is than the sort below.

More accurate estimates can be made based on clearer content and more detailed information. The lower the priority level. The less detail information.

The Product Backlog list entries that the development team will develop in the next sprint are fine-grained and have been decomposed. Therefore, any entry can be "completed" within the Sprint's time box. The Product Backlog list entries that the development team can "complete" in a sprint are considered "ready" or "operational" and can be selected during the Sprint planning meeting. with the use of products, the acquisition of value and market feedback. The product backlog becomes a larger, more exhaustive list. Because demand will never stop changing. So the product backlog is a constantly updated artifact.

Changes in business requirements, market conditions, and technology can cause changes in the product backlog.

A number of Scrum teams often develop a product together. But the product backlog that describes the next product development work can only have one.

Then it is necessary to use the properties that group the product backlog list entries. "Product representative list Optimization (grooming)" is a move to add details, estimate and sort items. This is an ongoing process in which the product owner and the development team collaborate to discuss the details of the Product representative list entry. When the Product Backlog list is optimized. Entries will be reviewed and modified. However, the product owner is able to update the product backlog list entries or discretionary decisions at any time.

What are the difficulties with the product backlog list for single-column tables? Judging from the above words, the product to-do list that the Scrum guide says is a list. Through constant maintenance. The backlog at the top is analyzed and split into small enough granularity for development in a sprint. Such a procedure has two major drawbacks such as the following:1, an earlier backlog may break down into multiple to-dos, and its associated information is difficult to maintain2, the information collected earlier may be distorted after multiple passes in the optimization and refinement process
Tree-shaped product to-do list more expressivein order to overcome the shortcomings of the single table, the use of a tree-shaped product to-do list, common patterns such as the following:1 Original demand or epic story a1.1 User Stories or use cases A11.2 User Stories or use cases A2 2 original demand or Epic story B 2.1 User Stories or use cases B1 2.2 User stories or use cases B1 2.2.1 More detailed user stories B11 2.2.2 More detailed user stories B12
In this way, the original information and relations are maintained.
The second way is a multi-list of associated relationships, such as the following

First Level list (for example, original demand, Epic story)	Second Level list (for example, user stories, demand use cases, etc.)	Third Level list (for example, interface details)
Epic1	Userstory1 Userstory2 Userstory3	Details corresponding to the Userstory1 Details corresponding to the Userstory2 Details corresponding to the Userstory3
Epic2	Userstory4 Userstory5 Userstory6	...
......	...

The table changes in the blog is not easy, general. In an agile development environment, the third-level list is not used.

Obviously, a multi-list of association relationships can also be converted into a tree structure. Nowadays, many tools can help show different forms to facilitate the habits of each person.long-term operations product Backlog list no longer only includes to- dosHow do I handle an already completed backlog? There are two common ways of doing this:1, removed from the product to-do list, but can not really throw away, for the long-term operation of the product, the transfer of its organization to reflect the latest product requirements of the document, the common use of wikis as a carrier. 2, remain in the product to-do list, the status and version number management.
The 2nd approach does not need to be transferred, using an item-based management tool (such as Vsts,jira,redmine. Polarion,mantis,sharepoint, etc.) can easily manage the status and version number. When an already completed item needs to be changed to enhance the upgrade, simply retrieve the original entry, then make the changes, and then set its publication target version number to the latest version number. Compared to the 1th method, there is no need to move, and the 1th method. when you encounter changes to enhance the upgrade. Retrieve the latest information from the document and then write the to-do item to the Product backlog list, based on the latest situation. When you are done. Move back to the document from the Product Backlog list.

with the development of tools. The 2nd approach is gradually becoming the majority choice, in such cases. The literal meaning of the product backlog is no longer appropriate. It may be more appropriate to change the name to a product demand list. or the product to-do list is part of the product requirements list, a filter for the list of product requirements, and a "product to-do List" to query for unfinished backlog items.
References1,scrum Guide Chinese version https://www.scrum.org/Scrum-Guide
[The text on this page agrees in the Creative Commons Attribution-same way to share the 3.0 agreement and the GNU Free Documentation License for changes and re-use. ]

Some best practices, upcoming product listings