Use user stories to capture and requirements

The purpose of requirement engineering is to improve the requirements that can be improved before the start of the development. The requirements that cannot be improved before the start of the development shall be improved during development.

This process also helps the team minimize the unnecessary surprises during the development and testing phases. This process also ensures that testers test the contents written by the developers and the contents expected by the users are in line.

Before entering the first iteration, it is the responsibility of the product owner to provide the demand backlog. If the product owner believes that the vision, business analysis, and even market promises on hand do not need to be improved or eliminated, and the unclear requirements are suitable for the team to improve after entering the first iteration, then requirements engineering is not necessary. If the product owner thinks that some ideas are too general and need to be improved or eliminated, or need to deal with the different opinions of other stakeholders, then the product owner can use the requirements engineering Kanban to improve or eliminate requirements to make them suitable for the first iteration.

The first batch of requirements are based on vision, business analysis, and even market promises. Product owners use scenarios or user stories to improve their clarity and resolve conflicting requirements. This process helps the product owner to explain the backlog of requirements to the team more structured after entering the iteration.

In the iterative development process, the requirements listed in the prioritized product backlog (which will be updated before each iteration) will evolve into work that can and should be done using empirical data, which is obtained by writing and testing code of. This type of requirements improvement is carried out after entering the iteration, rather than in the requirements engineering before entering the first iteration.

In requirements engineering, the product owner collects useful user stories, understands what users are doing, what they can do with new product features, and is inspired to sort out the initial backlog of requirements, and then enter the first iteration and start iteratively improving demand.

Where needs exist, product managers can establish a prioritized initial demand backlog through requirements engineering activities. The product manager introduces the vision and demand backlog to the team. The team meets with the Scrum supervisor to plan the first iteration so that the highest priority task can be completed and the high priority task can be broken down into several iteration tasks.