Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Distributed Agile Anti-Patterns

urfolomeus
September 19, 2013

Distributed Agile Anti-Patterns

Talk given by Neo's Paul Wilson and Alan Gardner at Lean Agile Scotland.

In the original Extreme Programming Explained Book, Kent Beck asks a question of Boehm's Cost of Change Curve: what if all that had been learnt over the previous 10 years -- simple design, object oriented programming, programmer tests -- could flatten the curve and move us away from big upfront specification and design? In the same book, he points out the crucial importance of collocating your teams.

What if in the 14 years since the publication of XP Explained, the advances in technology and all we have learnt about running Agile projects means that collocating is no longer the only way to run an XP project? Sure, having all the team members in one room is still optimal but is it micro-optimisation? What if the advantages of distribution (increased flexibility, better quality of life, increased talent-pool) can be made to outweigh the advantages of collocation?
Distributed Agile is not the easy choice, though; there are many pitfalls. In this talk we present some common Distributed Agile anti-patterns, the forces behind them, and the refactored solutions. We will include some great tools and techniques, including superb tips on remote pair-programming.

Distributed Agile: its time has come.

urfolomeus

September 19, 2013
Tweet

Other Decks in Programming

Transcript

  1. Chicago broke the build ... again Yeah I thought they

    were supposed to be a great I don’t think we should risk handing the payment system over to them Tribalism
  2. Why was the build broken last night? Since moving the

    CI server from UK to US we get random fails between midnight UK and midnight US. Must be timezones. Tribalism
  3. Historical Blindness They’re doing recommends in a bizarre way but

    after two days of rewriting I then figured out why! They could have told us!
  4. I don’t like the way they’ve done the latest API

    code. I’m going to rewrite it to fit the way that we do it. Yeah, haven’t they read Insightful Ruby for the Enlightened yet? Not In Our Handwriting
  5. Windy today isn’t it? Three Deaf Ladies So am I,

    let’s have a No, it’s Thursday
  6. City State Then we added the revenue graph to the

    iOS app We saw that - the calculations don’t match the website The customer said they didn’t mind if we use gross or net, but it needs to be consistent I give up
  7. Did you get my designs for the iPhone customer satisfaction

    survey? Yeah, we’re not sure it should be done like that. City State It’s more idiomatic to do it as a single table view.
  8. Privileged Group Did you not get the memo about the

    change to the TPS report headers? Yeah, Bob told us about it at lunch last week But I just took all the TPS Header code out!! Aaaaaaarggghhhh!!
  9. 3am eternal The CI server’s down. How do we get

    access? Chicago set it up But it’s 3am there ZZZZZZZZZZZZ ZZZZZZZZZZ
  10. Castaway ... then The Emperor saw the flat-fish Ha Ha

    Ha What? Anyway, Robinson, don’t let us keep you. We’ll just finish off here. Ok, bye.
  11. Remote Burnout So, I didn’t get that work quite finished

    I find your lack of progress disturbing
  12. Backseat Driver Ok, I’ll just consolidate the duplicate conditional fragments

    Then I’ll replace the nested conditionals with guard clauses No, no no!! Give me a shot. It’s my turn.