Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong Nguyen
•
0 likes•479 views
Recent surveys show that 42% of Agile projects are successful (this is three times better than traditional projects), but 49% of Agile projects are late or over budget, and 9% are even total failures. Some questions raising: • Are the Scrum teams in those projects productive? • Is there any better way to help Scrum teams guarantee the success at the highest effectiveness? On this presentation, we will answer those questions by sharing a comprehensive set of process improvement patterns that will help all Scrum Teams get significantly faster through showing them how to solve problems in a specific context.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong Nguyen
Similar to Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong Nguyen (20)
More from Scrum Breakfast Vietnam
More from Scrum Breakfast Vietnam (20)
Recently uploaded
Recently uploaded (20)
Pattern Language for Team Productivity - Mr. Khoa Le & Mr. Thong Nguyen
- 1. Enjoy your coffee and stay for scrum
- 2. PATTERN LANGUAGE FOR TEAM PRODUCTIVITY
- 4. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Swarming Daily Clean Code Teams that finish early accelerate faster Stable Teams Happiness Metric Yesterday’s Weather
- 5. Stable Teams Stakeholders want to know when the product is estimated to be delivered. Unstable environment just adds costs. Stable teams get benefit.
- 6. www.axon.vnfb.com/AxonActiveVietNam –Stable Teams “Keep teams stable and avoid shuffling people around between teams.”
- 7. www.axon.vnfb.com/AxonActiveVietNam –Stable Teams “Being flexible in shifting people NEED to change to being flexible with work.”
- 8. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Swarming Daily Clean Code Teams that finish early accelerate faster Happiness Metric Yesterday’s Weather Stable Teams
- 9. Yesterday ’s Weather Jeff says that he would not run a Scrum without including this Pattern.
- 10. Velocity There’s no such thing as “Stable Velocity” When it goes up… When it goes down…
- 11. Running Average Velocity Using running average of at least THREE Sprints to calculate the velocity of next Sprint
- 12. Should remember… One-time event is a part of life. Do NOT omit it from the moving average Definition of Done A moving average accommodates the increasing accuracy
- 13. Updated Velocity Shift gears only after you’ve established the ability to crew at a new level
- 14. When that time is… Update the velocity ONLY IF a new level is sustained for the past three sprints. From Takeuchi et al., "Extreme Toyota," Chapter 4
- 15. Yesterday ’s Weather Tool
- 16. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Swarming Daily Clean Code Teams that finish early accelerate faster Happiness Metric Yesterday’s Weather
- 18. Say goodbye to multitasking, because… Multitasking makes you stupid as well as slow. Gives the illusion that things are going faster, but this increases defects.
- 19. www.axon.vnfb.com/AxonActiveVietNam –Swarming “Focus maximum team effort on one item in the Sprint Backlog.” “Whoever takes this item is Captain of the team.” “Everyone must help the Captain if they can and no one can interrupt the Captain.” “As soon as the Captain is done, whoever takes responsibility for the next priority backlog item is Captain.”
- 20. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Daily Clean Code Teams that finish early accelerate faster Happiness MetricSwarming
- 22. Scrum teams are often interrupted during a sprint The Scrum Team is a critical resource for creating new software and maintaining old software. Defects created by the team during a sprint.
- 23. www.axon.vnfb.com/AxonActiveVietNam –Illegitimus Non Interruptus “Allot time for interrupts and do not allow the time to be exceeded.”
- 24. Three Simple Rules 1. The team creates a buffer for unexpected items based on historical data. 2. All requests must go through the product owner for triage. 3. If the buffer starts to overflow, the team should automatically abort.
- 25. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Daily Clean Code Teams that finish early accelerate faster Happiness Metric
- 26. Daily Clean Code
- 27. Daily Clean Code Take time / effort to manage, reproduce and fix bugs Blame and address bug by determining who caused it Low quality and customer is unhappy
- 28. www.axon.vnfb.com/AxonActiveVietNam –Daily Clean Code “Fix all bugs in less than a day. Aim to have a completely clean base of code at the end of every day.”
- 29. Patterns Emergency Procedure Daily Clean Code Scrumming the scrum Teams that finish early accelerate faster Happiness Metric
- 31. Emergency Procedure Rapid identification of problems and quick response Sprint cannot be completed due to unanticipated changes, technical problems Teams act without permission and ask for forgiveness later
- 32. Emergency Procedure Change the way the work is done. Do something differently Get help Reduce scope Inform PO, management how release date will be affected
- 33. Patterns Scrumming the scrum Emergency Procedure Happiness Metric Teams that finish early accelerate faster
- 35. Scrumming The Scrum Use Scrum as a process improvement Identify the most important impediment and remove it Put the improvement to the sprint backlog
- 36. Patterns Scrumming the scrum Happiness Metric Teams that finish early accelerate faster
- 37. Happiness Metric
- 38. Happiness Don’t look for bad people; look for bad systems Make work visible More likely to accomplish far more than you ever anticipated
- 39. Happiness Metric How happy are you with the team ? How happy are you with your own contribution to company ? How happy are you with your own knowledge improvement What would you want to change to increase your happiness
- 40. Happiness Metric
- 43. Teams that finish early accelerate faster Not complete sprint after sprint, people will feel unhappy Rushing development will lead to quality problems and technical debts No time to think clearly how to improve their work
- 44. Teams that finish early accelerate faster Maximize the probability of success by Yesterday’s Weather Implement deal with interruption Increase the probability of acceleration, apply Scrumming the Scrum
- 45. Patterns Scrumming the scrum Emergency Procedure Illegitimus Non Interruptus Swarming Daily Clean Code Teams that finish early accelerate faster Stable Teams Happiness Metric Yesterday’s Weather
- 46. Resources http://www.scrumplop.org/ Scrum The art of doing twice the work in half the time Practices Of An Agile Developer