1 / 14

Retrospectives in Agile Project Management

Retrospectives in Agile Project Management. Mai Müür Tallinn 2014. Table of content. Retrospective as a part of Scrum The idea of retrospectives Rules of the game Impact to IT team Strenghts and weaknesses. SCRUM framework . Sprint backlog. Product backlog . Release.

zora
Télécharger la présentation

Retrospectives in Agile Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Retrospectives in Agile Project Management Mai Müür Tallinn 2014

  2. Table of content • Retrospective as a part of Scrum • The idea of retrospectives • Rules of the game • Impact to IT team • Strenghts and weaknesses

  3. SCRUMframework Sprint backlog Product backlog Release Sprint planning meeting Daily scrum 1-2 weeks Updated product backlog Sprint retrospective 1-3 hours Sprint review meeting

  4. The Purpose of Retrospectives Here is Edward Bear, coming downstairs now, bump, bump,bump,bump, on the back of his head, behind Christopher Robin. It is, as far as he knows, the only way of coming downstairs, but sometimes he feels that there is another way, if only could stop bumping for a moment and think of it. * *qoutation from Winnie the Pooh by Norm Kerth, (Kerth 2001) Norm Kerth** • **Norm Kerth -the founder of the modern-day movement of retrospectives

  5. The Idea of Retrospective Meeting • What went well? • Where we failed? • What should we improve? • What should we stop? • What should we start? • DEVELOPMENT PROCESS • Tehnical event • Organizational event • Personal event INSPECT ADAPT Made by Scrum Team Supported by Scrum Master

  6. Procedure of Retrospective Meeting • Scrum retrospective prework • Timebox for meeting 1-3 hours • Scrum exercises • Decisions for next sprints : What? Who? When? • Changes to product backlog

  7. 1. Exercise: event timeline and emotions seismogram

  8. 2. Exercise INSIGHTS PREASSIGNED CATEGORIES SILENT GROUPING SHARED CONTEXT PRIORITIZING INSIGHTS DOT VOTING DETERMINE THE SOLUTION/WHO WILL DO IT/ HOW LONG DOES IT TAKE INSIGHTS BACKLOG. CLOSING. FOLLOW UP

  9. Retrospective Meeting INPUT • Agreed focus • Precollected objective data • Team members with subjective data and spirit • Backlog of insights from previous retrospective • Exercises and materials for visualization OUTPUT • Process improvement actions • Insight backlog • Changes in teamspirit

  10. Retrospective Impact to Team You might not like Your job, but still enjoy the camaraderie of the people You work with.* * Explanation to the word “camaraderie” in Vocabulary.com

  11. Estimation STRENGHTS • Fixed rules and timetable • Positive mindsetting • Equal possibility for every team member • Simple decision making tools WEAKNESSES • Weak Scrum Master • Inactivity in reflection/participation • Team doesn`t have clear understanding about Scrum process

  12. Take home message Take retrospective as a good advantage to look inside the process, before You are totally lost. Thank You!

  13. References • Derby E., Larsen D., Agile Retrospectives, The Pragmatic Bookshelf; version: P 6.0 – 2011 • Schwaber K., Sutherland J.; The Definitive Guide to Scrum: The Rules of the Game, The Scrum Guide TM , July2013 • Rubin, Kenneth S. Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn)) (Kindle Location 21). Pearson Education. Kindle Edition. (2012-07-20

More Related