Your SlideShare is downloading. ×
0
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

885

Published on

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

Published in: Technology, Self Improvement
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
885
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
37
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×