• Save

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network

Share

Scrumbuts - Italian Agile Day 2010

on

  • 1,812 views

Italian Agile Day 2010

Italian Agile Day 2010
Scrumbuts (DemotiScrum)

Statistics

Views

Total Views
1,812
Views on SlideShare
1,812
Embed Views
0

Actions

Likes
4
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Scrumbuts - Italian Agile Day 2010 Presentation Transcript

  • 1. ScrumBut: Scrum e la resa condizionata? - DemotiScrum -
  • 2. Talking of Scrum in your company...
  • 3. It's not another toy to break off...
  • 4. Edoardo Schepis Scrum Master in Funambol Certified Scrum Master and Scrum Professional [email_address] twitter: edschepis http://www.edschepis.net
  • 5. Agenda
    • Do we really know Scrum?
    • 6. A selection of ScrumButs
    • 7. Surrenders?
  • 8.  
  • 9. Scrum
      Do we really know Scrum? Scrum is NOT...
      • just a matter of meetings
      • 10. just a matter of roles
      • 11. just a matter of artifacts
  • 12. Scrum
      Scrum is not just this...
    or...
  • 13.  
  • 14.  
  • 15. SCRUM is...
      The Scrum Pillars
      • Lean Thinking
        • Respect People
        • 16. Continuous Improvement
        • 17. “ Anything that does not create value for a customer is waste ”
      • Agile Manifesto
      Scrum as a MIRROR
  • 18. Scrum is like your mother in law
  • 19.  
  • 20.  
  • 21. ScrumButs are...
    • ScrumButs are reasons why you can’t take full advantage of Scrum to solve the problems and realise the benefits.
    • 22. Format: (ScrumBut) (Reason) (Workaround)
    • 23. Example:
      • “We use Scrum, but Daily Scrum meetings are too much overhead so we only have them once a week.”
    • Agile development is like teenage sex. Everyone says they’re doing it, but only 10% are. And those who are — ARE DOING IT WRONG.
  • 24. Goalless/Soulless Scrum
      “ We use Scrum but... only because... ”
    • Scrum just for Scrum
    • 25. Scrum because the boss wants it
    • 26. Nobody knows why
  • 27. Goalless/Soulless Scrum – Try to...
    • Use Scrum to govern the Scrum adoption
    • 28. Regularly share and challenge Agile/Lean/Scrum/YOUR values and principles
    • 29. Perform retrospectives on how you're applying Scrum
  • 30. Makes our life difficult
      “ We use Scrum but... we don’t like it because it makes life more difficult. ”
    • It's a Mirror
    • 31. It won't be better with age...
  • 32. Makes our life difficult – Try to...
    • Look into the mirror
    • 33. Inspect and adapt
    • 34. Encourage people
    • 35. Coaching vs. Training
  • 36. Planning Paralysis
      “ We use Scrum but… we're still not confident about our plan after two days of Sprint planning! ”
    • Try to...
      • Keep the focus on the Sprint
      • 37. Find and adapt your velocity
      • 38. Use a checklist for a good Sprint planning meeting
  • 39. http://www.sprint-it.de/scrum-checklists
  • 40. Command and Control
      “ We use Scrum but... a manager keeps telling the team which tasks to do ”
    • It's all about self-organized teams. It doesn't mean:
      • No managers at all
      • 41. No help
    • Try to...
      • define boundaries... like railroads for trains
      • 42. self-organized teams need you!
  • 43. Rewards
      “ We use Scrum but... we track individual performances with rewards ”
    • Is the emphasis really on the team?
    • 44. Try to...
      • Review and assess the goals (Individuals vs. Team)
      • 45. Do not attack the organization mindset
  • 46. It's done... almost done
      “ We use Scrum but... at the end of the Sprint we need additional time to get things done ”
    • Take time to understand and share the issue
    • 47. Try to...
      • Write/Review a Definition of Done
      • 48. Improve your integration systems (continuous build/integration/testing)
      • 49. Sprint Review with live demo
  • 50. Risk Management
      “ We use Scrum but... we need a formal Risk Management process ”
    • Do we really know Scrum?
    • 51. Try to:
      • Review and map risks with scrum principles and practices
      • 52. Time-boxing
      • 53. Prioritization and estimation must consider risks
      • 54. Spikes
      • 55. Last responsible moment
        • A military officer: "The most important thing I did in my career was to teach young leaders that whenever they saw a threat, their first job was to determine the timebox for their response. Their second job was to hold off making a decision until the end of the timebox, so that they could make it based on the best possible data."
  • 56. Risk Management Chart
  • 57. Risk Management mapping
  • 58. Status Quo
      “ We use Scrum but... we have so much work to do (bug fixing, new features, documentation, testing, reporting, managing) that we don't have time to do anything more ”
    • Try to...
      • Inspect: work on failures immediately (pain-driven)
      • 59. Ask the 5 Whys
      • 60. Eat the dogfood
  • 61. Time-boxing what?
      “ We use Scrum but... if needed we extend Sprint lenght ”
    • The illusion of... “just few more hours and it's done”
    • 62. Try to...
      • Overcommitment and/or bad estimates?
      • 63. Track velocity as average from some past sprints
      • 64. Retrospective: missing (lack of) a commitment is an opportunity to inspect and adapt
      • 65. Work with managers to reduce pressure
  • 66. Component Teams
      “ We use Scrum but... we cannot have feature teams ”
    • Communication between teams is easier with feature teams
    • 67. Try to...
      • Define “feature”
      • 68. Keep focus also at feature level (maybe more Sprints)
      • 69. Minimize FIP (features in progress)
      • 70. Empower the team
      • 71. Move from dev. to user point of view
  • 72. Functional Teams
      “ We use Scrum but... we cannot afford cross-functional teams ”
    • Sometimes it's not a management decision
    • 73. Try to...
      • Define primary and seconday skills
      • 74. Reduce WIP
      • 75. Shorten the Sprint
  • 76. Stabilization
      “ We use Scrum but... we still need a Testing/Integration/QA/Release team to validate/finish the work ”
    • DONEish
    • 77. Try to...
      • Work on DONE
      • 78. Improve integration and testing systems
      • 79. Setup automated testing with mocks to avoid dependency
  • 80. The Scrum Monster
      “ We use Scrum but... the Scrum Master is a Manager ” (the SM with two heads)
    • Command and Control
    • 81. Trust?
    • 82. Try to... (if you can't avoid it)
      • Give parts of the role to other members
      • 83. Avoid personal rewards
      • 84. Be a good manager ;-)
  • 85. ScrumButs
    • Goalless
    • 86. Makes our life difficult
    • 87. Planning Paralysis
    • 88. Command and Control
    • 89. Rewards
    • 90. It's almost done
    • 91. Risk Management
    • Status Quo
    • 92. Time-Boxing what?
    • 93. Component Teams
    • 94. Functional Teams
    • 95. Stabilization
    • 96. Scrum Monster
    • 97. ...
  • 98. But Scrum...
      “ When a person/team/organization flips off their 'thinking bit' and just burps up whatever Scrum tells them to do ”
      • But Scrum says all my stories must follow a template: “As a ___ I can ___ so that____”
      • 99. But Scrum says our teams should be 7, +- 2
      • 100. But Scrum says we need self-organizing teams
      • 101. But Scrum says we estimate
    http://blog.versionone.com/blog/productive-agility/0/0/but-scrum Joel Tosi
  • 102. Surrending to the Status Quo?
      La resa incondizionata
        trattato secondo cui una parte accetta di arrendersi al nemico senza avanzare alcun tipo di pretesa (la forma di sconfitta più totale e umiliante per la parte che si arrende)
      L’onore delle armi
        particolare tipo di riconoscimento, un onore cavalleresco che si conferisce in ambito militare per rendere ossequio al valore dell'avversario sconfitto
  • 103.  
  • 104.  
  • 105.  
  • 106.  
  • 107.  
  • 108.  
  • 109. we all grow up...
  • 110.  
  • 111. Edoardo Schepis Scrum Master in Funambol Certified Scrum Master and Scrum Professional [email_address] twitter: edschepis http://www.edschepis.net Questions?