Handing over the Baton: Maintaining Value via the Sprint
When the next Sprint Meeting is held, the development team will select as many high priority items from the Backlog as they can complete during the Sprint time period and commit to getting them “done”. Each Sprint delivers an Increment. This is a working segment of the product that has been tested and checked against pre-defined acceptance criteria.
This is demonstrated to the stakeholders for their review by inspection and approval. What frequently happens at this stage, when faced with this working part of the whole product, is that the stakeholders find that they need to change their original requirements. This is where Scrum is more receptive than conventional project management; change is acknowledged and welcomed.
The only stipulation is that changes cannot be introduced during a Sprint; but since we are talking about a matter of a fortnight or four weeks, this is not a long delay. By introducing change requests as soon as possible, there is an increase in the business value, as the product is being continuously aligned to the latest requirements.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: