<<insert customer logo>>

<<insert customer logo>>

Sprint Retrospective

© 2013 Apigee Confidential – All Rights Reserved 2

Purpose of Retrospective:• Begin with recognition and/or appreciation

– What stood out– Who really went out of their way

• Goal:– “find our learning’s”– Incremental improvement– Feedback loop

• We want to reflect on what the team needs to be more efficient and effective• Noted charts should be auto-generated from JIRA and should not take a

significant amount of time.• Keep these goals in mind when building each sprint retrospective presentation

<<DELETE THIS SLIDE FOR FINAL PRESENTATION>>

Purpose


• Retrospective Overview• Accepted User Story & Special team recognition/appreciation

– [Fill in prior to retrospective team meeting]• Sprint Burn Down Chart• Planned vs. Actual Velocity• Velocity over Time• Big Picture: Release Burn Up• Creation of Actionable Items

– Focus on varying degrees of evaluation: “Keep Doing, More of, Start Doing, Stop Doing, Less of”

• Review the Top 3 actionable items created and obtain agreement from team

Retrospective Agenda


• <<align on intent of retrospectives. Recommend to have this reviewed the first few times and subsequent>>

Goal• Improve process to increase delivery efficiency

Ground Rules• Leave ego at the door• Keep comments team oriented versus making it personal• Don’t try to solve issues in the meeting• Keep comments short, so we get everyone’s input

Retrospective Overview


• <<List of accepted user stories, gives sense of achievement>>• <<Team member recognition as applicable>>

Accepted User Stories & Team Recognition


Sprint Burn Down Chart

• <<Add the Sprint burn down chart here from the sprint board>>• <<Self explanatory>>


<<Planned:>><<Achieved:>><<Scope changes, if any:>>

Planned Vs Actual Velocity


• <<Add bar chart showing velocity over last few sprints>>• <<Are we gaining momentum?>>

Velocity over time


• <<Chart showing release achievement till date>>

Big picture : Release burn-up


Keep Doing: focus on the good practices that we like about the project– Question to prompt team discussion: What would you [the project team] miss if you

didn’t have a particular practice/technique/methodology/role/team member/etc?

– [list actionable items here as discussion progresses]

Actionable Items – Keep Doing


More of: Is another focus that helps further refine or highlight practices, technologies, etc that team members might want to try more and are not necessarily taking full advantage of. – [list actionable items here as discussion progresses]

Actionable Items – More Of


Start Doing: the opportunity for team members to suggest new ways to try activities within a sprint– Examples include activities that may not have gone as well as expected or the

introduction of new activities


Actionable Items – Start Doing


Stop Doing: things that are not contributing to successful development practices or not adding value.


Actionable Items – Stop Doing


Less Of: practices that need more refining or that were not helpful in the last sprint– Note that the practice may have added value but not enough given the time it took to

complete or did not add as much value as other practices


Actionable Items – Less Of


Top 3 Items to Focus on for Next Sprint

Actionable Item Description Type Owner

More of Test Lead

Keep Doing Technical Architect

Start Doing Scrum Master

Thank you

2013

Documents

<<insert customer logo>>