Ce diaporama a bien été signalé.
Le téléchargement de votre SlideShare est en cours. ×

Jumping off the waterfall

Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Publicité
Chargement dans…3
×

Consultez-les par la suite

1 sur 28 Publicité

Jumping off the waterfall

Télécharger pour lire hors ligne

Jumping off the waterfall - watch out for the rocks below!

As agile adoption grows, more and more companies are finding themselves trying to transition from a waterfall-based product development approach to a more agile one. Success stories are easy to find from the great companies who get it right first time, but for most us that won't sound like our story. We'll take more than a few stumbles along the path and wonder what it is about us or our specific situation that means we're finding it so hard.

Having led this transition within some of Ireland's busiest websites, we did parts of it well, but I'm going to focus more on the stuff we got very wrong - decisions we made that at the time seemed like both the smart and low risk thing to do but ended up being neither!

It'll hopefully be a useful guide to potential pitfalls along the route if you're starting out on the same journey. And if you've already been through it, you may recognise more than a few of the rocks we hit along the way!

The slides themselves are mainly intended as an aid for when I'm talking and may not work so well for anyone who didn't see the talk! So I've expanded on my notes from the talk at http://www.conroyp.com/2014/10/21/jumping-off-the-waterfall-agile-transition/.

Jumping off the waterfall - watch out for the rocks below!

As agile adoption grows, more and more companies are finding themselves trying to transition from a waterfall-based product development approach to a more agile one. Success stories are easy to find from the great companies who get it right first time, but for most us that won't sound like our story. We'll take more than a few stumbles along the path and wonder what it is about us or our specific situation that means we're finding it so hard.

Having led this transition within some of Ireland's busiest websites, we did parts of it well, but I'm going to focus more on the stuff we got very wrong - decisions we made that at the time seemed like both the smart and low risk thing to do but ended up being neither!

It'll hopefully be a useful guide to potential pitfalls along the route if you're starting out on the same journey. And if you've already been through it, you may recognise more than a few of the rocks we hit along the way!

The slides themselves are mainly intended as an aid for when I'm talking and may not work so well for anyone who didn't see the talk! So I've expanded on my notes from the talk at http://www.conroyp.com/2014/10/21/jumping-off-the-waterfall-agile-transition/.

Publicité
Publicité

Plus De Contenu Connexe

Similaire à Jumping off the waterfall (20)

Plus récents (20)

Publicité

Jumping off the waterfall

  1. 1. Jumping off the waterfall Watch out for the rocks below!
  2. 2. Who am I? Paul Conroy, CTO, Square1.io Previously Daft.ie Director of Product & Engineering Led Waterfall to Agile move
  3. 3. So how did that go? [SPOILER] [/SPOILER]
  4. 4. So how did that go? [SPOILER] • More regular releases • Shorter build cycles • Improved build quality • Testing culture [/SPOILER]
  5. 5. So, short talk then?
  6. 6. The journey’s the interesting part…
  7. 7. Context
  8. 8. Context
  9. 9. Context Team of 7-8 devs
  10. 10. Context Team of 7-8 devs
  11. 11. Context Team of 7-8 devs Waterfall
  12. 12. Context Team of 7-8 devs Waterfall
  13. 13. Context Team of 7-8 devs Waterfall Siloed teams
  14. 14. Context Team of 7-8 devs Waterfall Siloed teams
  15. 15. Context Team of 7-8 devs Waterfall Siloed teams Management Support, own client
  16. 16. Lots of change Wary of too much change at once
  17. 17. Centre of attention Ban the boss!
  18. 18. Specsavers “Light-weight” spec very close to “no” spec..
  19. 19. Boxing clever Timebox. Not just a fancy name for a clock.
  20. 20. EAT S L E E P SPRINT R E P E AT
  21. 21. Don’t look back in anger
  22. 22. Weight of the crown(s) Keeping all the plates spinning
  23. 23. Despite it all.. • Regular review & adaptation • Team encouraged to push back when it’s not working • Supportive management team
  24. 24. Despite it all.. More regular releases • Shorter build cycles • Improved build quality • Testing culture • Regular review & adaptation • Team encouraged to push back when it’s not working • Supportive management team
  25. 25. Questions? @conroyp www.square1.io

×