Increment – the sum of all realized requirements of the product backlog.
- Meets the accepted criteria
- Product owner decides whether to bring it to the customer or not
The increment is the main artifact of the scrum.
It is what is the result of the team’s labor in a single iteration. It represents the incremental value of the product. If this increment is insignificant or looks “unsightly,” the product owner may not show it to the customer. However, a good practice in scrum is to regularly show or deliver the results to the customer. This motivates the customer, because he sees the progress and understands where the money is spent. This is also good for the team, because quick feedback from the customer makes it easier to stay focused on the customer’s needs.
Definition of done
– This is the condition when the job is considered to be successfully done. This criterion is determined in advance and stipulated by the team. Thanks to it there is no situation where the team members think that they have finished their tasks, but the product as a whole – does not work. The criterion of readiness should be separate for stories and separate for iteration.
Criteria may vary from team to team. From “code populated in the repository” to “ready for deployment to a live server.
Examples of readiness criteria
Custom History
– All the tasks of history are done
– Acceptance tests successfully passed
– Integration tests of the entire project successfully passed
– Changeelog entries made
Increment
– There is a working demo booth, which includes all the functionality made
– Successfully passed regression testing
– Demonstration was done
If necessary, individual readiness criteria can be set for individual stories, but they must be stipulated in advance, when planning them.
In the next article, we begin to deal with the Scrum process
