Life B4 and After Scrum


Published on

Presented at Scrum Gathering Brazil 2009

Published in: Technology, Health & Medicine
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Life B4 and After Scrum

  1. 1. The life before and after Scrum<br />Michel Goldenberg CSM/CSP<br />Payam Afkari CSM<br />
  2. 2. About this presentation<br />This presentation talks about some cases showing the processes in the IT team before Scrum; <br />How Scrum was implemented;<br />Some problems that appeared during the implementation and how they were solved;<br />What Scrum changed in the IT teams.<br />2<br /><br />
  3. 3. Michel Goldenberg<br />Agile Coach acting in Montréal area;<br />Over 10 years of experience in IT;<br />Expertise: Coaching people and implementing Scrum in big corporations.<br />Cofounder of Montreal’s Scrum user group<br />3<br /><br />
  4. 4. Payam Afkari<br />Scrum Master and Business analyst in montreal area<br />Close to 10 years in IT.<br />Cofounder of Montreal’s Scrum user group<br />4<br /><br />
  5. 5. The waterfall approach<br />Etude opportunite <br />Preliminary analysis<br />Architecture <br />Developpement <br />testing<br />Implementation<br />Request for Change<br />Add pictures<br /><br />5<br />
  6. 6. The waterfall approach<br />Requirement Gathering <br />and analysis<br />Client see for the first time<br />System design<br />Implementation<br />testing<br />Deployment<br />Yes<br />Maintenance<br />Client <br />approval<br />RFC<br />No<br />New functionality<br />
  7. 7. Used functionality<br /><br />7<br />
  8. 8. From plan driven to value driven dev<br /><br />8<br />
  9. 9. Scrum Framework<br />Analysis<br /><br />9<br />
  10. 10.<br />10<br />
  11. 11. Scrum Framework (vision)<br />Analysis<br /><br />11<br />
  12. 12. Vision <br />Before: Client came with his vision and wanted his solution.<br />After : the team works with the client to validate the needs and to come up with a better vision and solution<br /><br />12<br />
  13. 13. Scrum Framework (Release planning)<br />Analysis<br /><br />13<br />
  14. 14. Release planning (Before)<br />Project manager creates the plan and all the activities that he thinks is necessary. <br />The activities are assigned to members . <br />The release date is scheduled (imposed). <br />Every body think they know their job for the project.<br /><br />14<br />
  15. 15. Release Planning (After )<br />A product backlog is created with the help of the client (product owner, PO);<br />The PO prioritize the product backlog items;<br />Team has an idea of what should be done;<br />A release date can be proposed, based on the performance (velocity) of the team. <br /><br />15<br />
  16. 16. Release planning - Challenges we went through<br />Project manager wants to take control;<br />Work on task instead of activities;<br />Moving from a service provider to a partnership with the client;<br />Identify a PO;<br />Getting the client (PO) to work with the team;<br />Client wants to sign a contracts;<br />Client is hesitant.<br /><br />16<br />
  17. 17. Release planning<br />Release Plan<br />Sprint 1<br />Sprint 2<br />Sprint 3 - 8<br />Release planning <br /><br />17<br />
  18. 18. Scrum framework (Sprint planning)<br />Analysis<br /><br />18<br />
  19. 19. Sprint planning (Before)<br />Activity planning done by the Project manager.<br />No such thing as sprint.<br />No negotiation.<br /><br />19<br />
  20. 20. Sprint planning (After)<br />Team works with the client to prioritize the items that would be done in this sprint;<br />Items broken into tasks;<br />Evaluating the tasks;<br />Commitment to deliver the sprint;<br />Lots of room for negotiation.<br /><br />20<br />
  21. 21. Sprint planning - Challenges we went through<br />Explaining the value of Scrum;<br />Changing the team spirit;<br />Used to being told what to do;<br />Trusting each other;<br />Make developers to talk together;<br />Working together.<br /><br />21<br />
  22. 22. Sprint planning<br />Sprint 1<br />Sprint planning<br />Story<br />Story<br />Sprint Plan<br />Story<br />Ongoing<br />Done<br />Planned<br />Task<br />Task<br />Story<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br /><br />22<br />
  23. 23. The sprint backlog <br /><br />23<br />
  24. 24. Scrum framework (sprint)<br />Analysis<br /><br />24<br />
  25. 25. Sprint (Before)<br />No such thing as sprint;<br /><br />25<br />
  26. 26. Sprint (After)<br />Fewer features;<br />Better quality;<br />Suitable for the client;<br />Easier to manage;<br />Faster feedback;<br />Team spirit.<br /><br />26<br />
  27. 27. Sprint - Challenges we went through<br />Not every one ready for sprinting;<br />Members still need to be told what to do;<br />Hero personality;<br />Zero personality;<br />Collaboration between team member;<br />Team effort vs individual effort;<br />Team commitment vs individual commitment.<br /><br />27<br />
  28. 28. Scrum framework (Daily Standup)<br />Analysis<br /><br />28<br />
  29. 29. Daily Standup (Before)<br />Not really daily standup;<br />Not for the benefice of the team but rather for the PM management status;<br />Scheduled and driven by the PM.<br /><br />29<br />
  30. 30. Daily Standup(After)<br />For the team;<br />By the team; <br />About the team;<br />For a better product.<br /><br />30<br />
  31. 31. Daily Standup - Challenges we went through<br />PM trying to take control.<br />PM interrupting the team. <br />Members not speaking freely. <br />Focus on what was done yesterday and what will be done today.<br />Keep it short.<br />Keep other discussion for later. <br />
  32. 32. Scrum framework (Product Increment)<br />Analysis<br /><br />32<br />
  33. 33. Product increment (Before)<br /><br />33<br />
  34. 34. Product increment (After)<br />Team decide of the definition of Done;<br />This definition helps up having a potentially shippable product;<br />When ever the PO find it satisfactory, it can be shipped.<br />
  35. 35. Product Increment - Challenges we went through<br /><ul><li>Definition of Done.
  36. 36. Focus on the story, even if the functionality is not complete.
  37. 37. Developer reaction, not adding to much fine tuning.</li></li></ul><li>Framework(Sprint review)<br />Analysis<br /><br />36<br />
  38. 38. Sprint review (Before )<br /><br />37<br />
  39. 39. Sprint review (After )<br />Demo of working functionnality<br />Assist client with future functionality decision<br />Add/remove functionality<br />Change priority<br />Burndown chart<br />Statistics/metrics<br />Risk/Issues<br /><br />38<br />
  40. 40. Sprint review (Challenges )<br />Clients attitude. That’s what I want;<br />Organising the presentation with the client’s busy schedule;<br />Client’s feedback: Focus on important things;<br />Client expectation (not finished functionality?);<br />Controlling developers (planning bugs for next sprint).<br />
  41. 41. Scrum framework (Sprint retrospective)<br />Analysis<br /><br />40<br />
  42. 42. <ul><li>At the end of the project when there is one.</li></ul>Sprint retrospective - Before<br /><br />41<br />
  43. 43. Sprint retrospective - After<br />Retrospection is the heart of Scrum – creating and responding to change about how the team will perform;<br />Retrospective can occur anytime the team feels they need one.<br /><br />42<br />
  44. 44. Questions<br /><br />43<br />