Using DevOps to Drive the Agile ALM
- 3. 5/30/16 1 Agile ALM: Using DevOps to Drive the Agile ALM 1 Bob Aiello, Principal Consultant and Author of Configuration Management Best Practices : Practical Methods that Work in the Real World http://www.linkedin.com/in/BobAiello http://agilealmdevops.com http://cmbestpractices.com CM Best Practices Consulting © 2016 Who am I? • CM/DevOps & Consultant for over 25 years • Editor at CM Crossroads for 15 years • Author of CM Best Practices • IEEE Management Board • Tools and process agnostic • The guy called in the middle of the night when the release doesn’t work! 2 June 2016http://cmbestpractices.com © 2016
- 4. 5/30/16 2 Goals of this Talk • Introduce the Application Lifecycle Management • Understand what makes it agile? • Discuss how to create processes • Explain how to use DevOps • Rightsize and continuously improve 3 June 2016http://cmbestpractices.com © 2016 The Agile ALM 4 • Facilitates agile development • Adheres to agile principles • Most would say light process • Some would way no process How about that manifesto… http://cmbestpractices.com © 2016 June 2016
- 5. 5/30/16 3 New Book on Agile ALM & DevOps 5 June 2016http://cmbestpractices.com © 2016 ALM 6 • Defines the activities that the team is working on • Helps us understand what needs to be done next • Transparency and traceability • Are we there yet? What makes an ALM agile? http://cmbestpractices.com © 2016 June 2016
- 6. 5/30/16 4 Agile Configuration Management Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 7http://cmbestpractices.com © 2012 November 7, 2012 Some Agile Principles 8 • Satisfy the customer through early and continuous delivery of valuable software • Welcomes changing requirements – even late in the development • Deliver frequently • Business and Dev work together • Working software http://cmbestpractices.com © 2016 June 2016
- 7. 5/30/16 5 Dysfunctional ALM 9 • Too much process • Fighting last years war • Lack of integration • Mired in unusable workflow tools • Poor communication So how do we implement? http://cmbestpractices.com © 2016 June 2016 Agile ALM 10 • Choose your agile methodology … • Let’s go with SCRUM • Write your stories • Create your backlog • Choose a SPRINT duration, etc. Developers need… http://cmbestpractices.com © 2016 June 2016
- 8. 5/30/16 6 ALM for Dev 11 • Developers focus on understanding requirements and creating great code • Continuous Integration • Continuous Delivery and Deployment • Continuous Testing • Continuous Security http://cmbestpractices.com © 2016 June 2016 ALM for Ops 12 • IT Operations • Change control • Maintaining Infrastructure • Performance • Service continuity • Security and reliabity http://cmbestpractices.com © 2016 June 2016
- 9. 5/30/16 7 What about … 13 • Business • Information security • QA and testing • Help Desk • Audit and Compliance • Procurement http://cmbestpractices.com © 2016 June 2016 ALM Feedback Loops 14 • Incidents • Problems • Events • Postmortem versus Retrospective http://cmbestpractices.com © 2016 June 2016
- 10. 5/30/16 8 Never let a crisis go to waste 15 • When bad things happen • People are more open to change • Seems fair to not let it happen again http://cmbestpractices.com © 2016 June 2016 ALM Evolution 16 • Early in the development effort • IT controls to avoid mistakes • Comply with federal regulatory reqs • Reduce risk and avoid mistakes • What if our systems are hacked? Too much of a good thing… http://cmbestpractices.com © 2016 June 2016
- 11. 5/30/16 9 Keep it Light 17 • Just enough ceremony • Add more structure as the project evolves • IT controls avoid mistakes • Keep it as lean as possible So who needs DevOps http://cmbestpractices.com © 2016 June 2016 What is DevOps? 18 • Three guys in a dorm room • ITIL v3 Release & Deployment Management (RDM) • DevOps @ Scale It’s the principle of the thing… http://cmbestpractices.com © 2016 June 2016
- 12. 5/30/16 10 What is DevOps? 19 • Principles & Practices to communicate and collaborate more effectively • Not necessarily Dev or Ops • Full ALM endeavor Pragmatic and Goal Oriented http://cmbestpractices.com © 2016 June 2016 DevOps is also 20 • Emerging Best Practices • Collaboration between Dev, Ops & ** • Application and Systems Deployment • Software and Systems Development But is DevOps Agile? http://cmbestpractices.com © 2016 June 2016
- 13. 5/30/16 11 DevOps is Really... 21 • Developer and Operations collaboration • Crossfunctional team • Knowledge Management • Better communication Time to get rid of silos http://cmbestpractices.com © 2016 June 2016 Pick a Pilot (or POC) • Don’t try to boil the Ocean • Success changes culture! • Spread the credit • Paint the vision! Ok so what needs fixing? 22 June 2016http://cmbestpractices.com © 2016
- 14. 5/30/16 12 Assessment 23 • First step is to assess current practices - “As-Is” • Compare to industry standards and frameworks • Determine “To-Be” • Create a plan for improving your CM processes June 2016 http://cmbestpractices.com © 2016 Retrospective 24 • After action review • Need open and honest evaluation • Opportunity to improve the process • Drives the entire release process http://cmbestpractices.com © 2016 June 2016
- 15. 5/30/16 13 Continuous Delivery 25 • Methodology for getting software from development to release • Focus on the Deployment Pipeline • Rapid incremental deployment • Minimize Risk • Many small deployments better than big bang http://cmbestpractices.com © 2016 June 2016 Introducing the Trusted Base 26 • Ensure that you know exactly what you built • Verify that the release gets deploy • Ensure that there are no unauthorized changes Understanding Continuous Integration http://cmbestpractices.com © 2016 June 2016
- 16. 5/30/16 14 How Do We Implement? Are deployment pipelines practical? How do we figure out the details? Is it worth the time and effort? What are the benefits? What are the risks? Siloed behavior is bad ... 27http://cmbestpractices.com © 2016 June 2016 Where does support come from? 28 • Top down • Bottom up http://cmbestpractices.com © 2016 June 2016
- 17. 5/30/16 15 Beware of Silos 29 • The SAs see file systems • The DBAs have a different view • WebSphere Admins • InfoSec helped us secure (so much nothing worked) DevOps is about sharing knowledge! http://cmbestpractices.com © 2016 June 2016 Knowledge Management 30 • There are always a few experts • They are not working when system glitch • Building a Knowledge Management System • But What if some people do not want to share? (caution silos ahead) http://cmbestpractices.com © 2016 June 2016
- 18. 5/30/16 16 Globally Distributed team 31 • Managing work for a globally distributed team • Effective communication • Better coordination • Traceability • Visibility http://cmbestpractices.com © 2016 June 2016 Plan for Improvement 32 • Start small and add controls only as needed • Never make the same mistake twice • Workflow automation tools are essential • Don’t let your tools get in the way • Take an agile iterative approach! June 2016 http://cmbestpractices.com © 2016
- 19. 5/30/16 17 Goals of this Talk • Introduce the Application Lifecycle Management • Understand what makes it agile? • Discuss how to create processes • Explain how to use DevOps • Rightsize and continuously improve 33 June 2016http://cmbestpractices.com © 2016 New Book on Agile ALM & DevOps 34 June 2016http://cmbestpractices.com © 2016