Agile Retrospectives
A ScrumBut example
by Viktor Degtiarov
viktor.degtiarov@globallogic.com
Agile Manifesto
• Individuals and interactions over processes and tools
• Working software over comprehensive documentatio...
Agile Retrospective
Example of ScrumBut Process
• Scrum team of 8 team members
• Sprint length – 2 weeks
• Project start date – Sep 1st, 2011
Phase 1 – Set the Stage
• Do regular retrospectives
• Schedule the meeting
• Be in time
• Ask team to be prepared
• Schedu...
Phase 2 – Gather Data
• Prepare metrics
• Share metrics
• Fill all the work done to JIRA
• Used metrics: Sprint Length, Fo...
Phase 2 – Metrics Example
Sprint # 5 4 3 2 1
Duration (work days) 10 10 10 10 10
Velocity (story points) 54 28 19 36 24
Fo...
Phase 2 – Burndown Chart
Phase 3 – Generate Insights
• What did we do well?
• What can be improved?
• Brainstorming
• Retrospective poker
• Don’t t...
Phase 3 – Well Done
• Stabilization sprint
• Continuous integration
• Refactoring started
• Testing documentation done
• G...
Phase 3 – To Be Improved
• No code reviews
• Late deploy
• Poor automation testing
• No load/performance testing
• Lack of...
Phase 4 – Decide What To Do
• Decisions are approved by
majority of team members
• Discuss the ways of improving
the proce...
Phase 4 – Action Items
• English standups and chat – all
• Start DB clean up process – Alex
• Use JIRA as bug tracking too...
Phase 5 – Close the Retrospective
• Thanks to everyone
• Share the results
• Use action items during
next planning meeting...
Thank you
Upcoming SlideShare
Loading in...5
×

Agile Retrospectives (Виктор Дегтярёв)

114

Published on

- Review of Agile Manifesto.
- Retrospective as agility tool.
- 5 phases of retrospective.
- How we do Scrum(but) retrospectives in real project.

Published in: Automotive, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
114
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Agile Retrospectives (Виктор Дегтярёв)

  1. 1. Agile Retrospectives A ScrumBut example by Viktor Degtiarov viktor.degtiarov@globallogic.com
  2. 2. Agile Manifesto • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
  3. 3. Agile Retrospective
  4. 4. Example of ScrumBut Process • Scrum team of 8 team members • Sprint length – 2 weeks • Project start date – Sep 1st, 2011
  5. 5. Phase 1 – Set the Stage • Do regular retrospectives • Schedule the meeting • Be in time • Ask team to be prepared • Schedule enough time (1-1.5 hrs) • Select the convenient time of the day
  6. 6. Phase 2 – Gather Data • Prepare metrics • Share metrics • Fill all the work done to JIRA • Used metrics: Sprint Length, Focus Factor, Total Work Hours, Logged Time, % of Tasks Done, Planning Accuracy, Defect Removal Efficiency, etc
  7. 7. Phase 2 – Metrics Example Sprint # 5 4 3 2 1 Duration (work days) 10 10 10 10 10 Velocity (story points) 54 28 19 36 24 Focus factor 0.51 0.48 0.47 0.46 0.40 Stories done 53% 36% 49% 42% 37% Work hours submitted 287 243 198 178 161 Total hours 564 504 418 388 400 Planning accuracy 1.09 1.25 1.38 1.22 1.39
  8. 8. Phase 2 – Burndown Chart
  9. 9. Phase 3 – Generate Insights • What did we do well? • What can be improved? • Brainstorming • Retrospective poker • Don’t try to blame somebody • Everyone to share his/her opinion
  10. 10. Phase 3 – Well Done • Stabilization sprint • Continuous integration • Refactoring started • Testing documentation done • Good work done for the demo • Work on Saturday • Mobile version is created • Work started on new feature • DB documentation is created • iPad development • Customer visit • New DB changes deployment approach
  11. 11. Phase 3 – To Be Improved • No code reviews • Late deploy • Poor automation testing • No load/performance testing • Lack of girls in project team • Refactoring brought several problems • Poor estimations • Low website performance • Broken sprint • Ineffective merge practice • Communication problems
  12. 12. Phase 4 – Decide What To Do • Decisions are approved by majority of team members • Discuss the ways of improving the process • Find solutions that fix problems from what can be improved list • Create list of action items • Each action item is assigned to team member(s)
  13. 13. Phase 4 – Action Items • English standups and chat – all • Start DB clean up process – Alex • Use JIRA as bug tracking tool - all • Do not skip planning meetings! – all • Plan time for bugfix verification – QAs • Setup local knowledge sharing meeting – Ihor • Do code reviews for all the new features – developers • Create testing documentation – QAs • Create SVN account for autodeploy - Viktor • Penalties for not logged time or skipped stand ups - all • Fix local servers configuration – Pavel • Concentrate on features from the top of backlog - all
  14. 14. Phase 5 – Close the Retrospective • Thanks to everyone • Share the results • Use action items during next planning meeting • Check action items during next retrospective
  15. 15. Thank you
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×