220 likes | 356 Views
Software Engineering Process I. SE-2800-14 Sprint review and retrospective. Sprint Review & Retrospective. Two “ end of sprint ” activities Sprint review Sprint retrospective. How do they differ?. Review Participants. Review Preparation. Sprint review prework
E N D
Software Engineering Process I • SE-2800-14 • Sprint review and retrospective
Sprint Review & Retrospective • Two “end of sprint” activities • Sprint review • Sprint retrospective How do they differ?
Review Preparation • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE)
Review Preparation Same time each sprint? • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE)
Review Preparation • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE) • What is the definition of DONE? • Who decides? • When is the decision made? (at end? JIT during sprint?) • Granularity of the decision? (per PBI?)
Sprint review prework • Identify participants – specific people • Set the schedule (when, duration) • Confirm sprint work is done • Prepare for demonstration – ceremony level • Decide who does what (facilitator, demo?)
Review Overview Review • Sprint backlog items (or sprint goal) • Potentially shippable product • Groomed product backlog • Updated release plan • Present sprint goal, PBIs, actual achievements • Explain any discrepancies • Demonstrate what actually got built • What if it cannot be demonstrated? (Really??) • Discuss state of the product, future direction of the project • Implicit/explicit backlog grooming
Sprint Retrospective • Why?
Sprint Retrospective More meetings? • Why?
Sprint Retrospective More meetings? • Why? When am I supposed to get some work done?
Sprint Retrospective How about now? More meetings? • Why? When am I supposed to get some work done? The New York Times
Retrospective Participants In particular, probably no managers.
Retrospective Structure • How much time? • Location? • Facilitator? • ScrumMaster • Other team member • Outsider (other ScrumMaster?)
Overview • Improvement actions • Insight backlog • Improved team spirit • Focus • Exercises (or prep) • Objective data • Subjective data • Insight backlog Retrospective • Set atmosphere • Establish shared context • (common perspective from individual ones) • Identify insights (see following slides) • Determine actions • Close the activity
Insights • What worked well, or not? • Improvement ideas? • Organize insight backlog • Cards on wall A B C D E F
Insights • What worked well, or not? • Improvement ideas? • Organize insight backlog • Cards on wall B D E F • Silent grouping • Pre-existing categories? A C
Actions • Select insights from new backlog • “Dot voting” • Consider timeframe for changes • Decide on actions • Specific task items • General changes B D E F A C
Follow Through • Sprint tasks • Include tasks to implement chosen actions • Not a separate “improvement” effort • Integrate into the next sprint’s work
Retrospective Issues • Not doing one (or not well) • Superficial, not addressing real issues • Watch out for the elephant! (safety?) • Poor execution: facilitation, blame/complain • Too ambitious (or miss ongoing improvements) • Lack of follow-through
What Else? • What else did you learn about sprint reviews and retrospectives? • What questions do you have?