scrum failure modes in small business
DESCRIPTION
Presentation given at Brisbane Scrum meetupTRANSCRIPT
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/spidiehttp://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 companieso Product Ownero Organisationalo 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 NovemberRooms 1.18/1.19, Building G30Griffith Uni, Southport Campus
Learn stuff, meet people, have fun!
http://barcamp.org/BarCampGoldCoast