Scrum Introduction Vietnam
â˘Als PPTX, PDF herunterladenâ˘
4 gefällt mirâ˘1,794 views
Ken Schwaber gave the first time an introduction into Scrum at the agile vietnam forum in November 2011.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (13)
Ăhnlich wie Scrum Introduction Vietnam
Ăhnlich wie Scrum Introduction Vietnam (20)
Mehr von Agile Vietnam
Mehr von Agile Vietnam (18)
KĂźrzlich hochgeladen
KĂźrzlich hochgeladen (20)
Scrum Introduction Vietnam
- 1. Scrum for Vietnam A man who carries a cat by the tail learns something he can learn in no other way. - Mark Twain Ken Schwaber November 17, 2011 Copyright Scrum.org 2011 Slide 1
- 2. The Right Process Produces the Right Results The CHAOS Manifesto, Copyright 2011 November 17, 2011 Copyright Scrum.org 2011 Slide 2
- 3. The Right Process Produces the Right Results âThe agile process is the universal remedy for software development project failure. Software applications developed through the agile process have three times the success rate of the traditional waterfall method and a much lower percentage of time and cost overruns. The secret is the trial and error and delivery of the iterative process.â The CHAOS Manifesto, Copyright 2011 November 17, 2011 Copyright Scrum.org 2011 Slide 3
- 4. Are you using Scrum?
- 5. FBI Case Management Project (Sentinel) ⢠2006: Sentinel project awarded to Lockheed Martin, 4 phases, $450m, 6 years. ⢠2010, after four+ years, $421 spent and 1st phase and part of 2nd done. Mitre estimates another $351m and 6 years to complete. ⢠FBI stops contract and brings in house. ⢠Scrum studio in Hoover building basement, reduce staff from 400 to 40. ⢠Project done in 1 year for $30m. ⢠www.justice.gov Inspector General reports
- 6. Professional Scrum at Scrum.org Professional Professional Professional Scrum Scrum Master Scrum Product Owner Developer .NET or Java Architects Product Owners Scrum Masters Business Analysts Executives and DB Specialists Advanced Advanced Designers Practitioners Practitioners Programmers Testers Professional Scrum Foundations Everyone
- 7. Vietnam PSM Course http://courses.scrum.org/classes/show/498
- 8. Risk is reduced to one Sprint The same work, but organized differently and on fewer requirements. Waste becomes hugely visible and can be systematically removed. Time
- 9. Empirical Processes Plan Frequently P Planning D Doing ⢠Predictive ⢠Empirical All planning is done at Just-in-time planning and beginning re-planning based on frequent inspection P D P D P D P D P D
- 10. Scrum is a Tool used to Become Agile Scrum Short, high value iterations that deliver valuable, opportunistic pieces of functionality. ⢠Work done by self-organizing, cross- functional teams. ⢠Highly productive, creative, and delivering high quality product. Scrum Team
- 11. Visibility Ability to Change Business Value Risk
- 12. Scrum (n): A framework within which people can address complex problems, and productively and creatively deliver products of the highest possible value. ⢠Lightweight ⢠Extremely simple to understand ⢠Extremely difficult to master
- 13. 3 Types of Content in Scrum Roles Artifacts Events ⢠Product ⢠Increment ⢠Sprint Owner ⢠Product ⢠Sprint ⢠Development Backlog Planning Team ⢠Sprint ⢠Daily Scrum ⢠Scrum Backlog ⢠Sprint Master Review ⢠Retrospective
- 14. Roles: each one has a specific responsibility Development ⢠Manages itself Team ⢠Delivers âDoneâ Increments Product ⢠Optimizes value of the Product Owner ⢠Manages the Product Backlog Scrum ⢠Manages the Scrum Process Master ⢠Removes Impediments
- 15. Roles ⢠Product Owner Sprint ⢠Development Review Daily Scrum Team ⢠Scrum Master Increment Artifacts Retrospective ⢠Product Backlog ⢠Sprint Backlog Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus nibh dui, rutrum non interdum sed, porttitor non augue. Morbi adipiscing vulputate diam nec blandit. Aenean sed viverra magna. Pellentesque ac quam velit. Cras pharetra, urna nec mattis interdum, tortor orci iaculis tellus, nec lobortis sapien justo quis felis. In hac habitasse platea dictumst. Phasellus posuere cursus lacus, non congue massa fringilla ⢠Increment eu. Sed viverra vulputate quam, in aliquam nulla Sprint tincidunt at. Sed posuere est at nisl cursus mollis. Aliquam erat volutpat. Curabitur pretium turpis vel nibh adipiscing sed molestie eros euismod. Pellentesque pretium sagittis ipsum, vitae condimentum risus hendrerit eu. Cras ullamcorper massa in eros lobortis sodales. Integer ultrices molestie turpis nec cursus. Etiam tempor vestibulum mollis. Sed dictum condimentum nibh, eget tincidunt libero sodales ac. Aliquam sed justo nisl, eu mollis justo. Curabitur egestas libero nec quam fringilla bibendum. Ut hendrerit quam et nibh volutpat Events vitae pretium erat scelerisque. Phasellus id est est. Sprint ⢠Sprint Backlog ⢠Sprint Planning ⢠Daily Scrum ⢠Sprint Review Lorem ipsum dolor sit amet, consectetur Sprint adipiscing elit. Phasellus nibh dui, rutrum non interdum sed, porttitor non augue. Morbi adipiscing vulputate diam nec blandit. Aenean sed viverra magna. Pellentesque ac quam velit. Cras pharetra, urna nec mattis interdum, tortor Planning ⢠Retrospective orci iaculis tellus, nec lobortis sapien justo quis felis. In hac habitasse platea dictumst. Phasellus posuere cursus lacus, non congue massa Meeting fringilla eu. Sed viverra vulputate quam, in aliquam nulla tincidunt at. Sed posuere est at nisl cursus mollis. Aliquam erat volutpat. Curabitur pretium turpis vel nibh adipiscing sed molestie eros euismod. Pellentesque pretium sagittis ipsum, vitae condimentum risus hendrerit eu. Cras ullamcorper massa in eros lobortis sodales. Integer ultrices molestie turpis nec cursus. Etiam tempor vestibulum mollis. Sed dictum condimentum nibh, eget tincidunt libero sodales ac. Aliquam sed justo nisl, eu mollis justo. Curabitur egestas libero nec quam Product Scrum fringilla bibendum. Ut hendrerit quam et nibh volutpat vitae pretium erat scelerisque. Phasellus id est est. Product Owner Dev. Team Master Backlog
- 16. Scrum Review November 17, 2011 Copyright Scrum.org 2011 Slide 16
- 17. Scrum Shields Projects From Complexity Scrum Scrum creates container within which complexity can be transformed into product increments.
- 18. Next Steps Stay Connected Subscribe to our RSS feed to receive the latest updates on scrum.org programs, training, and certifications. http://www.scrum.org/news/rss.xml Follow us on Twitter, our username is @scrumdotorg Engage Join the Yahoo! discussion group where you can tap into the collective knowledge of Scrum users around the world. http://groups.yahoo.com/group/scrumdevelopment/ If you achieve PSPO certification you are eligible to join the LinkedIn group to continue the conversations with the people youâve met in this class, and start new ones with other PSPOs. November 17, 2011 Copyright Scrum.org 2011 Slide 18
- 19. Thank you! Ken Schwaber ken.schwaber@scrum.org @kschwaber kenschwaber.wordpress.com www.scrum.org November 17, 2011 Copyright Scrum.org 2011 Slide 19
Hinweis der Redaktion
- Scrum is the most widely used agile method. Note that 3 of these methods in this survey result have the word âScrumâ in them.
- Ability to ChangeAdaptability goes down over time, regardlessAgile enables higher adaptability longer With pluggable architectures encouraged by frequent delivery With encouraging the business decision makers to change their minds as they learn more about the market being sold toIn the beginning, if what is being created is the INFRASTRUCTURE, the investment needs to be protected from change. Adaptability goers down quickly as specs are frozen.In agile, priorities may be changed and architectures may be refactored, resulting in systems that stay more adaptable longerRiskThe risk of making the wrong thing In plan-driven, customers may not see the product until is is ready for release Agile solicited feedback all along the way on features that are fully bakedThe risk of missing an important featureIn plan driven, risk is mitigated by strict change control. In Agile, risk is mitigated by iterating to the correct answer. There is never more than a single iteration of work at rick at a time.