Agile development story Wall

After clarifying the requirement, se stuck all the stories on the story wall, waiting for developers to develop. The story wall template is:

Analysis: After the requirement clarification is completed, se adds all the stories to the analysis stage.

Waiting for development: After the developers and Se confirm the requirements and clarify what to do and how to do it, they will move the story from the analysis phase to the waiting for development.

Under development: Developers develop only one story card at a time, and port the card to development.

Blocking: If the story card cannot continue during development due to coordination, move the card to the blocking stage

Development completed: After the development is complete and show case to se, the developer will plug the story card and wait for the test.

Waiting for test: The tester will test the story card after waiting for the card to be tested. After the test is completed, the card will be moved to the test completion phase. If the test has any problems, the card will be removed to the development phase.

Test Complete: The Life Cycle of this card ends

The story wall is under development and development. Waiting for the test to be completed belongs to the tester. The developer and tester must stick to their own territory. When the card moves, they must confirm the acceptance. If there is any unclear and problems, remove your territory in time.

Why is there a story wall? What is the role of the story wall?

The story wall describes various stages in the development process and reflects the health status of the current development team. During daily standing meetings, developers will share their Development Status, Problems, and assistance with the story wall. The project leader can also learn the status of the current team through the story wall in a timely manner and adjust it in a timely manner.