3 ms·
Oh my god! No, no, no, the author does not understand the purpose of sprints. Assuming the originator of the concept of a sprint is Scrum (and it's a big assum
by azangru 4y ago
Oh my god! No, no, no, the author does not understand the purpose of sprints.
Assuming the originator of the concept of a sprint is Scrum (and it's a big assumption; normally I'd check, but I am lazy and somebody is clearly wrong on the internet), then the purposes of sprints are:
- to set a regular cadence/rhythm to work, and to set up periodic checkpoints for inspection of the done product and adaptation of the work that follows
- within a sprint, to produce a done increment that brings the team closer to the product
- by the end of the sprint, to allow stakeholders to inspect the done increment, to observe if anything is being done wrong or in the wrong order, to collect the feedback, and adjust, if necessary, the plans against the reality
- and then to repeat the same over the next iteration, and the next, and the next
- HelloNurse 4y agoIn Scrum, the purpose of defining sprints is mostly, despite the name, to slow down between them, in order to allow for some planning and discussion; otherwise there would be only an endless stream of "urgent" tickets and requests.
- JackMorgan 4y agoYou missed one of the most important: to provide slack time. Ideally, the team will only commit to less than they can accomplish, so there is built in slack time to do research, training, tech debt, and proof of concepts.