Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011


Published on

Rachel Davies' slides from Northampton IIBA event in August

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Common challenges in adopting Agile: IIBA Northampton event 23rd August 2011

  1. 1. Common Challenges in Adopting Agile by Rachel Davies About you ..Are you:• New to agile?• Practicing?• Expert? © Agile Experience Ltd 1
  2. 2. Traditional WaterfallPhases of activity focused on a fixed-scope release.• Divide the work up• Resist change• Communicate via documents © Agile Experience Ltd Agile is not speeding this up• Agile is not a case of “do less, go faster”• Mistake to focus on replacing:- – Process – Role descriptions – Tools – Templates – Training © Agile Experience Ltd 2
  3. 3. Agile ManifestoShared values and principles for better ways to develop software (2001) © Agile Experience Ltd Individuals and interactions over processes and tools © Agile Experience Ltd 3
  4. 4. Working softwareover comprehensive documentation © Agile Experience Ltd Customer collaboration over contract negotiation © Agile Experience Ltd 4
  5. 5. Responding to change over following a plan © Agile Experience Ltd Key Agile Principles• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software• Welcome changing requirements, even late in development.• Business people and developers must work together daily throughout the project• The most efficient and effective method of conveying information to and within a development team is face-to- face conversation. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. © Agile Experience Ltd 5
  6. 6. Agile is .. Concurrent activity to create continuous flow of releases. • Develop iteratively • Cross-functional teams • Frequent releases © Agile Experience Ltd Potential Benefits• Deliver change more quickly (smaller releases)• More confidence in delivery dates (testing done throughout)• Improved employee retention (motivating work)• Better solutions (user feedback folded in) © Agile Experience Ltd 6
  7. 7. But ..• Products may not be easy to break into incremental releases.• Pipeline to live may be constrained.• Iterative development feels like rework.• Reorganising into cross-functional teams is challenging especially when key functions are outsourced. © Agile Experience Ltd Agile depends on TeamworkReal-time interactions rather than processorchestrated via artefacts. © Agile Experience Ltd 7
  8. 8. Teamwork relies on Motivation• Make vision and benefits clear• Permission to try new approach• Empower team to make choices about how they work• Build awareness and responsibility © Agile Experience Ltd New Skills Take TimeBecoming agile requires:• Understanding principles• Time to practice• Coaching to avoid old habits © Agile Experience Ltd 8
  9. 9. Support across the organisationAgile can have impact on many areas:• Hiring policy• Line management• Incentives• Operations• Office Furniture © Agile Experience Ltd Further ReadingMike Cohn – “Succeeding with Agile”Rachel Davies Liz Sedley – “Agile Coaching”James Shore Shane Warden – “The Art of Agile Development” © Agile Experience Ltd 9
  10. 10. Any Questions?Get in touch – Email: – Twitter: @rachelcdavies – Blog: – Web: © Agile Experience Ltd 10