Sprints are the heartbeat of Scrum, where ideas get turned into value. They are fixed length events of one month or less designed to create a consistent delivery and feedback cadence for the team. All the work and events necessary to achieve the Sprint Goal (including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective) happen within the Sprint. Each new Sprint starts immediately after the conclusion of the previous one.
Estimated time for this course: 5 minutes
Suggested Prerequisites: Scrum Framework
Upon completion you will:
Sprints are fixed length events of one month or less to create a consistent delivery and feedback cadence for the Scrum Team. The shorter the Sprint length the faster the feedback loop. For example, Scrum Inc. works in one week Sprints.
The Sprint is a container of all other events. A new Sprint starts immediately after the conclusion of the previous sprint, and each Sprint typically begins with Sprint Planning and ends with Sprint Review & Sprint Retrospective. During each day of the Sprint, there is a short event called the Daily Scrum which serves to keep the team aligned and to uncover impediments the team encounters related to making progress on the Sprint Backlog. All the work and events necessary to achieve the Sprint Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.
The regular Sprint cycle serves to:
- Focus delivery on the Sprint Goal. Each Sprint the team should develop a potentially shippable increment of software, a useable iteration of a hardware product, or ultimately: distinct customer value.
- Give the Team regular, high-quality customer feedback on value delivered. The Team can then inspect and adapt both their process and their product based on real and actionable customer input.
- Measure Team output over a consistent and recurring period. This measurement of output is called the Team's Velocity. The Team can use Velocity to forecast their ability to deliver work over time, and create realistic sprint plans based on historical data.
Sprints enable predictability by ensuring inspection and adaptation of progress toward the Product Goal at least every calendar month. Shorter Sprints can generate more learning cycles and limit the risk of cost and effort to a smaller time frame. When a Sprint's horizon is too long, the Sprint Goal may become invalid, complexity may rise, and risk may increase. Each sprint may be considered a short project and can be canceled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the sprint.
View and Download Class Slides
The Scrum Pattern Language of Programming (PLoP) codifies well known Agile practices that have been successfully implemented many times.
Sprints ni moyo wa Scrum, ambapo mawazo kupata kugeuka katika thamani. Ni matukio ya muda wa kudumu ya mwezi mmoja au chini iliyoundwa ili kuunda utoaji thabiti na maoni ya timu. Kazi zote na matukio muhimu kufikia Sprint Lengo (ikiwa ni pamoja na Sprint Mipango, Daily Scrums, Sprint Review, na Sprint Retrospective) kutokea ndani ya Sprint. Kila Sprint mpya huanza mara tu baada ya kumalizika kwa ile ya awali. Wakati wa kukamilisha: 5 dakika, na baada ya kumaliza, utaweza kuanzisha Sprint, ambayo ni kipindi cha muda wa mwezi mmoja au chini ya kuunda utoaji thabiti na feedback cadence kwa timu ya Scrum. Muda mfupi Sprint urefu kasi zaidi feedback kitanzi. Kwa mfano, Scrum Inc. inafanya kazi katika Sprints ya wiki moja. Sprint ni chombo cha matukio mengine yote. Sprint mpya huanza mara tu baada ya kumaliza Sprint ya awali, na kila Sprint kawaida huanza na Sprint Mpango na mwisho na Sprint Review & Sprint Retrospective. Katika kila siku ya Sprint, kuna tukio fupi linaloitwa Daily Scrum, ambalo hutumika kuweka timu sawa na kufunua vikwazo ambavyo timu inakutana na kuhusiana na kufanya maendeleo kwenye Sprint Backlog. Kazi zote na matukio muhimu kufikia Sprint Lengo, ikiwa ni pamoja na Sprint Mpango, Daily Scrums, Sprint Review, na Sprint Retrospective, kutokea ndani ya Sprints. Mzunguko wa kawaida wa Sprint hutumika kwa: - Kuweka lengo la utoaji kwenye Lengo la Sprint. Kila Sprint timu lazima kuendeleza uwezekano shippable ongezeko la programu, iteration usable ya bidhaa ya vifaa, au hatimaye: tofauti thamani ya mteja. - Kutoa Timu mara kwa mara, ubora wa juu wateja maoni juu ya thamani alitoa. Timu inaweza kisha kukagua na kurekebisha mchakato wao na bidhaa zao kulingana na maoni halisi na ya vitendo ya wateja. - Kupima Timu pato juu ya kipindi cha mfululizo na mara kwa mara. Kipimo hiki cha pato huitwa Kasi ya Timu. Timu inaweza kutumia kasi ya kutabiri uwezo wao wa kutoa kazi kwa muda, na kuunda mipango ya sprint ya kweli kulingana na data ya kihistoria. Sprints kuwezesha predictability kwa kuhakikisha ukaguzi na marekebisho ya maendeleo kuelekea Lengo la Bidhaa angalau kila mwezi kalenda. Sprints fupi inaweza kuzalisha mzunguko zaidi wa kujifunza na kupunguza hatari ya gharama na juhudi kwa muda mdogo. Wakati upeo wa Sprint ni mrefu sana, Sprint Lengo inaweza kuwa halali, utata inaweza kuongezeka, na hatari inaweza kuongezeka. Kila sprint inaweza kuchukuliwa mradi mfupi na inaweza kufutwa kama Sprint Lengo inakuwa ya kizamani. Mmiliki wa Bidhaa tu ana mamlaka ya kufuta sprint. Scrum Pattern Language of Programming (PLP) ni lugha ya programu ya Scrum ambayo inaonyesha mbinu za Agile ambazo zimetumika kwa mafanikio mara nyingi.