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.
Even more Agile

 Chris Stevenson & Deven Tolia
Agenda

• Agile processes stress the importance of
  continual reflection
• We will describe how we have recently
  refacto...
Short History
• ThoughtWorks’ first agile project
• Old, large legacy codebase
• Complex domain
• Iterative – but quite hea...
What were the
        problems?
• Long story card lifecycle (~2 months)
• Too many bugs
• Team growing in size
• Distribut...
How did we
        address them?
• Enable Better Practices
• Make Progress Visible
• Improve Developer Productivity
• Fost...
Enable Better Practices

• Team owns cards
• Pairing – not just pair programming
• Smaller and Co-located teams
• Emphasis...
Make Progress Visible

• Build Tower
• Story Walls
• Colored cards
• Master story wall
• ... you can’t fix it if you can’t ...
Improve developer
       productivity
• Fast development machines
• Linux
• Refactor the build
• Productivity cards
• ... ...
Foster Communication
• Ambassadors
• Open furniture
• Anybody can contact any client
• Lunch-time domain sessions
• ... co...
Make it more

• Team outings
• Pizza for IPMs
• Ice cream for successes
• AoE forever
What’s not working?
         (yet)
• Automated functional testing
• Rotation across teams
• Induction
• Privacy/noise
• .....
So...

• Making visible progress
• Customer trusts us
• Team morale is much higher
• Productivity is much better
• ... we ...
How do we feel now?




       Q &A
Upcoming SlideShare
Loading in …5
×

Even More Agile

1,085 views

Published on

Chris Stevenson & Deven Tolia presentation on scaling agile in an offshore context

Published in: Technology, Self Improvement
  • Be the first to comment

Even More Agile

  1. 1. Even more Agile Chris Stevenson & Deven Tolia
  2. 2. Agenda • Agile processes stress the importance of continual reflection • We will describe how we have recently refactored the process of one of our oldest agile projects
  3. 3. Short History • ThoughtWorks’ first agile project • Old, large legacy codebase • Complex domain • Iterative – but quite heavy process • Distributed – large team in India • Beta release approaching
  4. 4. What were the problems? • Long story card lifecycle (~2 months) • Too many bugs • Team growing in size • Distributed team – communication • Developer productivity problems – slow build time • ... low morale
  5. 5. How did we address them? • Enable Better Practices • Make Progress Visible • Improve Developer Productivity • Foster Communication • Make it more fun
  6. 6. Enable Better Practices • Team owns cards • Pairing – not just pair programming • Smaller and Co-located teams • Emphasis on testing • Efficient stand-ups
  7. 7. Make Progress Visible • Build Tower • Story Walls • Colored cards • Master story wall • ... you can’t fix it if you can’t see it
  8. 8. Improve developer productivity • Fast development machines • Linux • Refactor the build • Productivity cards • ... it all boils down to “Reduce waste”
  9. 9. Foster Communication • Ambassadors • Open furniture • Anybody can contact any client • Lunch-time domain sessions • ... communication is the single biggest problem for a distributed project
  10. 10. Make it more • Team outings • Pizza for IPMs • Ice cream for successes • AoE forever
  11. 11. What’s not working? (yet) • Automated functional testing • Rotation across teams • Induction • Privacy/noise • ... but we are still refactoring
  12. 12. So... • Making visible progress • Customer trusts us • Team morale is much higher • Productivity is much better • ... we are having fun!
  13. 13. How do we feel now? Q &A

×