Presentation is a key practice in agile development. Generally, it is iterated once, which can be adjusted according to the specific situation of the project. Showcase is the time to show the function and the face of the development team, and its importance is self-evident.
Showcase's process is to follow the user story acceptance criteria (AC) one by one, without continuity. It is difficult for the audience to associate each AC with the overall system characteristics and real business scenarios during this demonstration, and it is easy to get lost.
Therefore, instead of presenting user stories one by one, it is better to string the whole function together. It is best to define business scenarios one by one and show them to customers, and try to describe them in business language. In this way, the customer's business personnel feel more intimate, and it will definitely leave a good impression to see that the development team members can describe and demonstrate in business language.
The importance of display
In order to reduce contradictions and ensure that development and testing have the same understanding of requirements, several key activities such as planning meeting, requirements discussion meeting, requirements clarification meeting before development, test case review, development and display are ensured in the agile process.
In the planning meeting, the product manager will explain the requirements, and development and testing will be involved. If the requirements are inconsistent, the project manager or product manager will immediately check the communication. When it comes to test case review, the requirements are refined into test cases, so that development and testing can further understand the requirements and reach an agreement.
After the function development is completed, give a test demonstration. The test will check whether the developed function is consistent with the requirement again, and point out the obvious inconsistency on the spot. The developer will submit it to the test after correction, which basically ensures that the test can run all the test cases of the requirement at one time.