Published on

This introductory presentation shows the basics of Scrum software development framework.

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Activity: Step Production Company
  • Left col: GlobalRightcol: Vietnam Located Company & VN Corp.
  • The Scrum framework
  • 3 legs of Scrum
  • Relates Retro ~ Kaizen
  • Technical staffs don’t like meetings, but meetings are usefullet’s make it funnierTool: stopwatch, ball, etc.
  • Show some template
  • Table : Deemer et al.
  • Introduce Planning Poker: deck cards and software (web, android, iOS) (comparative planning)
  • Table & image: Deemer et al.
  • Shows the Team their progress towards their goalThe importance is how much work remains in the future, not how much effort spent in the pastChart: Deemer et al.
  • Scrum

    1. 1. Scrum<br />Transforming the world of work<br />Duong Trong Tan (CSM)<br />Hanoi, Mar. 2011<br />
    2. 2. Agenda<br />On chaos and effectiveness<br />What is Scrum?<br />Three Core Values<br />Three Roles of Scrum<br />Operate Scrum<br />Joining Scrum Users Community<br />2<br />
    3. 3. Chaos and effectiveness<br />In chaos, people still walk effectively<br />Photo:<br />3<br />
    4. 4. Scrum history<br />Jeff Sutherland<br />Initial scrums at Easel Corp in 1993<br />IDX and 500+ people doing Scrum<br />Ken Schwaber<br />ADM<br />Scrum presented at OOPSLA 96 with Sutherland<br />Author of three books on Scrum<br />Agile Alliance 2001<br />Scrum Alliance in 2002<br />4<br />
    5. 5. What is Scrum?<br />Scrum Is an Innovative Approach to Getting Work Done<br />Scrum is an agile framework for completing complex projects. <br />It focuses on delivering the highest business value in the shortest time.<br />Scrum is based on agile software development principles and values<br />Teams in Scrum are self-managed<br />5<br />
    6. 6. Who use Scrum?<br />6<br />
    7. 7. Scrum Framework<br />7<br />
    8. 8. 3 Core Values<br />Transparency<br />Adapt<br />Inspect<br />8<br />Dùainóingảnóinghiêng<br />Lòngtavẫnvữngnhưkiềngbachân<br />
    9. 9. The Agile Manifesto <br />We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:<br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Customer collaboration over contract negotiation<br />Responding to change over following a plan<br />9<br />That is, while there is value in the items on the right, we value the items on the left more.<br /><br />
    10. 10. 3 Roles<br />Product Owner<br />responsible for the business value of the project <br />ScrumMaster<br />ensures that the team is functional and productive <br />Scrum Team<br />self-organizes to get the work done <br />10<br />
    11. 11. Scrum Process Overview<br />Image:<br />11<br />
    12. 12. Deemer el al.<br />12<br />
    13. 13. 4 Ceremonies<br />Sprint Planning<br />the team meets with the product owner to choose a set of work to deliver during a sprint <br />Daily Scrum<br />the team meets each day to share struggles and progress <br />Sprint Reviews<br />the team demonstrates to the product owner what it has completed during the sprint <br />Sprint Retrospectives<br />the team looks for ways to improve the product and the process. <br />13<br />
    14. 14. Activity: Daily Meeting<br />Photo:<br />14<br />
    15. 15. 3 Artifacts<br />Product backlog<br />prioritized list of desired project outcomes/features <br />Sprint backlog<br />set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks <br />Burndownchart<br />at-a-glance look at the work remaining (can have two charts: one for the sprint and one for the overall project) <br />15<br />
    16. 16. Product Backlog<br />Requirements<br />Items valued to users & customers<br />Prioritized and maintained by the Product Owner<br />16<br />
    17. 17. Estimation in Scrum<br />17<br />
    18. 18. Sprint Backlog<br />Plan and tracking tool for a sprint<br />Maintained by the team<br />18<br />
    19. 19. Burndown Chart<br />19<br />
    20. 20. Scrum Obstacle<br />According to Bas Vodde:<br />The illusion of command and control <br />The persistence of status-quo <br />The mediocracy of ScrumBut<br />The belief in magic <br />The era of opacity <br />The tyranny of the waterfall.<br />20<br />
    21. 21. Causes of failure<br />Ineffective use of retrospective <br />Inability in getting all people in planning meeting <br />Failure to pay attention to the infrastructure required <br />Bad ScrumMaster<br />Product Owner is consistently unavailable <br />Failure to push testing forward <br />Reverting to form <br />Obtaining only "checkbook commitment" from executive management <br />Teams lacking authority and decision making ability <br />Not having onsite evangelist for remote location <br />Cultures that do not support learning <br />Denial is embraced instead of brutal truth<br />Jean Tabaka<br />21<br />
    22. 22. Scrum Community<br />Global community:<br />Ho Chi Minh City:<br />Ha Noi City: Gathering Soon…<br />22<br />
    23. 23. References and Resources<br />Jean Tabaka, Twelve ways agile adoption failed, Better Software, Nov. 2007, (<br />Mountain Goats, Scrum Overview, (<br />MoutainGoats, Planning Poker Estimating in details (<br />Scrum Alliance ,<br />Scrum Alliance, What is Scrum? (<br />Pete Deemer, Gabrielle Benefield, Craig Larman & Bas Vodde, Scrum Primer ver. 1.2<br />Tan, practices-of-agile-developers (PPT slide: )<br />23<br />
    24. 24. Books<br />24<br />