1 / 21

Understanding DevOps: Principles and Benefits for Agile Software Development

This recap of the Agile 2013 conference explores the fundamentals of DevOps, its significance, and the benefits it offers to software teams. Key practices include improving software release efficiency, automating testing and builds, and adopting Continuous Integration (CI) principles. By focusing on reducing deployment times, identifying defects early, and maintaining a self-testing code repository, teams can enhance their productivity. The session also highlights the importance of Continuous Delivery and planning for effective rollbacks. Discover how to streamline software development and delivery with DevOps.

betty
Télécharger la présentation

Understanding DevOps: Principles and Benefits for Agile Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Michael Lepine Agile2013 Recap

  2. What is DevOps?

  3. Why DevOps?

  4. Benefits of DevOps Teams

  5. Releasing Software Time spent deploying new software releases:

  6. Improve Deployments • Here are some common things that DevOps teams do to improve software releases: • Increase efficiency – less waste • Decrease time to commit software changes • Automate tests • Identify defects/issues quickly • Automate the build process • Simplify the deployment process • Make deployments reproducible • Automate as much as possible

  7. Welcome Continuous Integration

  8. Principles of Continuous Integration • Maintain a code repository • Automate the build • Make the build self-testing • Everyone commits to the baseline every day • Every commit (to baseline) should be built • Keep the build fast • Test in a clone of the production environment • Make it easy to get the latest deliverables • Everyone can see the results of the latest build • Facilitate automated deployments

  9. How CI Improves Efficiency • Simplify Merges • Rapid Feedback • Identify problems early • Makes bugs easier to find • Reduce bug accumulation • Visibility (team and stakeholders) • Builds Automated • minimizes manual intervention • plug-ins (i.e. for static code analysis, gathering metrics) • Precursor to Continuous Delivery & Deployment

  10. And…Continuous Delivery/Deployment

  11. Keys to Continuous Delivery • Process should be automated • Reduces the number of features introduced per release, minimizing shock to users • Will reduce the standard release cycle • Changes approach to releasing software from an event to a non-event • Helps to avoid off-hour, high risk, expensive deployments • Know your rollback plan (do you rollback or roll forward only) • Build in health checks

  12. Potential Concerns to Implementing Continuous Delivery - Data

  13. CI/CD Tools

  14. What Is an Ideal Work Environment?

  15. Ready to Solve Problems and Make Decisions?

  16. Improve Productivity & Problem Solving Skills

  17. Ostrich Pillow – Power Nap Anywhere Research at NASA demonstrated that power naps increased alertness by 54% and improved performance by 34%.

  18. Agile 2013 Sessions: • Lean DevOpswith KarthikGaekwad at Mentor Graphics Embedded • Continuous Delivery with Steve Stolt& Steve Neely at Rally Software • Agile Logistics • Better Problem-Solving and Decision-Making with Linda Rising

More Related