New answers tagged

1

Backlog and 'Fail-fast' are at the very foundation of agile development. In a way, 'Failure in a sprint' is actually a desirable quality. Failed sprint, according to me, is a well-executed sprint. Failure facilitates continuous improvement. 100% success of sprint happens in 2 cases: Team is complacent and is not pursuing ambitious goals. Organization ...


8

I am personally adverse to the idea of ever saying a sprint 'failed'. Scrum uses the term 'inspect' 27 times, and 'adapt' 16 times over the course of the guide. Scrum also has no notion of 'failure', and the only reference to failure in Scrum is listed here: Failure to include any of these events results in reduced transparency and is a lost ...


4

From the Scrum Guide: During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment. So basically, in each Sprint it's not enough to keep yourself ...


22

According to Mike Cohn It’s quite common for a team to have a bit of unfinished work at the end of an agile sprint or iteration. Ideally, a team would finish every item on its sprint backlog every sprint. But, for a variety of reasons, that isn’t always the case. Accordingly to Scrum.org: The Scrum Goal is the creation of productive and creative ...


3

A failed sprint means you did not reach the sprint goal. That can mean all stories but one were completed, but that one was critical to reach the goal. Only you can know whether this is the case here. Keep in mind that the stories pulled into the sprint are a forecast of what the team should be able to do. Saying "all stories must be done" as some ...


Top 50 recent answers are included