Agile development with tools-14

Now let's start talking about things after a sprint. The first thing is of course the review meeting, the so-called review will be the product owner to check whether the sprint function is completely based on the design document, and whether it is 100% of the customer's requirements, in this meeting, we need to demonstrate each function.

 

The ideal situation is that all the functions required at the Planning Meeting are perfectly implemented. Everyone is very satisfied and excited. Even the user representatives are satisfied. However, this is often not the case. The following situations may occur:

1. The feature has not been completed by the end of the sprint: in this case, you do not need to view this feature at the meeting. You can skip this feature and wait until the end of the next sprint to see this feature.

2. the function has been completed, but the test has not been completed: in this case, we recommend that you wait until the test is completed to demonstrate this function, because the developers think that the "done" is perfect, there are no bugs, but many problems are often found in the test. Therefore, after development is completed, it is not the real function, but it must be completed after the test is completed.

3. the function development and testing are completed, but the design idea is incorrect and needs to be modified again: in this case, we recommend that you create a new function and add it to the backlog, the task will be assigned as a new feature.

 

For a review meeting, it is very important to see a product that can work to demonstrate the functions implemented by the sprint. The purpose of the demonstration is to let everyone know whether the product is as planned, follow the correct direction and follow the customer's needs. Therefore, each sprint cannot be postponed without reason. Even if you have an important feature that is not completed, it doesn't matter, delay this function until the next sprint is completed. Other functions in this sprint can be normally demonstrated in the product. Therefore, we generally require development. Do not submit unimplemented features.CodeOtherwise, it may cause build failure or other unpredictable problems. Make sure that the implemented functions work properly. Our company has experienced the development and submission of unfinished functional code, resulting in two days of failure to obtain an available build for testing, which has a huge impact.