Transfer: https: //www.leangoo.com/9229.html
The traditional waterfall operating mode using the detailed requirements specification to express their needs, the needs of persons responsible for doing research needs, the preparation of detailed fact sheets needs based on research carried out needs assessment, signature confirmation to the research and development team designed and developed after review. In such an environment, requirements document is the subject of information transmission, but also a contract.
However, the detailed requirements specification has the following five major drawbacks:
- One-way information transfer, prone to be understood that deviations.
- Formal document, we will think it must be right, do not question it, let's stop judgment.
- With detailed documentation, we will not discuss it again, mutual recognition.
- Written documentation is not conducive to shared responsibility team, which played the role of evidence. Scrum team emphasized shared responsibility, regardless of demand, developers and testers still, our common goal is through discussion, collaboration, after proper understanding of the needs of these needs into customers really need function, rather than one-way tasks are passed .
- Preparation of detailed, accurate expression of the requirements document takes a lot of time, if the requirements change frequently, higher maintenance costs.
Agile Product Backlog use to manage demand, product Backlog is a list of requirements, in accordance with the needs of the commercial value of the sort of high-priority demand of the uppermost layer in the Backlog. Product Backlog is a gradual breakdown of the list, it has four main features, known as DEEP:
- Detailed appropriate level of detail, the high-priority needs more detail, more low-priority needs of granularity
- Emergent style emerged, demand is slowly emerging from the gradual breakdown of
- Estimated after estimated
- Prioritized / Ordered in good order according to business value
In the Product Backlog, the demand is mainly in the form of user stories. User story is a brief description from the user's point of view on demand. User stories are the focus of the team from the description, write functional requirements transferred to the best way to approach demand.
User stories are described from the user's perspective eager to get user function. A good user story consists of three elements:
- Cast: Who use this feature.
- Activities: What kind of function needs to be done.
- Business Value: Why do you need this feature, which brings what kind of value.
User stories are usually expressed in the following format:
英文：
As a <Role>, I want to <Activity>, so that <Business Value>.
Chinese:
As a <character>, I want <event> in order to <commercial value>.
For example: as an ordinary member of a site, I expect until after I place an order, shipping can not cancel the order, which is more flexible for me.
Leangoo is a very simple Kanban collaboration tools, we can create products Backlog Agile Kanban by Leangoo to manage demand. The figure is a Product Backlog Kanban example:
On Leangoo billboards, we can create multiple lists, then add story cards on each list. Because we need to the recent high-priority needs into the Sprint, so the billboards can create these lists: the current Sprint, the next Sprint 2, after Sprint, needs to be combed original, you can according to the priority needs of the demands were placed in these columns. Sprint currently has the highest priority, to be sort of the original lower demand priority. After If you can not predict product demand to 3 Sprint, you can create a small column, such as the current Sprint, the next Sprint, after Sprint.
After establishing a good column, we can increase the previous task list inside the card, a card for each story.
The lower right corner of the map story card icon representing the card of this story story points, some discussion on this story, and acceptance testing gist of the story. Acceptance test points reflect the way check items.
In addition to the workload, review, inspection items, we can also set an expiration date, labels, etc. to the card, the card classification or prioritization of the card through the label. As shown below:
In Leangoo, the priority of each card by its position is determined, for each list based on the position of the card inside the card ordering mandatory, high-priority card on top, a low-priority card in demand below.
When the end of an iteration, we need to review to complete the story of the meeting, the assessment can be moved by the story of the list have been delivered in. Leangoo release burndown chart will change automatically generated based on the story card.
Click on the right side of Kanban "menu", select "Kanban statistics" to see burndown chart, as shown below:
Through the above way, we can be very good management of our products Backlog.
Finally, there is a little reminder, agility emphasize transparency, so the visual management product backlog is very important, if conditions allow, we can consider the Product Backlog visualized by a large display screen with touch screen large TV will be better.