The document discusses the need for continuous improvement and a "built to change" approach in software development. It argues that the traditional "built to last" model does not work in today's rapidly changing world. It advocates adopting cloud native technologies, strategies, and processes that embrace change, such as starting with minimum viable products, using containers and microservices, and practicing continuous delivery. This allows software systems to evolve and adapt through incremental improvements rather than large, infrequent changes.
Frank Frambach presented on DevOps and testing. Some key points: 1. DevOps is driven by digital business models that require faster development and delivery of new features. 2. The DevOps Agile Skills Association (DASA) provides a competence model and certification program to develop high-performing IT professionals in DevOps. 3. Testing is an important part of DevOps and is integrated into several areas of the DASA competence model, including test specification, programming, and infrastructure engineering. 4. Bob, a tester, is shown undertaking a journey through the DASA model, first learning about DevOps and then developing his skills in related areas to transition into a DevOps
This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include: - High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction. - DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures. - Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully. - Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.
So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.
DevOpsGuys - How to get started with DevOps - Redgate Webinar April 2017. 9 steps to DevOps Transformation #SystemsThinking #MakeWorkVisible #MeasureWhatsImportant #ActOnFeedback #IdentifyTheGoal #BeAgile #DeliverContinuously #BuildTrust #AlignToValue #OptimiseForFlow
The document discusses applying lean thinking principles from manufacturing and agile programming to content development. It outlines how lean and agile methods emphasize iterative development, frequent delivery, flexibility, and eliminating waste. This allows content to be produced in a more efficient flow that promotes continuous learning and improvement. Key principles include specifying value, identifying the value stream, pulling work, and optimizing the whole system rather than individual parts.
The document discusses the history and evolution of DevOps. It traces the origins of DevOps back to 2007 when the terms "DevOps" and "Agile Infrastructure" first emerged. It then summarizes the rise in DevOps conferences and communities from 2009 onward. The document also outlines key findings that DevOps adopters see significantly faster lead times, higher deployment frequencies, better change success rates, and faster recovery times compared to non-adopters. Additionally, DevOps teams are more likely to exceed goals for profitability, market share and productivity. The document argues that organizations should focus on fast feedback loops, continuous improvement and adopting an "Improvement System" like DevOps Kaizen in order to see these benefits as a
The Home Depot has over 3500 engineers averaging nearly 6000 git commits per day, with 91% of software written in-house. They have invested $11.1 billion over 4 years, hiring over 1000 new engineers to transform the company from projects to products and experiences. They focus on living their culture and values by investing in associates through cohorts, ongoing education, and onboarding to create an attractive environment for engineers while accomplishing great things like award-winning mobile apps and changing associates' lives.
The continuous culture - Are you looking for ways to speed up? Companies are rapidly adopting technologies, tooling and practices that make them so agile that it changes their culture overnight and changes the playing field. We see disruptors being disrupted within a year. We see the elimination of the first mover benefit due to instant response of competitors. There is no more use for longterm strategies, roadmaps and plans that are just slowing you down. Kim will show you how moving to continuous delivery will change the DNA of your company. Learn how continuous delivery will speed up your company. Learn how your thinking will change through the presence of feedback and data-driven decision making. It’s time to move to the continuous culture.
This document discusses high performance in technology organizations and the DevOps movement. It finds that technology organizations that are high performers are twice as likely to achieve goals like productivity and profitability. High performers have code deployments 46 times more frequent and lead time from commit to deploy is 440 times faster. They also recover from downtime 96 times faster. Achieving high performance requires a focus on technology, processes, and organizational culture together. Leadership is also important but not sufficient on its own. The document provides recommendations for accelerating improvement, including starting with architecture and approval processes.
SpringOne 2021 Session Title: How to Start Your Application Modernization Journey Speaker: Steve Hawkins, Sr. Manager Converged Infrastructure at BT
Jonny Wooldridge, CTO, The Cambridge Satchel Company at the DevOps Enterprise Summit 2014 View video: https://www.youtube.com/watch?v=CzUTztwcc58 View Jonny Wooldridge's blog: http://www.enterprisedevops.com Following 3.5 years building a DevOps capability and culture at M&S I will be condensing the experience down to 10 Enterprise DevOps tips that are relevant to companies of all sizes and complexities. Bringing start-up lean thinking to an enterprise was never going to be easy but the lessons learned are relevant to us all.
This document summarizes the key findings from the 2018 State of DevOps report. Some of the main points include: - Elite performing teams are still able to optimize for throughput, stability and availability. - Adopting essential cloud characteristics and using cloud resources effectively is correlated with high performance. - Architecture and how teams are structured matters more than the specific technology stack. - Open source software usage and avoiding outsourcing are correlated with better performance. - Continuous testing, monitoring, security and including the database in DevOps practices are emerging technical best practices. - Culture and ensuring autonomy for teams also contributes significantly to performance.
SpringOne 2021 Session Title: Saving the DoD $800M: How Portfolio Management is the Missing Link Between Agile and Waterfall Speakers: Jackie Ho, Staff Product Designer at VMware; Oscar Chacon, Portfolio PM at United States Space Force
There are many facets of devops, and we will spend our time in this presentation focusing on collecting and using metrics (business, application, system, etc.) and building a metrics driven culture in organizations. We will define how we have seen devops progress in our organizations and how we’ve realized that different teams in our organizations can find common ground when teams (who have different roles) can work well together when they use metrics as the common language. Karthik will talk about how we are using the principles from the Lean Startup to define our development cycles, sprints and using metrics to quantify how successful the products we are trying to come out with in R&D. Initially we started practicing devops on the dev and ops side of the house but realized this was still a black box to the business side of the house, so we pivoted to what our business actually understood, and that was metrics; today, we focus more on metrics (business and system level), and can fail or succeed fast to achieve our business goals faster than before. Ernest will go into detail on how a large, mature SaaS organization uses metrics in conjunction with distributed agile development and DevOps to guide their development at scale. How much a product is used, how much each feature is used, and how much value each user gets out of it are key drivers for a business strategy - and it’s all information that’s emitted by a system. He'll show how large companies have invested time in collecting and using these metrics to guide their decisions and influence their culture.
There are many systems that need monitoring -- Applications, Infrastructure, Network, Servers all producing metrics, logs, events etc. There are also many vendors selling their APM, NPM, Tracing, monitoring and alerting tools. But how does an organization get to that mythical single pane of glass where there is one consolidated view across these systems? This webinar will look at 5 practical steps that our customers have taken on this journey and what business results they have seen as they have moved to a centralized metric and event store while still leveraging their existing investments in specialized tooling and applications.
This document provides an overview of DevOps Kaizen, which is a methodology for continuous improvement in DevOps. It discusses how Kaizen focuses on continuously improving the flow of work through scientific problem-solving approaches and total workforce engagement. The document outlines elements of a DevOps Kaizen program, including making work processes visible, planning improvements, and overcoming barriers to change. Techniques for process mapping, identifying inefficiencies, and creating improvement plans are also presented.
DevOps Loop at VMworld Session Title: Blame DevOps: Shifting Left the Wrong Way Speaker: Hannah Foxwell, Director, VMware Tanzu Labs Platform Services, VMware Andy Burgin, Lead Platform Engineer, VMware
After having run SDLC projects for more than 8 years, I made the transition to agile projects. This deck captures some of the insights from that journey. Read more here - http://restlesstempest.blogspot.in/2013/06/article-transition-from-sdlc-to-agile.html
With projects springing up at a dizzying pace, it’s hard not to feel like you’re falling behind the curve, or that you’re somehow not doing cloud native development correctly. Breaking out of this “container shame spiral” can be tough. It starts with being better equipped to evaluate projects and trends, and make better decisions about when is the right time to start adopting a new project. Otherwise, you’re all bound to stay stuck in a spiral of reacting to every new announcement. Guiding you through the last few years of container fervor, Laura will help you understand the current landscape and emerging trends, and introduce you to a framework that will help you make sense of all the rapid innovation happening around you.
This document discusses strategies for migrating applications to the cloud. It outlines several service offerings from Pivotal Application Transformation (AppTx) focused on re-hosting, re-platforming, re-factoring, or re-building applications. Common problems encountered include lack of ownership, commitment, readiness, and cultures unsuited for extreme programming. However, many issues like inexperience can be mitigated. The document emphasizes doing the right thing, what works, and being kind.
Continuous Delivery, Reactive Manifesto, Microservices, and DevOps are only few of the great ideas and practices that are currently transforming the way we work in IT. For people working in start-ups or with green field projects all this feels natural, you can expect it, you can take it for granted. Too perfect, and way too easy J If you look for real challenges, look at the Enterprise world. As a Tech Lead in Danske Bank I have the responsibility to help steering our Enterprise and ignite the evolution process that is needed to stay competitive in today’s markets. Through this quest for Agility in the extreme conditions of an Enterprise we are transforming decades of legacy into actual competitive advantage, enabling us to define and deliver brand new financial services at the rate and speed of start-ups.
Summary of fast development and cloud native architecture along with cost optimization techniques. Presented as opening keynote at the Utility and Cloud Computing 2014 as part of the Cloud Control Workshop.
The document discusses the concepts of Lean IT and provides an overview of a training presentation on the topic. It defines key Lean principles like value-added work and waste. It also outlines common Lean roles and certifications like Yellow Belts. The presentation aims to explain how Lean can help IT organizations reduce waste and cycle times to improve service delivery.
A case study like no other. In this series of sessions at BoS Conference USA 2023 we deep dived into how Autobooks retooled their business and ask the question, “What Happens if Product, Sales & Marketing Work Together?” By focussing everything they did on the needs of their customers and helping them grow, they also grew faster, made their lives easier and changed the way they think about collaboration across the company. https://businessofsoftware.org/events/business-of-software-conference-usa-2023/how-autobooks-reinvented-itself-2/
The document provides an overview of Agile project management methodologies like Scrum and Kanban. It discusses how Agile emerged from a 2001 meeting where representatives from various groups developed the Agile Manifesto. Scrum uses sprints, daily stand-ups, retrospectives and story points to manage work in an iterative process. Kanban uses visual boards and work-in-progress limits to manage flow. Both aim to deliver working software frequently through self-organizing teams that can adapt to changing priorities.
The webinar discusses the importance of website redesign and provides tips for doing so successfully. It covers how the internet has changed and buyers now research online before engaging with sales. A redesign may be needed if a website is not aligned with a company's strategy, brand, or built for conversions. Key steps include evaluating analytics, assessing competitors, setting goals, requirements gathering, and choosing the right partner. Must-have features discussed are great design, compelling content, lead generation elements, and considering technical requirements.
KEYNOTE TALK What does it take to innovate quickly? I’ll address how blockers to innovation – including culture, skills, antiquated processes, and board level concerns – can stand in the way of business agility. We’ll map out a pathway to digital transformation including new metrics for success, integrating real-world best practices from enterprises, and the most effective organizational patterns, as we integrate the business with development and operations.
Lessons learned on rewriting a large technology stack from Drupal to Java + Ruby Video here: http://www.youtube.com/watch?v=PhYUvtifJXk
This document discusses building an intranet from the bottom up rather than the traditional top-down approach. It advocates starting simply with personal collaboration tools like OneDrive and building out ad hoc collaboration sites before establishing departmental sites and a centralized landing page. This bending of the value curve allows for quick wins that generate momentum. The document provides an example of an oil and gas company that takes this approach, first promoting safety and providing reports before upgrading their unstable SharePoint farm. It emphasizes an iterative process of defining vision, mapping to value, working solutions, evaluating and adapting as the intranet is developed incrementally from the ground up.
This document discusses how to embrace change and overcome inertia in organizations. It argues that a revolution is happening due to digital disruption. Incumbents are locked into perfecting existing models while startups can disrupt at a fraction of the cost and much faster. It then provides recommendations on how to fuck inertia by focusing on purpose, people, and process. Specifically, it suggests building a visionary customer-centric purpose, hiring agents of change, and adopting agile processes and a culture of experimentation.
The biggest challenge to successful product design isn’t the limits of technology or the changing global marketplace- it’s the sheer number of tasks waiting for each engineer to complete! A large Work In Progress (WIP) queue turns innovation into imitation by delaying product launch. A large WIP reduces agility because new opportunities go to the back of the queue, yet only 2 percent of product developers measure their WIP queues and only 15 percent of them can quantify the cost of launch delay. But the answer isn’t to hire more people or pull your hair out- it’s to automate tasks that lend themselves to it, reducing your WIP queue and finally freeing your engineers to innovate! This presentations covers some techniques to quantify your WIP queue and how much it is costing you. It also covers how to automate the most common product development tasks that engineers, sales and quoting departments do every day, using a combination of SolidWorks software and the powerful automation add-in DriveWorks.
Presented by Diana Budreau on January 27th, 2017. Are you considering moving your NAV or CRM solution to the cloud? This session will walk you through the steps you'll need to take to make sure it's the right decision, get your organization ready, and build a project plan to ensure that the move is a success.
Containers, Microservices, Cloud Native and DevOps are all gaining the speed and more and more companies are refactoring their development processes and infrastructure platforms to to build ever more complex applications and avoid falling behind the competition. But what does it take to adopt these technologies? Is it as easy as running one Docker container on one server? In this talk, I will share our experience of implementing those technologies while working with verity of different clients.