Rookie Scrum Agile Practice Series (iii) planning of organizational---Functional architecture of user stories

Using Scrum Agile Project management method for product development, when the large-scale product development, user stories are more, it is necessary to take certain methods to organize and manage user stories, so that the management of their categories, organized only clear. Often we use "functional architecture" to classify the user stories in a hierarchical hierarchy.

First, the planning level

Following the scrum Agile Project Management theory, the project can be divided into three large levels, which are the top layer, supporting multiple products at the same time; the second layer is the functional architecture (Features) layer, which can plan the entire skeleton (functional blueprint) of the SOFTWARE product; The third layer is the user story layer, Categorize user stories into functional architectures. Project managers and developers can see the overall situation of the whole project at a glance, quickly locate user stories and their associated tasks, test cases, and so on. As shown in the following:

Second, the scrum product layer

The product layer includes one or more products that can be carried out concurrently and tracked in parallel. The basic information for each product includes the product name, product number, start time, end time, project team member, product available work, project assigned work, project total working day, where the product available work and product total working days are generated by the system automatically, and the product assigned work is accumulated by the estimated hours of all user stories for the product.

Product Available hours = number of project Groups * Product Total business days * 8

III. Scrum Functional architecture Layer

Today's product size, a few dozens of user stories, many hundreds of thousands of user stories, so many user stories how to manage is a big problem. With an infinitely graded functional architecture, the user stories are grouped under the function, and project-related people can quickly locate user stories.

Each feature architecture item also has the ability to track progress, and the product manager is able to track the development completion of the feature, which is the sum of the progress of all user stories under that feature.

Iv. Scrum User Story layer

User stories are a description of the functional points that are valuable to users, systems, or software purchasers, simply described as user needs, with a few sentences of the user's everyday language, the estimated workload can be completed in an iterative plan, and if the estimated workload is too large, it can be split into smaller user stories.

Each user story contains multiple related tasks, changes, defects (bugs), test cases, and test histories, and through tasks to schedule development work for each project member, "Change" records changes to the user story, "bug" records the bugs and their handling of the user story, " The test case "contains the points that the user story needs to be tested and their steps, and" Test history "records the test and test results of the user story experience.

V. Scrum Agile Project Management functional Architecture diagram example

In addition, if you do not understand or need to communicate scrum knowledge and opinions, please add my personal public number: Scrum master, or scan code to join:

Rookie Scrum Agile Practice Series (iii) planning of organizational---Functional architecture of user stories