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.

Agile Practice in a DevOps World

Does Agile fit in a DevOps world?

  • Login to see the comments

Agile Practice in a DevOps World

  1. 1. AGILE PRACTICE IN A DEVOPS WORLD Magnus Hedemark @Magnus919
  2. 2. What is DevOps? “DevOps is a software development method that stresses communication, collaboration (information sharing and web service usage), integration, automation and measurement cooperation between software developers and other information-technology (IT) professionals. “DevOps acknowledges the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services and to improve operations performance - quality assurance.”
  3. 3. Critical Mass • John Allspaw spoke at Velocity Conference, 2009 • Flickr was deploying code 10+ times per day • First DevOps unicorn? • This is probably where everyone else started to take notice.
  4. 4. Over the Top • “The Phoenix Project” was published in 2013 • Modern retelling of Goldratt’s “The Goal” applying DevOps principles to a software development project • Has anyone here not read this yet?
  5. 5. Diet DevOps Developers + Operations Working Together
  6. 6. DEVOPS IS COMPREHENSIVE DevOps success comes from full organizational alignment around goals, values, cadence.
  7. 7. CAMS
  8. 8. CAMS • Culture • Automation • Measurement • Sharing
  9. 9. CULTURE People and process first. If you don’t have culture, all automation attempts will be fruitless.
  10. 10. AUTOMATION Visibility -> Accountability -> Automation
  11. 11. Visibility • Don’t automate what you don’t understand.
  12. 12. Accountability • Don’t automate what you can’t validate. • Define the desired state. • Validate current state against desired state.
  13. 13. Automation • Your environment must be understood • Your desired state must be verifiable • You’re now ready to automate.
  14. 14. MEASUREMENT If you can’t measure, you can’t improve.
  15. 15. SHARING The loopback in the CAMS cycle
  16. 16. THE THREE WAYS
  17. 17. SYSTEMS THINKING emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department
  18. 18. AMPLIFY FEEDBACK LOOPS this is about creating the right to left feedback loops. The goal of almost any process improvement initiative is to shorten and amplify feedback loops so necessary corrections can be continually made.
  20. 20. IF SOMETHING HURTS… …keep doing it until it’s easy.
  21. 21. DEVOPS IS HOLISTIC How effective is your Agile practice if IT Operations isn’t participating?
  22. 22. VALUES BEGET BEHAVIORS. Behaviors beget culture.
  23. 23. OK, I GET IT. DEVOPS IS AWESOME. Do I have to abandon Agile?
  24. 24. WE’RE GONNA DO SCRUM! It’s going to be awesome. Right?
  25. 25. What’s wrong with Scrum? • Sprint-based release cycle (as commonly practiced) vs continuous delivery of working software • “Meetings for days” vs “Getting s*** done” • Business asking for time estimates & actuals, which are never true. Where’s the value? • Do you really need sprints? So much planning? Review?
  26. 26. What’s Right With Scrum? • Effective standups • Effective retrospectives • Agile values & principles
  27. 27. Kanban • Kanban emphasizes one-piece workflow, continuous just-in-time delivery of what customers want. • Very visual so team and stakeholders know the state of all work. • Frequent changes of ranking in the To Do pile are welcome. • WIP is respected. Teams gets more done without working any harder. • Measuring Lead Time / Cycle Time has true value.
  28. 28. Agile Heritage vs DevOps Heritage • Came out of Software Development • Well-defined values & principles • Many well-defined processes • Came out of nexus between Software Development and IT Operations • Borrows heavily from auto manufacturing industry • Not well-defined • No specific processes defined
  29. 29. Service Oriented Architecture • Is a logical representation of a repeatable business activity that has a specified outcome • Is self-contained • May be composed of other services • Is a “black box” to consumers of the service
  30. 30. If the team is a black box… …how do I make it Agile? • There are many opportunities here to develop new Agile methodologies. • Huge opportunity to develop a scaled framework that respects autonomy of team’s inner workings while prescribing true business requirements • How do we request new value from a team? • How do we validate value output of the team?
  31. 31. THE MENTAL LEAP Creating software isn’t all that different than building cars. OK yes it is. But we can learn a lot anyway.
  32. 32. MANTRA “Every git merge event represents a potentially shippable increment of product.”
  33. 33. SAY IT AGAIN “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
  34. 34. NEGATIVE POLITICS Canary in the Coal Mine
  35. 35. Brief Note on Autism • I am autistic. • No, I can’t do big math in my head. • 1 to 2% of population is on- spectrum. • Autism is disproportionately present in Engineering professions • presents some serious social challenges • Agile and DevOps are inherently social practices • You’ve probably already experienced this perfect storm, but didn’t know it. • Empathy, patience, and kaizen