Agile uses the Product Backlog to manage requirements. The Product Backlog is a list of requirements sorted by their business value. High-priority requirements are at the top of the Backlog. Product Backlog is a progressively detailed list, it has 4 main features, called DEEP:
- Detailed Appropriate level of detail, high-priority requirements are more detailed, and low-priority requirements are more granular
- Emergent emerges, the demand emerges slowly, gradually detailed
- Estimated Estimated
- Prioritized/ Ordered Ordered according to business value
In the product Backlog, the main form of requirement is the user story. A user story is a short description of a requirement from the user's point of view. User stories are the best way to shift the team's focus from describing and writing functional requirements to discussing requirements.
Usually we will create these lists in the product backlog kanban: "user story pool, user story - to be sorted out, user story - sorted out, user story - in progress, user story - completed", through the list flow, let The team intuitively understands the prioritization and planning of requirements. Then add requirement cards on each list, one card for each requirement.
Requirement planning to iteration Kanban for iteration
Before the start of each iteration, we need to plan the user stories that have been sorted out and have the highest priority in the iteration Kanban, so as to prepare the content that needs to be completed in the iteration.
Click the "Sprint Planning" button in the Kanban, and drag the user stories planned to be done in "Sprint1" to the "Sprint1" Kanban.
Note: There will be a blue planning mark in the upper left corner of the planned card.
The iterative kanban is shown in the figure below:
Defect Management and Planning:
Defect management usually focuses on the following aspects:
1. Defect processing speed
2. Status of defect handling
3. Distribution of defects
4. The cause of the defect
As shown in the figure below, we divide the status of the defect into four states: the latest submission to be confirmed, confirmed to be repaired, repairing, and completed. Through the circulation of the list, the team can intuitively understand the progress and status of the defect . Then add defect cards to each list, one card for each defect.
The following figure shows a defect example kanban:
Defects are planned to be fixed in the iteration kanban
Usually, the defects of the current iteration are recommended to be placed on the iteration kanban of the current iteration, and repaired before the end of the iteration.
"Defect Kanban" usually contains defects left after release, defects reported by customers, etc.
During the Sprint sprint, we not only need to make relevant user stories, but also need to solve the defects that arise during this process. Therefore, we can plan the defects on the defect kanban into the Sprint when planning the Sprint.
Click "sprint planning" and drag the defects that have been determined to be fixed to the corresponding iteration Kanban.
To sum up, Leangoo is a professional agile development management tool that provides end-to-end agile R&D management solutions, covering agile requirements management, iteration management, defect management, task collaboration, progress tracking, statistical measurement, etc., visualized through Kanban Not only is defect management convenient and fast, but it also helps us discover problems and bottlenecks and optimize team efficiency.