Copyright © by Mark J. Sebern Software Engineering Process I SE Sprint review and retrospective

Copyright © by Mark J. Sebern Sprint Review & Retrospective Two “end of sprint” activities Sprint review Sprint retrospective How do they differ?

Copyright © by Mark J. Sebern Review Participants WhoRole Scrum teamHear product feedback, answer questions regarding the sprint and product increment Internal stakeholders Provide feedback, suggest changes (from what perspective?) Other internal teams Provide area-specific feedback (e.g., sales, legal, other development) and sync work External stakeholders Provide feedback, suggest changes (who exactly? why?)

Copyright © by Mark J. Sebern Review Preparation Sprint review prework Identify participants (specific people) Set the schedule (when, duration) Confirm sprint work is done (DONE)

Copyright © by Mark J. Sebern Review Preparation Sprint review prework Identify participants (specific people) Set the schedule (when, duration) Confirm sprint work is done (DONE) Same time each sprint?

Copyright © by Mark J. Sebern Review Preparation 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 (DONE)

Copyright © by Mark J. Sebern 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?)

Copyright © by Mark J. Sebern Review Overview Sprint backlog items (or sprint goal) Potentially shippable product Groomed product backlog Updated release plan Review 1.Present sprint goal, PBIs, actual achievements Explain any discrepancies 2.Demonstrate what actually got built What if it cannot be demonstrated? (Really??) 3.Discuss state of the product, future direction of the project Implicit/explicit backlog grooming

Copyright © by Mark J. Sebern Sprint Retrospective Why?

Copyright © by Mark J. Sebern Sprint Retrospective Why? More meetings?

Copyright © by Mark J. Sebern Sprint Retrospective Why? More meetings? When am I supposed to get some work done?

Copyright © by Mark J. Sebern Sprint Retrospective Why? More meetings? When am I supposed to get some work done? The New York Times How about now?

Copyright © by Mark J. Sebern Retrospective Participants WhoRole Scrum teamReflect on the sprint experience from a process point of view ScrumMasterLead process discussion, help team focus on fidelity to its own chosen process Product ownerHelp address issues with requirements, PBI grooming issues, interaction with team Other stakeholdersOnly if invited by the team; not invited if negative effect on team safety/openness

Copyright © by Mark J. Sebern Retrospective Participants WhoRole Scrum teamReflect on the sprint experience from a process point of view ScrumMasterLead process discussion, help team focus on fidelity to its own chosen process Product ownerHelp address issues with requirements, PBI grooming issues, interaction with team Other stakeholdersOnly if invited by the team; not invited if negative effect on team safety/openness In particular, probably no managers.

Copyright © by Mark J. Sebern Retrospective Structure How much time? Location? Facilitator? ScrumMaster Other team member Outsider (other ScrumMaster?)

Copyright © by Mark J. Sebern Overview Focus Exercises (or prep) Objective data Subjective data Insight backlog Improvement actions Insight backlog Improved team spirit Retrospective Set atmosphere Establish shared context (common perspective from individual ones) Identify insights (see following slides) Determine actions Close the activity

Copyright © by Mark J. Sebern Insights What worked well, or not? Improvement ideas? Organize insight backlog Cards on wallABC DEF

Copyright © by Mark J. Sebern Insights What worked well, or not? Improvement ideas? Organize insight backlog Cards on wall A B C D EF Silent grouping Pre-existing categories?

Copyright © by Mark J. Sebern A B C D EF Actions Select insights from new backlog “Dot voting” Consider timeframe for changes Decide on actions Specific task items General changes

Copyright © by Mark J. Sebern Follow Through Sprint tasks Include tasks to implement chosen actions Not a separate “improvement” effort Integrate into the next sprint’s work

Copyright © by Mark J. Sebern 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

Copyright © by Mark J. Sebern What Else? What else did you learn about sprint reviews and retrospectives? What questions do you have?