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

Agile-ish is good enough

Agile-ish is good enough

A sort of contrarian view on how strictly one needs to follow formalised agile methodologies (Scrum, etc.) to get the benefits and intentions which inspired the agile manifesto. A brief exploration of agile development processes in tech organisations.

E85644104e56d9f8be2fcea8b20f5e97?s=128

Bradley Whittington

January 16, 2013
Tweet

Transcript

  1. Agile-ish is good enough Brad Whittington @darb | Community Products,

    Mxit
  2. Or, how much agile religion is enough

  3. I might say some offensive things Start at the beginning

  4. Lots of waterfall

  5. A-type people felt like everything was under control

  6. Gantt chart

  7. 2001

  8. Individuals and interactions over processes and tools Working software over

    comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  9. Individuals and interactions over processes and tools Working software over

    comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Kiff. Sure.
  10. Organisations welcomed agile! But not really.

  11. 2005-ish

  12. (rigid planners) Project Managers

  13. Magic!

  14. (Strategists / Visionaries / Negotiators) Product managers

  15. Huh.

  16. 2013

  17. Agile-ish is sort of everywhere

  18. Organisations are really kind of starting to understand agile

  19. Let's talk principles

  20. ... We're about: Delivery, Supportive Environment, Flexibility

  21. Business people and developers must work together daily throughout the

    project.
  22. Two different languages

  23. Scrum kanban totes fix that!

  24. Says the A-type Just need a good process A good...

    structure
  25. Scrum masters!

  26. Planning poker!

  27. Burn down charts!

  28. Product owners!

  29. Retrospectives!

  30. Sprint 0!

  31. Fibonacci Sequence! Points!

  32. Backlog!

  33. Individuals and interactions over processes and tools

  34. Let's go ghetto style What is enough?

  35. Because memory is kak Backlog

  36. because someone needs to live inside it Product owner

  37. What's next Prioritisation

  38. to-do, in-progress, verifying, done, (released) Progress columns

  39. Jira makes them real pretty What about my charts?

  40. Be careful of vanity metrics

  41. Charts don't understand broken developers

  42. How will we know when feature X will be done?

  43. Rework / Jason Fried & David Heinemeir Hansson

  44. It will get done when it climbs up the backlog

  45. But... points!

  46. Brains add numbers together and make assumptions

  47. http://brucefwebster.com/2008/04/15/the-wetware-crisis-the-themocline-of-truth/ Don't create a thermocline of truth

  48. My love affair with Trello

  49. Backlog Inbox / Idea pool Backlog pit Really important stuff

    Next up
  50. The working board Scheduled In progress Testing / Verification Done

    Deployed
  51. Everything else is Interactions

  52. Tx.