Scrum drill (6)

End.

The system will be demonstrated at Wednesday morning and Wednesday after the scanning of Monday and Tuesday.
The key points of the system are not fixed, that is, the goal of this sprint is not achieved. During this demonstration, we found that there are still some functional omissions.

The overall investment is lower than the estimated value. Functional omission is my poor supervision. In fact, I did not care about it intentionally. It is to test whether the list of my stories is clearly written so that everyone can understand it. It turns out that improvements are needed. The story must be detailed and have its own themes. It is not possible to merge irrelevant stories because of similarity.

The decomposition of the story is not good at this time, and the team is used to encoding by level. However, if a story is divided into three layers, it is too small. It is too messy to combine it. Next time, we will make a specific subdivision to avoid omission.

The driver for this test is not well executed. Next time you improve the driver, write the test first.Code.

The good thing is that cc.net can automatically complete code acquisition, compilation, and unit testing. Automatic Web Testing has not yet been implemented.

When entering the sprint, personnel investment should be improved as much as possible to reduce interference with other projects or tasks. External factors should minimize their dependencies to ensure the normal progress of the project.

In short, this is our first scrum experience.