際際滷

際際滷Share a Scribd company logo
Identifying Scrum Failure Patterns Studying FAIL to help us do better next time     Steve Dalton  http://refactor.com.au
Who is Steve Dalton? Software Engineer Doing Agile/XP since 2000 CSM in June 2008 Passionate about networking and love being a "connector" Co-founder of Refactor - Agile Software Consultancy based on Gold Coast   http://twitter.com/spidie http://linkedin.com/in/dalton
"Experience is simply the name we give our mistakes." - Oscar Wilde
Format of presentation Some common Scrum failure patterns in small companies Product Owner Organisational Team Some general tips Questions/Discussion
1. No/Bad Product Owner Poor domain knowledge Reluctance to give written requirements Politics Them/Us mentality Lack of process or process for no apparent reason (eg. TPS reports)
2. Organisational Issues  Role clarity - too many hats Dedicated resources Funding Line management Poor working environment
3. The Team Not doing Standups  "Carrying" weak members Toxic team members Over-protective team members Testers not fully engaged Reluctance to use new methods (eg. TDD, XP)
What to do Recognise when you are in a failure mode and act FAST Scrummasters - ASK THE TEAM!  Don't be scared of wearing the Black Hat .  ALWAYS, ALWAYS do retrospectives. Make them interesting, mix them up a bit. Remember: Inspect & Adapt STAND UP to management. It may get you fired... but it feels damn good and you will be a better person in the long run! It's frustrating, but if all else fails....
Go in for a little anger management or do a presentation at a meetup on it..
Saturday 29th November Rooms 1.18/1.19, Building G30 Griffith Uni, Southport Campus Learn stuff, meet people, have fun!  http://barcamp.org/BarCampGoldCoast

More Related Content

Scrum Failure Modes in Small Business

  • 1. Identifying Scrum Failure Patterns Studying FAIL to help us do better next time Steve Dalton http://refactor.com.au
  • 2. Who is Steve Dalton? Software Engineer Doing Agile/XP since 2000 CSM in June 2008 Passionate about networking and love being a "connector" Co-founder of Refactor - Agile Software Consultancy based on Gold Coast http://twitter.com/spidie http://linkedin.com/in/dalton
  • 3. "Experience is simply the name we give our mistakes." - Oscar Wilde
  • 4. Format of presentation Some common Scrum failure patterns in small companies Product Owner Organisational Team Some general tips Questions/Discussion
  • 5. 1. No/Bad Product Owner Poor domain knowledge Reluctance to give written requirements Politics Them/Us mentality Lack of process or process for no apparent reason (eg. TPS reports)
  • 6. 2. Organisational Issues Role clarity - too many hats Dedicated resources Funding Line management Poor working environment
  • 7. 3. The Team Not doing Standups "Carrying" weak members Toxic team members Over-protective team members Testers not fully engaged Reluctance to use new methods (eg. TDD, XP)
  • 8. What to do Recognise when you are in a failure mode and act FAST Scrummasters - ASK THE TEAM! Don't be scared of wearing the Black Hat . ALWAYS, ALWAYS do retrospectives. Make them interesting, mix them up a bit. Remember: Inspect & Adapt STAND UP to management. It may get you fired... but it feels damn good and you will be a better person in the long run! It's frustrating, but if all else fails....
  • 9. Go in for a little anger management or do a presentation at a meetup on it..
  • 10. Saturday 29th November Rooms 1.18/1.19, Building G30 Griffith Uni, Southport Campus Learn stuff, meet people, have fun! http://barcamp.org/BarCampGoldCoast

Editor's Notes

  • #2: Identify Scrum Failure patterns that is the presentation You need to have much stronger presence starts with why you are standing up Okay I am going to talk to you about the 3 / 4 main failure patterns in Scrum that I have experienced See where I am going with this right that means you need 10 slides opening statement Product owner
  • #5: Show of hands - who has NOT ever been part of a project that was a failure.
  • #6: Apologies for "Office Space" pictures to those who haven't seen the film.
  • #9: Show of hands - who has done retrospectives. Show of hands on 6 thinking hats maybe. Show Agile Retrospectives Book.