copyright © 2012-2014 by mark j. sebern software engineering process i se-2800-14 sprint review and...

Copyright © 2012-2014 by Mark J. Sebern

Software Engineering

Process ISE-2800-14

Sprint review and retrospective


Sprint Review & Retrospective

• Two “end of sprint” activities

• Sprint review

• Sprint retrospective

How do they differ?


Review Participants

Who Role

Scrum team Hear 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?)


Review Preparation• Sprint review prework

• Identify participants (specific people)

• Set the schedule (when, duration)

• Confirm sprint work is done (DONE)


Review Preparation• Sprint review prework




Same time each

sprint?


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





Sprint review prework

• Identify participants – specific people


• Confirm sprint work is done

• Prepare for demonstration – ceremony

level

• Decide who does what (facilitator,

demo?)


Review OverviewSprint backlog items (or sprint goal)Potentially shippable product

Groomed product backlogUpdated 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


Sprint Retrospective

Why?



Why?

More meetings

?



Why?

More meetings

?

When am I supposed to get

some work done?



Why?

More meetings

?

When am I supposed to get

some work done? The New York Times

How about now?


Retrospective Participants

Who Role

Scrum team Reflect on the sprint experience from a process point of view

ScrumMaster Lead process discussion, help team focus on fidelity to its own chosen process

Product owner Help address issues with requirements, PBI grooming issues, interaction with team

Other stakeholders

Only if invited by the team; not invited if negative effect on team safety/openness


Retrospective Participants

Who Role

Scrum team Reflect on the sprint experience from a process point of view

ScrumMaster Lead process discussion, help team focus on fidelity to its own chosen process

Product owner Help address issues with requirements, PBI grooming issues, interaction with team

Other stakeholders

Only if invited by the team; not invited if negative effect on team safety/openness

In particular, probably no managers.


Retrospective Structure

• How much time?

• Location?

• Facilitator?

• ScrumMaster

• Other team member

• Outsider (other ScrumMaster?)


OverviewFocusExercises (or prep)Objective dataSubjective dataInsight backlog

Improvement actionsInsight backlogImproved team spirit

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 wallA

B

C

D

E F

• Silent grouping

• Pre-existing categories?


A

B

C

D

E F

Actions• Select insights from new

backlog

• “Dot voting”

• Consider timeframe for changes

• Decide on actions

• Specific task items

• General changes


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?

copyright © 2012-2014 by mark j. sebern software engineering process i se-2800-14 sprint review and...

Documents

sebern sprint retrospective

sprint work

sebern sprint review

sprint experience

retrospective slide

present sprint goal

team safetyopenness

participants specific