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.

Modern agile overview


Published on

An overview of Joshua Kerievsky’s "Modern Agile", used to generate some interesting discussion at Agile Ottawa in Feb 2016.

Based on Joshua's work:
* blog:
* webcast:

Published in: Leadership & Management
  • Be the first to comment

Modern agile overview

  1. 1. Modern Agile Overview Agile Ottawa Feb 2016 by Steve Purkis & Dag Rowe based on Joshua Kerievsky’s work:
  2. 2. Joshua had seen too much of this... Sprints Storypoints Standups Agile?!?
  3. 3.
  4. 4. Ecosystem Not just Scrum
  5. 5. Make Users Awesome discipline #1
  6. 6. Why does your business exist? We have great new tech! We’re the best at what we do! We have brilliant marketing! We have the greatest product(s)! …
  7. 7. Your business exists… To help your customers achieve something! they don’t have the skills/resources they’re too busy it’s too painful they’d just rather not do it …
  8. 8. Modern Agile: Go beyond just helping your users… Make them awesome!
  9. 9. eg: What switching meant to me… No more excel + paper tax returns! Less work figuring out what I needed to do. More money back than I would’ve otherwise! It was really nice to use! Great, friendly support They offered it to me for free… and they actually meant it! They took away the pain, and even made it a little bit pleasant to file taxes.
  10. 10. What does your user need? May not be the same as what they say they want! Up to you to figure it out. Customer journey mapping
  11. 11. Chartering your work How are you going to make your users awesome? What does it mean? What’s your vision? mission? How will you know when you’ve succeeded? Measurable & testable outcomes Ongoing, revisit during a project.
  12. 12. Big shift in thinking! eg: Definition of Done Internal acceptance criteria
  13. 13. Big shift in thinking! eg: Definition of Done Internal acceptance criteria vs Validated by real users
  14. 14. Make Safety a Prerequisite discipline #2
  15. 15. - Frank Herbert, Dune image: killer/
  16. 16. Fear poisons productivity Being fired Being penalised for making a mistake Being rejected Being excluded or marginalised Looking stupid These are basic, primal fears. In our tribal past, rejection by a group could involve banishment, which could result in death.
  17. 17. Anzeneering “Protecting people is the most important thing we can do, because it frees people to take risks and unlocks their potential. I call this Anzeneering, a new word derived from anzen (meaning safety in Japanese) and engineering.” - Joshua Kerievsky
  18. 18. everyone, not just devs! Software users Software makers Software managers Software purchasers Software stakeholders Make it safe to fail Read this!
  19. 19. How do I make it safe to fail at my company? Break down any culture of fear you come across. Empower employees to: voice dissenting opinions safely take risks discuss & address safety issues bring new ideas to the table Avoid mixed messages (we care about your safety, but please
  20. 20. Remember, it’s people! Respect & appreciation Be authentic Cultivate an open mind Transparency (2 way street!) Shared responsibility Boost communication
  21. 21. Safety-first is a Cultural Shift Do it safely: evolve gradually. Try to understand where your organisation is at first. Have a plan on how to change. Share it!
  22. 22. Improve software safety Test! TDD, Automated testing, Manual testing Refactor, continuous improvements Continuous Integration Pay down tech debt de-SPOF coders pair as needed
  23. 23. Evolution: Smaller releases Less risk for developers, customers, users & managers. Better feedback loops.
  24. 24. Remember: we’re dealing with complex systems! Assume goodwill Use 5 why’s / root cause Use neutral language Seek to understand, not criticize Encourage everyone to share Blameless Retros
  25. 25. User safety & appreciation Own up to issues and provide solutions eg: Sorry, we overcharged you last month! That’s embarrassing to say the least. We’ve refunded your account, and given you an extra [month free] to make up for it! Step up to show your appreciation Notice things & engage users. eg: You didn’t use all your credit with <SaaS co> this month. 1. do/say nothing 2. message: You didn’t use all your credit this month. Please call us at your earliest convenience to get a refund. 3. message/act: You didn’t use all your credit this month, so we’ve refunded the difference.
  26. 26. Experiment and Learn Rapidly discipline #3
  27. 27. Lean Startup = Lean Thinking + Customer Development + Agile Development Lean startup is a process involving rapid and iterative experimentation to test assumptions and build a product or service that customers actually want
  28. 28. Lean UX = Lean Thinking + Design Thinking + Agile Development Lean UX is a process to build a product that customers actually want with a focus on shared understanding of the experience being designed
  29. 29. Design Thinking
  30. 30. Science! 1. Assumptions 2.Hypothesis 3.Experiment 4.Measure 5.Learn Pivot (do something else based on what you’ve learned) Continue
  31. 31. Fail Fast Make it safe to fail because failure enables learning You can learn by conducting an After Action Review when you project is late and over budget Or you can choose to learn quickly and cheaply before committing to building a product Some people don’t like the word fail - call Learn Fast instead
  32. 32. Deliver Value Continuously discipline #4
  33. 33. Continuous delivery maturity model
  34. 34. Continuous Delivery Maturity Model
  35. 35. Simple Build Pipeline
  36. 36. CD Resources Books The Visible Ops Handbook: Implementing ITIL in 4 Practical and Auditable Steps Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation CD videos
  37. 37. Joshua Kerievsky’s Modern Agile Blog post Webinar @ Lean Kit
  38. 38. Things that may come up
  39. 39. Agile Manifesto & Modern Agile