4. 2012 survey by 4000+ respondents

5. 2012 survey by

6. Primavera: Results
•
•
•
•

8. Final: over 600 million viewers worldwide

9. 3.4 billion pageviews in 1 month

10. Year long project, 2-wk sprints 10

11. Europe: 2008 Major Sports Event Schedule
Euro
Paris-Dakar Tour de France
January February March April May June
Rugby 6 Nations Rolland Garros Wimbledon
“Minor” Events:
Football: Moto GP Boxing
Olympic qualifiers Golf, Athletics, Cycling Horse Racing
11
28-Mar-13 World Cup qualifiers Basketball Hockey, etc

12. Scrum Adoption at
• 2004: One person experimented with scrum
• 2005: VP of Product Development hired Senior Director of Agile Development
• 2008:
3 coaches, each coaching approx. 10 scrum teams/year
200 scrum teams world wide, total approx. 1500+ employees
• Results in 2008:
Average Team Velocity increase estimated at +35% / year,
in some cases 300% - 400%
Development cost reduction of over USD 1 million / year
ROI on transition and trainings about 100% in first year
• Note: In first three years, 15-20% of people consistently DID NOT like Scrum
Source: Gabrielle Benefield http://agilesoftwaredevelopment.com/blog/artem/lessons-yahoos-scrum-adoption
12

13. 3 MONTHS
Scrum vs. Waterfall: Time ToFaster Time to Market

Market
 Higher Quality
 Satisfied Customer
Scrum
Collaborative
Develop & QA Results-Oriented
Spec
6-10 MONTHS
9 weeks
Waterfall 3 months
Spec Develop & QA Updates
12 weeks 3-6 wks
x wks y wks
6-10 months
Sequential
Process-Oriented
© Silvana Wasitova

18. http://webwhiteboard.com

19. Why Scrum Works
1. Close collaboration with client / proxy
=> better solution, better buy-in
2. Transparency through daily reviews:
=> early visibility of issues
=> early resolution
=> risk reduction
3. LEAN ‘flow’: frequently delivering
business value in small increments
4. Eliminate waste, focus on highest
priorities
5. Inspect, adapt, improve: in each iteration

20. http://www.poppendieck.com/

21. Ziv’s Law: • Specifications will never be fully understood
• The user will never be sure of what they want
Humphrey’s Law: until they see the system in production (if then)
• An interactive system can never be fully
Wegner’s Lemma: specified, nor can it ever be fully tested
• Software evolves more rapidly as it approaches
Langdon’s Lemma: chaotic regions (without spilling into chaos)

22. Agile Philosophy

23. The Agile Manifesto
http://www.agilemanifesto.org

24. Waterfall, Agile and Scrum: Characteristics
When is a project a “Scrum Project” and when is it not?
Waterfall Agile : Iterative Development
Scrum
Specifications Upfront, Detailed Emergent Design
• Daily “standup” status checks ≤ 15mins
• Delivery rhythm in iterations (Sprints)
• Demo & Retrospective at end of ea. Sprint
Linear hand-offs: Cross-functional &  Continuous Improvement
Teamwork Dev then QA collaborative: Dev & QA
XP: eXtreme
Change Formal process, Welcomed,
Requests implemented at end prioritized vs. backlog Programming
• Automated Tests
• Pair Programming
Customer / User At beginning and • Automated / Continuous Builds
• TDD: Test-Driven Development
Involvement at delivery Throughout cycle • Continuous Deployment
RUP DSDM
Scrum is the most popular Agile method:
74% of Agile practitioners (2009)
28-Mar-13 24 24

25. Scrum Framework

26. Scrum Framework: Summary
Product Owner Product Backlog Product Planning
Team Sprint Backlog Sprint Planning
Scrum Master Potentialy Shippable Daily Scrum
Product Sprint Review
Burn-down Chart Retrospective
Cardinal Rule: Work on the highest priority item first

27. Photo credit: http://www.flickr.com/photos/tomnatt/

31. 2012 survey by

33. Criteria Scrum Candidate Waterfall
What To Build or Iterate to clarify
Both are known
How to Build it direction / details
Market or User
Want Market/User input User/Market input
Feedback and
to improve usability not needed
Involvement
Time to Market vs.
Flexible about Scope Flexible about Time
Feature Content
Minimum Start: project over 30 days of duration

34. http://www.infoq.com/news/2007/09/why-do-agile-adoptions-fail

37. Silvana Wasitova, PMP, CSM, CSP
wasitova@yahoo.com
slideshare.com/wasitova

38. http://blog.jackvinson.com/archives/2010/12/31/resilience_-_managing_at_the_speed_of_change.html
• “The New New Product Development Game” Takeuchi and Nonaka. Harvard Business Review, January 1986
http://www.mountaingoatsoftware.com
http://www.agilealliance.org
http://www.agilealliance.hu/index.php/ProfessonalMaterials/169
http://www.infoq.com/news/2007/09/why-do-agile-adoptions-fail
http://www.c-spin.net/2009/cspin20090204AgileTransformationAtBorland.pdf