Your SlideShare is downloading. ×
0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Scrum is not enough v2.0
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum is not enough v2.0

1,803

Published on

My presentation about how Scrum is not enough for solving the problems a well-executed Scr

My presentation about how Scrum is not enough for solving the problems a well-executed Scr

Published in: Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,803
On Slideshare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
49
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Scrum Is Not Enough v2.0 or A few stumbling blocks that many companies have encountered with Scrum Ari Tanninen Agile Saturday, Estonia, May 15th Friday, May 14, 2010
  • 2. Ari Tanninen Software engineer, freelance agilist Decade of product development Telecom, on-line gaming, startups Currently ScrumMaster & lead designer Six years agile, three years Scrum Five Scrum projects, coach in three Friday, May 14, 2010
  • 3. Hello, who are you? Friday, May 14, 2010
  • 4. Scrum is great! • Individuals: clarity, pride, and joy in work • “Move task to done, go home.” • Companies: good projects, high quality, time to market • Agile is the best way to build software (that I know of) Friday, May 14, 2010
  • 5. Scrum in a nutshell Friday, May 14, 2010
  • 6. Scrum is simple but difficult. It’s greatest benefit is that it surfaces problems, but Scrum is not enough to solve them. Many companies fail with Scrum because solving problems is difficult and change is painful. More companies would succeed with Scrum if they would anticipate or avoid some of the problems. Friday, May 14, 2010
  • 7. Scrum is simple • Minimalistic framework: demands little • Multi-purpose • Surfaces problems • Catalyst for improvement and change (if done correctly) Friday, May 14, 2010
  • 8. Scrum is difficult • Minimalistic framework: no toolbox • Depends on change in thinking, culture, organization structure • Depends on trust, collaboration, teamwork • Assumes goals, strategy, leadership Friday, May 14, 2010
  • 9. Typical problems Friday, May 14, 2010
  • 10. Broken team Friday, May 14, 2010
  • 11. Broken team do es eam form • Unclear purpose and goal T t no • Missing skillsets ne • Part-time members do ing gs ait in w th nd • Distributed ingys a tt la ge e n ot to d due Friday, May 14, 2010
  • 12. Broken Missing team teamwork Friday, May 14, 2010
  • 13. Missing teamwork • Cross-functional team, full-time members, clear goal, yet: • Little collaboration pe Po • Low energy rf or or ma nc • Unhappy team members e • Inattention to results Friday, May 14, 2010
  • 14. Team vs. group 1. Do we trust each other? 2. Dare we communicate openly? 3. Do we understand our shared goals? 4. Are we truly dedicated to achieving these goals? 5. Can we solve our differences? 6. Is everyone participating? 7. Do we enjoy being a part of this team? Friday, May 14, 2010
  • 15. Broken Missing team teamwork Inadequate skills for agile development Friday, May 14, 2010
  • 16. Inadequate skills for agile development • Team working fine, good energy, yet: • Software not “done” • Refactoring sprints Software collapses • Bugs • Frustration project doomed Friday, May 14, 2010
  • 17. From Waterfall to Agile Analysis Design Impl. Testing Deploying February March April May June A D I T D A D I T D A D I T D A D I T D A D Friday, May 14, 2010
  • 18. Specification Analysis GUI Architecture Design k s ! W e e Implementation 1 -4Testing Integration Packaging Deploying Documentation Handover Friday, May 14, 2010
  • 19. Missing skills • Automated regression testing • Version control • Incremental architecture, GUI design, testing... • Test-Driven Development, Refactoring, Continuous Integration • Task planning, self management, discipline Friday, May 14, 2010
  • 20. Friday, May 14, 2010
  • 21. The Product Owner role Broken Missing team teamwork Inadequate skills for agile development Friday, May 14, 2010
  • 22. The Product Owner role • “How do I prioritize the Product Backlog?” • “Figure it out!” • No customer contact • Unable to answer team’s questionswrong the uilt • Frustration At pr best t is b oduc Friday, May 14, 2010
  • 23. Business model Stakeholder Scrum v. 2.0 v. 1.0 Q2 Q3 Q4 Q1 Scheduling Developers Domain Acme Customers Product End users Friday, May 14, 2010
  • 24. Friday, May 14, 2010
  • 25. Organizational silos The Product Owner role Broken Missing team teamwork Inadequate skills for agile development Friday, May 14, 2010
  • 26. Organizational silos • Scrum running fine, teams happy, still: • Not much gets done Not rouvceh enal m re m t • Teams lack support imp • Turf wars between units “Scrum does not work” Friday, May 14, 2010
  • 27. Accounting Projects IT Product development Acme Friday, May 14, 2010
  • 28. Organizational silos The Product Missing or Owner role wrong goals Broken Missing team teamwork Inadequate skills for agile development Friday, May 14, 2010
  • 29. Missing or wrong goals • “Our goal is to be agile” • “What are we doing and why?” • Missing success criteria • Missing business drivers • No buy-in No change Failure Friday, May 14, 2010
  • 30. Organizational silos The Product Missing or Owner role wrong goals Broken Missing team teamwork Inadequate skills for agile development Friday, May 14, 2010
  • 31. Managed Product organization Business management drivers for in check Scrum Good Teamwork team Good agile development skills Friday, May 14, 2010
  • 32. Done correctly Scrum helps you to succeed. Scrum will not solve problems for you, you need a plan for solving them. Keep your eyes open, and good luck! Friday, May 14, 2010

×