Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

The 2019 Accelerate State of DevOps Report Webinar

978 Aufrufe

Veröffentlicht am

The Accelerate State of DevOps Report is the result of five years of research—and more than 30,000 data points—and aims to understand how software delivery and operational (SDO) performance drives organizational performance. Our data also supports analyst reports that the industry is crossing the chasm: we see almost 3x the proportion of elite performers compared to last year, with low performers shrinking in comparison.

In this webinar, we discuss the key findings in the 2019 report. Join us and learn:

● the best strategies for scaling DevOps;
● how to leverage the cloud to drive superior outcomes and unlock effective change management;
● how to optimize productivity so you can improve work/life balance and reduce burnout; and
● new findings for how to build a great organizational culture.

Speakers:

Dr. Nicole Forsgren does research and strategy at Google Cloud. She is co-author of the Shingo Publication Award-winning book, Accelerate: The Science of Lean Software and DevOps, and is best known as lead investigator on the largest DevOps studies to date. She has been a successful entrepreneur (with an exit to Google), professor, performance engineer, and sysadmin. Her work has been published in several peer-reviewed journals.

Richard Seroter is the VP of Product Marketing at Pivotal, a 12-time Microsoft MVP for cloud, an instructor for developer-centric training company Pluralsight, the lead InfoQ.com editor for cloud computing, and author of multiple books on application integration strategies. As VP of Product Marketing at Pivotal, Richard heads up product, partner, customer, and technical marketing and helps customers see how to transform the way they build software. Richard maintains a regularly updated blog (seroter.wordpress.com) on topics of architecture and solution design and can be found on Twitter as @rseroter.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

The 2019 Accelerate State of DevOps Report Webinar

  1. 1. The 2019 Accelerate State of DevOps Report
  2. 2. Our Hosts Today Richard Seroter Nicole Forsgren
  3. 3. Today! ● Key Findings from the 2019 Accelerate State of DevOps Report ● Some fun STATS: Benchmarks and more ● Getting better (aka Choose your own adventure) ● Performance ● Productivity ● Culture ● Successful paths to Elite performance ● Fin! (and more!)
  4. 4. We have movement ● Look at the elite performers. Yay! ● Now look at the low performers. Yay! ● Check out medium performers… ● Now look at the medium vs. high. Oooo
  5. 5. How do they compare? (And what does it all mean?)
  6. 6. Availability Availability is about promises we make and keep to our customers and end users… The measure: How well teams ● Define their availability targets ● Track their current availability ● Learn from any outages
  7. 7. Availability Availability is about promises we make and keep to our customers and end users… The measure: How well teams ● Define their availability targets ● Track their current availability ● Learn from any outages Day one is short, day two is long
  8. 8. So… We do tech because it’s fun?
  9. 9. So… We do tech because it’s fun? yes, and...
  10. 10. Elite performers are Technology delivers value 2xas likely to meet or exceed their organizational performance goals
  11. 11. Okay… so it matters. How do we get better? ?
  12. 12. Okay… so it matters. How do we get better?
  13. 13. ImprovingPerformance
  14. 14. Cloud is a differentiator for elite performance… But only 29% of respondents met all five characteristics of cloud computing Elite performers were 24 times more likely to have met cloud characteristics than low performers On-demand self-service Broad network access Resource pooling Rapid elasticity Measured service
  15. 15. Code maintainability Contributes to CD and helps reduce technical debt (stay tuned!) Change code maintained by other teams Find code in the codebase Reuse other people’s code Add, upgrade, and migrate to new versions of dependencies without breaking code Systems and tools that make it easy to:
  16. 16. ImprovingProductivity
  17. 17. What is productivity? Productivity is the ability to get complex, time-consuming tasks completed with minimal distractions and interruptions
  18. 18. What is productivity? Productivity is the ability to get complex, time-consuming tasks completed with minimal distractions and interruptions This kind of productivity helps us leave work at work and reduce burnout
  19. 19. Technical debt was introduced in 1992 by Ward Cunningham to describe what happens when we fail to maintain “immature code” It is a problem for many of us and includes code or systems with: Known bugs that go unfixed in favor of new features Insufficient test coverage Problems related to low code quality or poor design Code or artifacts that aren’t cleaned up when no longer used Implementations the team doesn’t have expertise in, and therefore can’t debug or maintain Incomplete migration Obsolete technology Incomplete or outdated documentation or missing comments
  20. 20. Reducing Technical Debt This helps us maintain a mental model of our systems, something Ward Cunningham suggested we would need in his original article. Maintainable code Loosely coupled architecture Monitoring
  21. 21. Culture I keep hearing culture matters.
  22. 22. What does that even mean?
  23. 23. Culture is important ● A culture of trust and psychological safety has a positive impact on: ○ Software delivery performance ○ Organizational performance ○ Productivity ● These results indicate teams with this culture see significant benefits in teams in many contexts
  24. 24. How can you increase your chances of success in your journey to Elite performer?
  25. 25. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. ➔ Spring Boot is the most widely used Java framework with 85+ million downloads per month. It eliminates boilerplate code that reduces stability and consistency. ➔ Common approach to every sort of enterprise app. Code scalable, robust web apps, microservices, APIs, streaming apps, batch processors, and functions. ➔ Spring Cloud brings Netflix-style patterns to apps, anywhere. Incorporate best practices—like remote config, service discovery, circuit breakers—on any infrastructure. Choose robust developer frameworks.
  26. 26. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. ➔ The Pivotal Platform gives you a secure, always updated infrastructure layer that’s ready for developers. ➔ PKS offers a consistent Kubernetes experience, everywhere. With multi-cluster tenancy, continuously patched infrastructure, and self-service interfaces, you can operate at scale. ➔ Own the software supply chain with Pivotal Build Service. Securely build and patch container images using buildpack automation. Standardize infrastructure management.
  27. 27. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. ➔ Scale your (multi) cloud by implementing continuous integration and continuous delivery across the organization. ➔ Leverage tools like Concourse and Spinnaker. Get uniform builds with Concourse, and sophisticated deployments on any infrastructure with Spinnaker. ➔ Do value stream assessments to find constraints. Identify the full path to production and uncover bottlenecks that limit flow. Automate your path to production.
  28. 28. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. ➔ Do rapid portfolio assessment using tools like the Pivotal App Analyzer. ➔ Choose representative apps to modernize. Develop a pattern catalog that can apply elsewhere. Work with Pivotal Labs to design and upgrade software that’s continuously delivered. ➔ Treat modernization as a lifestyle, not a project. You’re never done modernizing, so develop the skills, tech stack, and organizational appetite to continue the work. Build up your modernization muscle.
  29. 29. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. ➔ Scale the practice of software delivery. Product teams own the full lifecycle of the value stream. ➔ Empower teams with a responsible amount of choice. Decide where consistency is critical, and where team- driven needs win out. ➔ Put the cloud | Kubernetes focus where it belongs: business outcomes. Identify and measure business metrics like value, cost, and quality. Adopt a product team model.
  30. 30. TL;DR ● Is this DevOps thing even “A Thing”? ● Getting better (aka Choose your own adventure) ● Performance ● Productivity ● Culture ● Successful paths to Elite performance ● Fin! (there’s so much more!) ○ Disaster Recovery Testing ○ Change Approvals (the “right” way) ○ Open source! ○ More cloud (and costs!) ○ Scaling transformations successfully Go check it out! cloud.google.com/devops

×