This document provides guidance on transitioning an organization to a DevOps model. It discusses how organizational structures can impact technical designs based on Conway's Law. It then covers common anti-patterns when shifting to DevOps like relying on a single consultant. The document proposes using a logical rather than structural view of the organization and modeling it after Spotify's Guild model. It offers tips for facilitating collaboration between teams and overcoming challenges to change. Finally, it addresses technical transition topics like security as code and environment consistency. The overall message is that organizational change requires clear communication, addressing business needs, facilitating cross-team work, and setting ambitious yet achievable goals.
DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.
DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.
The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s
James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.
For more information visit www.devopsguys.com and www.red-gate.com
A high level introduction to DevOps. Explains what it is, how popular DevOps has become, why DevOps is popular, how DevOps differs from traditional approaches and some next steps to implementation.
DevOps Transformation: Learnings and Best PracticesQBurst
The presentation delves into the best practices and approach for DevOps adoption. Understand key aspects of DevOps and how it brings about speed and efficiency in the software development lifecycle
DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.
DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.
The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s
James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.
For more information visit www.devopsguys.com and www.red-gate.com
A high level introduction to DevOps. Explains what it is, how popular DevOps has become, why DevOps is popular, how DevOps differs from traditional approaches and some next steps to implementation.
DevOps Transformation: Learnings and Best PracticesQBurst
The presentation delves into the best practices and approach for DevOps adoption. Understand key aspects of DevOps and how it brings about speed and efficiency in the software development lifecycle
What is DevOps | DevOps Introduction | DevOps Training | DevOps Tutorial | Ed...Edureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This DevOps tutorial takes you through what is DevOps all about and basic concepts of DevOps and DevOps Tools. This DevOps tutorial is ideal for beginners to get started with DevOps. Check our complete DevOps playlist here: http://goo.gl/O2vo13
DevOps Tutorial Blog Series: https://goo.gl/P0zAfF
DevOps is a methodology capturing the practices adopted from the very start by the web giants who had a unique opportunity as well as a strong requirement to invent new ways of working due to the very nature of their business: the need to evolve their systems at an unprecedented pace as well as extend them and their business sometimes on a daily basis.
While DevOps makes obviously a critical sense for startups, I believe that the big corporations with large and old-fashioned IT departments are actually the ones that can benefit the most from adopting these principles and practices.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
DevOps is the act of managing two distinct but complementary areas of expertise: development and operations. Devops emphasizes collaboration and integration between app developers and IT operations professionals.These 10 business advantages of DevOps can help you see why it's important for organizations to adopt this methodology if they want to stay competitive in the digital economy.
DevOps vs Agile | DevOps Tutorial For Beginners | DevOps Training | EdurekaEdureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This is a short tutorial by Edureka on DevOps vs Agile, which will help you understand the fundamental difference between DevOps and Agile software development strategies.
What is DevOps? | DevOps Introduction | DevOps Tools | DevOps Tutorial For Be...Simplilearn
This presentation on DevOps will help you understand what is DevOps, how DevOps came to being, stages and tools of DevOps, implementation of DevOps, DevOps practices, benefits of DevOps approach and at the end, you will also see a use case of DevOps approach by Etsy. DevOps is a software engineering culture that unifies the development and operations team, under an umbrella of tools to automate every stage. The benefits of DevOps outweigh the potential difficulties. Aligning the two transparency-limited silos ensures that systems are delivered faster, and also reduces risks in production changes through nonfunctional and automated testing, as well as shorter developmental iterations. The DevOps approach automates the service management for the support of operational objectives and improves understanding of the layers in the production environment stack. In turn, this helps prevent and resolve production issues. Now, lets deep dive into these slides and understand what actually DevOps is.
Below topics are explained in this DevOps presentation:
1. How DevOps came to being
2. What is DevOps?
3. Stages and tools of DevOps
4. Implementation of DevOps
5. DevOps practices
6. Use case: DevOps approach by Etsy
7. Benefits of DevOps approach
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit to the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/
DevOps is a software development method which is all about working together between Developers and IT Professionals. This presentation gives you an introduction to DevOps.
That DevOps and Agile bring benefit is self-evident; these slides explore how the key benefits can be quantified such that a business case can be built.
What is DevOps | DevOps Introduction | DevOps Training | DevOps Tutorial | Ed...Edureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This DevOps tutorial takes you through what is DevOps all about and basic concepts of DevOps and DevOps Tools. This DevOps tutorial is ideal for beginners to get started with DevOps. Check our complete DevOps playlist here: http://goo.gl/O2vo13
DevOps Tutorial Blog Series: https://goo.gl/P0zAfF
DevOps is a methodology capturing the practices adopted from the very start by the web giants who had a unique opportunity as well as a strong requirement to invent new ways of working due to the very nature of their business: the need to evolve their systems at an unprecedented pace as well as extend them and their business sometimes on a daily basis.
While DevOps makes obviously a critical sense for startups, I believe that the big corporations with large and old-fashioned IT departments are actually the ones that can benefit the most from adopting these principles and practices.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
DevOps is the act of managing two distinct but complementary areas of expertise: development and operations. Devops emphasizes collaboration and integration between app developers and IT operations professionals.These 10 business advantages of DevOps can help you see why it's important for organizations to adopt this methodology if they want to stay competitive in the digital economy.
DevOps vs Agile | DevOps Tutorial For Beginners | DevOps Training | EdurekaEdureka!
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This is a short tutorial by Edureka on DevOps vs Agile, which will help you understand the fundamental difference between DevOps and Agile software development strategies.
What is DevOps? | DevOps Introduction | DevOps Tools | DevOps Tutorial For Be...Simplilearn
This presentation on DevOps will help you understand what is DevOps, how DevOps came to being, stages and tools of DevOps, implementation of DevOps, DevOps practices, benefits of DevOps approach and at the end, you will also see a use case of DevOps approach by Etsy. DevOps is a software engineering culture that unifies the development and operations team, under an umbrella of tools to automate every stage. The benefits of DevOps outweigh the potential difficulties. Aligning the two transparency-limited silos ensures that systems are delivered faster, and also reduces risks in production changes through nonfunctional and automated testing, as well as shorter developmental iterations. The DevOps approach automates the service management for the support of operational objectives and improves understanding of the layers in the production environment stack. In turn, this helps prevent and resolve production issues. Now, lets deep dive into these slides and understand what actually DevOps is.
Below topics are explained in this DevOps presentation:
1. How DevOps came to being
2. What is DevOps?
3. Stages and tools of DevOps
4. Implementation of DevOps
5. DevOps practices
6. Use case: DevOps approach by Etsy
7. Benefits of DevOps approach
Simplilearn's DevOps Certification Training Course will prepare you for a career in DevOps, the fast-growing field that bridges the gap between software developers and operations. You’ll become en expert in the principles of continuous development and deployment, automation of configuration management, inter-team collaboration and IT service agility, using modern DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios. DevOps jobs are highly paid and in great demand, so start on your path today.
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet and Nagios in a practical, hands-on and interactive approach.
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
1. This DevOps training course will be of benefit to the following professional roles:
2. Software Developers
3. Technical Project Managers
4. Architects
5. Operations Support
6. Deployment engineers
7. IT managers
8. Development managers
Learn more at https://www.simplilearn.com/
DevOps is a software development method which is all about working together between Developers and IT Professionals. This presentation gives you an introduction to DevOps.
That DevOps and Agile bring benefit is self-evident; these slides explore how the key benefits can be quantified such that a business case can be built.
Next Generation IT Delivery - What it means to deliver atthe speed of the Dig...Mirco Hering
We live in the Digital Age and IT delivery needs to get faster and faster...I presented this point of view at the Accenture Test Symposium in Australia in 2015.
Accenture DevOps: Delivering applications at the pace of businessAccenture Technology
Are you ready to shift to continuous delivery? DevOps, a leading software engineering innovation, makes this shift possible by bringing business, development and operation teams together to streamline IT and applying more automated processes.
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype
There are numerous examples of DevOps and Continuous Delivery reference architectures available, and each of them vary in levels of detail, tools highlighted, and processes followed. Yet, there is a constant theme among the tool sets: Jenkins, Maven, Sonatype Nexus, Subversion, Git, Docker, Puppet/Chef, Rundeck, ServiceNow, and Sonar seem to show up time and again.
DevOps, SAFe and critical information bearers: A practical approach for plann...Bosnia Agile
A lot of enterprises have successfully adopted agile practices and are now challenged by the questions: How do we scale it? How will we know what is going on in development, product management and deployment? How do we know that we develop according to business priorities? How do we make the quicker development cycles lead to faster market response and more frequent releases? To answer these some companies have turned to a DevOps approach and use concepts like the Scaled Agile Framework (SAFe). Join us in this session to look at the critical information bearers in such a setup and how information from business planning, portfolio management, program management and release planning are connected.
Ignite Presentation by Derek E. Weeks
Pictures help describe how we work, how our work flows, and what’s actually flowing where. I'll share insights from 31 DevOps and Continuous Delivery real-world reference architectures that have been key to building DevOps empathy -- when it’s not about people and who screwed up...it’s about a picture of a system that works great or needs improvement.
from 0 to continuous delivery in 30 minutesAgileSparks
In this session we will explore the full continuous delivery cycle from check-in to production using set of popular tools. During the session the attendees will be introduced to a set of tools and practices that enable continuous delivery from the technical point of view.
he 7 habits of Highly Effective Organization that Embraced DevOps - Oded TamirAgileSparks
Adopting DevOps will have major impacts on many organization aspects since DevOps is not only technical but mainly Business, Organizational and Cultural oriented initiative.
This is the reason why the success factors of DevOps implementation should be measured by business KPIs such as ROI (Return On Investment), TTM (Time To Market), OTC (Order To Cash) or others business parameters.
“The 7 habits of Highly Effective Organization that Embraced DevOps” presentation will help organizations to better understand the habits they need to adopt while implementing DevOps in order to achieve the business goals.
We at Whitehedge help you build better systems. Systems which help you accelerate and scale your business. DevOps adoption is very specific to each business case. It is important to align your business vision with DevOps vision.
Monitoring Attack Surface to Secure DevOps PipelinesDenim Group
A web application’s attack surface is the combination of URLs it will respond to as well as the inputs to those URLs that can change the behavior of the application. Understanding an application’s attack surface is critical to being able to provide sufficient security test coverage, and by watching an application’s attack surface change over time security and development teams can help target and optimize testing activities. This presentation looks at methods of calculating web application attack surface and tracking the evolution of attack surface over time. In addition, it looks at metrics and thresholds that can be used to craft policies for integrating different testing activities into Continuous Integration / Continuous Delivery (CI/CD) pipelines for teams integrating security into their DevOps practices.
Without Self-Service Operations, the Cloud is Just Expensive Hosting 2.0 - (a...dev2ops
Damon Edwards (DTO Solutions) presentation at Cloud Expo 2014 Santa Clara.
We are all here because we are sold on the transformative promise of The Cloud. But what good is all of this ephemeral, on-demand infrastructure if your usage doesn't actually improve the agility and speed of your business? How must Operations adapt in order to avoid stifling your Cloud initiative?
Mark Mzyk
Engineering Manager with Chef
Find more by Mark Mzyk: https://speakerdeck.com/mmzyk
All Things Open
October 26-27, 2016
Raleigh, North Carolina
A keynote presentation comparing/contrasting old & new SDLC methodologies that was used to kick off an internal agile meetup focused on standardizing on the Atlassian suite of SDLC tools.
stackconf 2023 | Better Living by Changing Less – IncrativeOps by Michael Cot...NETWAYS
DevOps has always been about dramatic changes to improve IT. You don’t only need to use a different set of tools, you need to change your entire IT culture! It’s all exhausting, really. Worse, this imperative to change never goes away. Will we ever actually be done and “be like Google”? Instead of carrying the flag of “change or die,” this talk proposes an alternate, more practical, sustainable, and comforting approach to improving: IncrativeOps.
How (can) Scrum and DevOps Walk Together to Build a High-Quality Product Deli...Scrum Day Bandung
Discussion in fishbowl format to find out how Scrum and DevOps should more power-full if we use it together and properly, then validating with data and convergence of CEO Scrum.org and CEO DevOps Institute.
What can DesignOps do for you? by Carol Smith at TLMUX in MontrealCarol Smith
You have probably seen the terms DesignOps and/or ResearchOps float by in your social media queue. These teams make designing (and researching) at scale beautifully efficient and successful. Carol steps through how these teams work, the types of activities they perform, situations they are helpful for, and ways you can leverage these types of programs in your organization. Carol will share examples from her experiences and stories from other organizations that are using Design Ops to do effective design at scale.
Presented at Tout le monde UX in Montreal, Quebec, Canada on February 28, 2019. http://toutlemonde-ux.com/
Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.
How To (Not) Open Source - Javazone, Oslo 2014gdusbabek
Releasing an open source project while maintaining a shipping product is hard! Different behaviors, attitudes and actions can help or hinder your cause; and they are not always obvious.
The Blueflood distributed metrics engine was released as open source software by Rackspace in August 2012. In the succeeding months the team had to strike a manageable balance between the challenges of growing a community, being good open source stewards, and maintaining a shipping product for Rackspace. Find out what worked, what did not work, and the lessons that can be applied as you endeavor to take your project out into the open.
In this presentation you will learn about strategies for releasing open source products, pitfalls to avoid, and the potential benefits of moving more of your development out in the open.
We have also made a few realizations about the community growing up around metrics. It is still young, and there are problems that come with that youth. I'll talk about some things we can do to make a better software ecosystem.
Lean UX - Applying Lean Principles to improve
User Experience in Agile environment. It accomplishes this by getting out of the deliverables business and instead focusing on successful experiences.
Real World Lessons Using Lean UX (Workshop)Bill Scott
Half Day Workshop given 5/22/2013 at WebVisions Portland.
In this workshop Bill will explore the mindset of LeanUX and how it relates to bring products to life in the midst of big organizations that don't normally think "Lean". He will look at how teams can create a strong partnership between product, design & engineering in a way that tears down the walls and instead focuses on three key principles:
Shared understanding
Deep collaboration
Continuous customer feedback
The workshop will take a look at how Bill has been able to apply Lean UX at PayPal — a place that in recent years has been the total antithesis of the lean startup idea. With very specific examples, he will share lessons learned applying lean to the full product life cycle as well as how it relates to agile development.
Finally, the workshop looks at the technology stack. In the last few years there has been an explosion of open source technology stacks that can support rapidly creating products, launching them to scale and rapidly iterating on them when live. While startups embrace these stacks from the get-go, large organizations struggle with how to embrace this change. This workshop will also look at the shift that has happened, what is driving this change, and how organizations can embrace this stack and how to marry Lean Tech with Lean UX.
Why Your Team Has Slowed Down, Why That's Worse than You Think, and How to Fi...C4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1ytDjEW.
Edmund Jorgensen discusses how and why engineering teams slow down, showing how attempts to manage costs in the face of slowdowns can death-spiral into worse delays with deadly economic consequences. Filmed at qconnewyork.com.
Edmund Jorgensen is a co-founder at Hut 8 Labs. Before Hut 8 Labs he worked at HubSpot, TripAdvisor, and a number of startups (some of them also with camel-cased names), where he led teams, designed and coded high-traffic systems, and carried the pager. He is especially interested in the operational and economic aspects of software.
How to Ship in 8 Weeks or Less (via Cross-Functional Teams)QuekelsBaro
Get you clued up on what the development methodology Shape Up looks like in practice and sneak-peak into what we do at Process Street as our EPD team shares their secrets.
Software Development Life CyclesPresented byBrenda Reynold.docxrosemariebrayshaw
Software Development Life Cycles
Presented by
Brenda Reynolds
In association with
Matt Henwood and the University of Phoenix Systems Analysis & Development Department
September 13, 2019
We Love Video, Inc.
Welcome to the presentation guys, have a seat anywhere you’d like and help yourselves to some coffee and pastries. This is my bribe to you so you like me and pay close attention to the details I’m about to give you. Your fabulous company has decided to put a CRM in place for you guys, does anyone know what that is?
Kelsey: A What?
C.R.M. it’s one of many acronyms people in IT use.
Robin: Something about Customer Management?
Yes, can anyone elaborate?
Jesse: Customer Relationship Management, I used Salesforce at my last job. I have to tell you guys if this is what they’re doing for us, you’re going to notice a huge difference in how easy it is to find what you need on any customer.
Me: Well thank you for making my job a little easier.
<Audience Laughter>
I’ve done this a whole lot, so I already have a CRM in mind, and yes it will be Salesforce. I love that software for many many amazing reasons. What I want to educate you guys on today is the Software Development Life Cycle and of course there are multiples of those too. I’m going to fill you in on two SDLC’s, how they work, and why we will be using the one that we’ll be using. This is important because it involves you and how you’re going to help us integrate the new CRM into your every day processes.
1
Waterfall SDLC
See how this water looks like it’s on a mission to rush down those steps? Keep this in mind while I describe the Waterfall SDLC, more acronyms, I know. With the waterfall model we have some typical phases that comprise an entire systems project. Makes it easy, right? Just follow the waterfall down and you’ll get to the completed CRM. The reason I say ‘rushing’ is because the waterfall model is focused on getting the project done, get the requirements, get it done and get outta there.
On the next slide we’re gonna see what these steps look like, but does anyone want to take a stab at the first step?
Alyssa: Get the band back together and write down a plan. I can’t imagine computer nerds do this stuff without first knowing what the finished product is supposed to look like.
Me: YES! First and foremost we have to Plan. If we don’t have a plan, what are we building? Not even the best of the best “computer nerds” should start working on something like this for a company without a plan.
2
The typical phases that comprise an entire systems project
Agile
SDLC
Who can tell me what these guys are doing?
Robert: PARKOUR!!
Me: Wow, you must like the thrill of being able to do this stuff. What word would you use to describe someone who has the ability to do this?
Robert: Adventurous, thrill seeker, well trained
Alyssa: Dare devil
Me: This is awesome! What about flexibility?
Audience: yes, that works, of course, yeah…
<Click>
Remember we’re talking about soft.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
2. AGENDA
I. Organization structures and necessary tensions
II. Common anti-patterns in shifting towards DevOps
III. Tools for a logical rather than structural view
IV. Mapping your organization to a logical view
(the business parts)
V. DevOps Organizational Transition Guidance
VI. DevOps Technical Transition Guidance
3. CONWAY’S LAW
DevOps does not live in a vacuum…
“Organizations which design
systems ... are constrained to produce
designs which are copies of the
communication structures of these
organizations.”
-Melvin Conway (1967)
4.
5. ONE TEAM, ONE PRODUCT
The team discusses and arrives at a decision.
Let’s do
A.
ProductProduct
11
7. TWO TEAMS, ONE PRODUCT
Perhaps some differences of opinion on security or architecture, but
we align on what needs to ship when and get through it.
Let’s do A.
Product 1Product 1 Product 1Product 1
Maybe A’ but
OK
8. THREE TEAMS, TWO PRODUCTS
Let’s do A.
Product 1Product 1
Let’s do B.
Product 2Product 2
Product 1Product 1
Let’s do C.
Product 2Product 2
9. THREE TEAMS, TWO PRODUCTS
Let’s do A.
Product 1Product 1
Let’s do B.
Product 2Product 2
Product 1Product 1
Let’s do C.
Product 2Product 2
14. MATRIXED ORG – DEV VS OPS
$
SLA / Uptime
$
New Feature Delivery
15. DEVOPS ANTI-PATTERNS – THE LONE CONSULTANT
I just met you, yet I fully believe you
have the ability to solve the problems
I've been struggling with for years. My
manager and the product owner have
allocated time for me to both learn new
techniques and contribute as a subject
matter expert to help with the
infrastructure provisioning/deployment
automation. I'm really excited.
I just met you, yet I fully believe you
have the ability to solve the
problems I've been struggling with
for years. I don't have any official
time to work on this, but I'll find
some spare time to help somehow.
I'm really excited.
I’m here
to help!
16. This has been a mess for years. It's
really complicated and you don’t know
what you got into. I’m pretty busy
though and don’t really have time to
waste on this and I’m not paid by the
hour. You’ll be here today and gone
tomorrow.I’m here
to help!
DEVOPS ANTI-PATTERNS – THE LONE CONSULTANT
17. DOAP – THE LONE “DEVOPS” HIRE
I’m here
to help!
This has been a mess for years. It's
really complicated. I’m pretty busy
though and don’t really have time to
waste on this. You’ll see for yourself.
Put in a ticket to request source
control access. Nothing is
documented too well. Maybe you
can make the app compile. Good
luck though.
18. DOAP – THE REBRANDED DEVOPS TEAM
I haven’t done this before
and I’m still doing my day
job as SysAdmin, Release
Engineer, but I’m here to
help!
That’s OK! We’re both behind on
our day jobs, but we’ll find some
spare time and learn and work on
this together! I'm really excited.
19. DOAP – THE PURPOSE BUILT DEVOPS TEAM
We have experience in this
area and time and are here
to help!
That sounds neat. Wait, do I work
with you or IT? IT wanted to do
something else and I don’t have
time to work through this. Why
don’t you figure this out with them?
20. WHY ALL THE ANTI-PATTERNS?
DevOps is not the
language of the rest of
the business.
You can’t just keep
using the word across all
levels of the company
and expect orderly
change.
Need to frame the transformation within
the business context and language
Need a better way to model the
organization
25. COMMANDOS, INFANTRY, AND POLICE
Think of the growth of a company as a military operation, which isn't a stretch, given that both enterprises involve strategy, tactics, supply line,
communication, alliances and manpower.
- Cringely, Robert X. Accidental Empires. Reading, MA: Addison-Wesley, 1996. 235-238. Print.
Commando's parachute behind enemy lines or
quietly crawl ashore at night. Speed is what
commandos live for. They work hard, fast, and
cheap, though often with a low level of
professionalism, which is okay, too, because
professionalism is expensive. Their job is to do
lots of damage with surprise and teamwork,
establishing a beachhead before the enemy is
even aware they exist. They make creativity a
destructive art.
But what they build, while it may look like a
product and work like a product, usually isn't a
product because it still has bugs and major
failings that are beneath the notice of commando
types. Or maybe it works fine but can't be
produced profitably without extensive redesign.
Commandos are useless for this type of work.
They get bored.
Most of business and warfare is conventional. But
without commandos you'd never get on the
beach at all.
Grouping offshore as the commandos do their
work is the second wave of soldiers, the infantry.
These are the people who hit the beach en
masse an slog out the early victory, building the
start given by the commandos. The second wave
troops take the prototype, test it, refine it, make it
manufacturable, write the manuals, market it, and
ideally produce a profit. Because there are so
many more of these soldiers and their duties are
so varied, they require and infrastructure of rules
and procedures for getting things done - all the
stuff that commandos hate. For just this reason,
soldiers of the second wave, while they can work
with the first wave, generally don't trust them,
though the commands don't even notice this fact,
since by this time they are bored and already
looking for the door. While the commandos make
success possible, it's the infantry that makes
success happen.
What happens then is that the commandos and
the infantry advance into new territories,
performing their same jobs again. There is still a
need for a military presence in the territory.
These third wave troops hate change. They aren't
troops at all but police. They want to fuel growth
not by planning more invasions and landing on
more beaches but by adding people and building
economies and empires of scale.
Commandos Infantry Police
Original Publication: 1991
Revised: 1996
26. SPOTIFY GUILD MODEL
Scaling Agile@ Spotify
With Tribes,
Squads,
Chapters
& Guilds
Henrik Kniberg &
Anders Ivarsson
Oct 2012
27. SPOTIFY GUILD MODEL – SELF CONTAINED TEAMS
D – Dev
Q – QA
S – SysAdm / DevOps
p - Pioneer
s - Settler
t - Town Planner
Dp
Ds
Dt
Qp
Qs
Qt
Sp
Ss
St
Dp
Qt
St
Dt
Ds
Ds
Ds
Qp DevOps
Guild
Ds
Ds
Qp
Ds
Ss
SsQs
Dp
SpDevOps
Guild
X,Y
28. SPOTIFY GUILD MODEL – MATRIXED TEAMS
D – Dev
Q – QA
S – SysAdm / DevOps
p - Pioneer
s - Settler
t - Town Planner
Dp
Ds
Dt
Qp
Qs
Qt
Sp
Ss
St
Dp
St
DsDs
Qp
Ds
Qp
Ds Ss
SsQs
Sp
DevOps
Guild
X,Y
IT IT
29. PREPARING THE STRUCTURE PLAN
Overlay virtual teams with
P/S/T exercise to get at an
effective design you need
It contains our desired
mix of product maturity
lifecycle domain
expertise
How do we make it
happen?
We have a desired end
goal virtual team
DevOps Guild layout
30. DEVOPS TEAM TO DEVOPS GUILD
Key permanent core members serve as:
Facilitators
Evangelists
Incubators of environment/deployment/monitoring practices
Curators of established reference models
Recipients of outside training and leaders of internal training
DevOps Team → Tools & Automation Practices Team
Satellite members from dev/QA teams:
SME’s for application internals
Know highest risk areas needing better monitoring/logging
Know definition of success, how to test for it, transition as much as
possible to automatic
31. DEVOPS TEAM IS NOT
Your permanent new release management team
•Manual practice and understanding of deployment WITH Dev and/or IT
is a very short term step to automation
•End Goal: Release responsibilities should be automated and then
owned/initiated by the dev teams
On hand team augmentation for general Dev/IT/SysAdmin
•Temptation to pull people for other tasks/fires can be great
•BUT Some group needs a focus on continuous improvement activities
leading towards faster and safer releases or there won’t ever be less
fires.
Change this maybe not tomorrow, but soon.
32. TRUE CROSS-TEAM EFFORT
Dev needs official time for collaboration on automation and monitoring
QA needs official time for collaboration on automation, data setup, and
automated testing
Long-term program NOT one person’s lone side project
33. FACILITATION IS IMPORTANT!
SIMPLE METAPHOR…
Mgr Email To: Bob, Nancy, Jim, Sally
Subject: Please get X done
Result: Waiting. Some pockets of activity.
Instead…
Mgr Email To: Nancy
CC: Bob, Jim, Sally
Subject: Please get X done with assistance from Bob, Jim, Sally
Result: Everyone is accountable. Nancy will facilitate. Self organize from there.
Given management support, DevOps team can facilitate.
34. FACILITATION IS NOT HEAVY PROJECT MANAGEMENT
1. There should not be comparable time meeting and talking about tasks not
getting done as time spent working on them.
2. Pairing at one computer with someone on another team IS helpful.
3. Start with agreement on shared goals and time commitment. You’ve failed
already without this.
4. Initially work can be entered, estimated, and prioritized in each team’s home
tracking system (JIRA, tickets, etc) rather than adding a side process to each
team. Make any alignment points or deadlines clear to all.
5. Track and celebrate measurable overall DevOps goals progress.
IF (Issues) GOTO 3
6. Revisit cross-team work process as needed.
35. CHALLENGES
Moving from recreational to organized sports often takes
painful unlearning of old techniques and learning new
ones and being worse in between
Setup will get more complex before it gets easier
After better abstractions and automation are in place, it’s
far better than before
- Arthur C. Clarke.Any sufficiently advanced technology
is indistinguishable from magic..
-Arthur C. Clarke
37. WORKING TOGETHER
We need to change the culture, especially in IT operations,
from one of viewing ourselves as ‘order takers’ to one of being
full team members.
-Gene Kim
38. GENE KIM?
We need to change the culture, especially in IT
operations, from one of viewing ourselves as ‘order
takers’ to one of being full team members.
-Gene Kim
Creator and CTO of Tripwire – one of the first file integrity
monitors authorized in PCI DSS
Author of prominent ITIL book
Well respected security community member
DevOps thought leader
Author of prominent THE DevOps book
40. LISTEN AND RE-EVALUATE
3. Can a different
process meet the
need BETTER
than before for all
involved?
2. Which
processes
are
structural
rather than
logical?
1. LISTEN to
goals and
processes of
pre-existing
groups
44. COMMUNICATE, REPEAT, REPEAT, REPEAT, REVIEW
Make it a real
project & hold
people accountable
for doing their part
Review and revise
Communicate plans and expectations
repeatedly all the way down to dev
managers / team leads. Everyone’s
direct boss needs to know the
importance of the work and have time
budgeted. Hard to ask people to spend
time on things without their direct boss
buy-in
45. FINAL TIPS ON ORGANIZATIONAL CHANGE
The structuring and often restructuring of departments
isn’t done by people that are irrational.
Complaining about the structures without making any
attempt to understand the underlying motivation is not
helpful.
The most productive negotiations come from a place of
mutual understanding (people need to feel heard)
Lead not only with what change you need, but also what
aspects the other side will also find agreeable
46. WE TRIED THAT ALREADY…
What was different?
Did any parts get traction at any point?
Did you have budget and time allocated for all required team
members?
Was progress on DevOps initiatives a real project with people
accountable for progress?
Did progress stop before reaching a more user friendly automation
end state?
Did you start with the most complex project before hitting a rhythm
and building experience and reusable work?
50. SECURITY / COMPLIANCE – DEV ACCESS
Dev access to prod servers is a further discussion point.
Ideally it can be arranged, but either way there are techniques to reduce the
need for it for many situations.
51. SECURITY / COMPLIANCE – DEVSECOPS MANIFESTO
Leaning in over Always Saying “No”
Data & Security Science over Fear, Uncertainty and Doubt
Open Contribution & Collaboration over Security-Only Requirements
Consumable Security Services with APIs over Mandated Security Controls & Paperwork
Business Driven Security Scores over Rubber Stamp Security
Red & Blue Team Exploit Testing over Relying on Scans & Theoretical Vulnerabilities
24x7 Proactive Security Monitoring over Reacting after being Informed of an Incident
Shared Threat Intelligence over Keeping Info to Ourselves
Compliance Operations over Clipboards & Checklists
http://www.devsecops.org/
http://rewrite.ca.com/us/articles/devops/integrating-infosec-into-the-daily-work-of-dev-and-ops.html
http://techbeacon.com/detailed-analysis-isacas-10-key-devops-controls
52. EVALUATE, AGREE, & MOVE ON
Both have more in common than
not
Little value starting a new initiative
and teams already diverging on
which they use
55. BOLD END STATE GOAL – DEV LAPTOP
ENVIRONMENT
Aim high!
Set a goal to have an end to end testing
environment on a dev laptop with one
command.
•Any tier >1 server in prod is >1 in laptop
environment
•Local data tier with auto-loaded test data
•Unit and integration tests ready to run
•3rd
party services simplest fake that works
•Not trivial but not as hard as people think
Share this quote BEFORE comments start:
Try replacing "we can't because.."
with "we can't until..." and then
we can when..."
-Kent Beck
57. EVERYTHING IS ABOUT FEEDBACK LOOPS
How fast can you identify an issue if you’re free to tear down, restart, turn on
insane level debug logs ANY time you want?
58. NEXT STEPS
Parallel Streams
1.Set up budget/time for training and post training implementation practice for
DevOps culture soft skills & automation for promising DevOps core team members
2.Start training
A.Socialize ideas here to teams
B.Select a project (ideally with change interested engineers on it)
C.Map it to est. Pioneers, Settlers, Town Planners mix
D.Lay out your DevOps Guild (logical/virtual cross-team group)
E.Identify possible member fits from current DevOps team, dev teams, IT
F.Agree on time, budget for activities
G.Share those with DevOps Guild and collaboratively agree on plan with milestones
fitting in time/budget (highly dependent on existing skillset and ramp up on possibly
new technologies)
H.Start initiative
59. ADDENDUM 1: DEVOPS RESOURCES
DEVOPS WORKS FOR ENTERPRISE
SAP Global IT – Continuous Delivery: From dinosaur to spaceship in 2 years
DevOps Enterprise Summit - http://devopsenterprise.io/
DOES Presentations on YouTube
Puppet Labs State of DevOps 2015
DevOps Days – How not to do DevOps: Confessions of a “thought leader”
60. ADDENDUM 2: DEVOPS RESOURCES
DEVOPS WORKS FOR FINANCIAL COMPANIES
Continuous Delivery - The ING Story: Improving time to market
www.slideshare.net/.../continuous-delivery-the-ing-story-improving-time...
Dec 3, 2014 - Continuous Delivery - The ING Story: Improving time to market with
DevOps and Continuous Delivery. 1. Continuous Delivery - The ING Story ...
From Idea to Implementation: DevOps Enabled Agile ...
devopsenterprise.io/.../from-idea-to-implementation-devops-enabled-agil...
Oct 20, 2015 - Three years into an Agile transformation at Bank of America, an
executive who led the effort will take a look at what his team learned along the ...
Capital One Launches Hygieia Open-Source DevOps ...
www.eweek.com/.../capital-one-launches-hygieia-open-source-devops-d...
Jul 27, 2015 - Capital One's engineering team developed a DevOps dashboard called
Hygieia that the company has open-sourced.
61. ADDENDUM 3: USEFUL TANGENTS TO DEVOPS
John Willis: “Devops and Dr. Deming’s 14 Points”
(Velocity NY 2014)
66. Q&A / THANK YOU!
Ask Questions / Share
Concerns
now and/or later
Email: alecl@alecl.com
Editor's Notes
Collection of experience from
* a 20 person small company in the late 90’s and 2000’s
* a global 30,000 person education technology company leading products with millions of students
* a modern startup
* conversations with many industry leaders
Note: Conway’s Law is over 50 years old
Narrative and context is crucial.
The novels The Phoenix Project or The Goal wouldn’t have been as successful had they been two page blog posts with action items.
Let’s dig in.
In the beginning life was simple…
It’s easy to feel part of one team with one mission if you’re all a few feet apart and on the same product.
Features vs Non-Functional Requirements is a timeless concern.
Tension is not a bad thing. Constructive debate keeps you from going to either extreme. Clear value on both sides.
You have no balance this even in a team of 1. It’s not simply structural to an organization but the core of software delivery itself.
Not just enterprise. This applies to growing small companies or even divisions too…
Entering a new market? Working with a strategic partner?
You can’t have 30+ people in a single standup, fully aligned, working closely and in sync in same area without some further structure.
You can call it teams with team leads, holacracy, whatever. It will be different than one team of 4-7 people.
Word product is overloaded
Replace Product with
API
iOS / Android App
Even Microservice
More products -&gt; potentially divergent business and technology goals and schedules
Now things are complicated…
Things get heated and progress slows. What if you didn’t centralize any infrastructure/operational concerns? The dream of Microservices! Is everything fine? [click]
Maybe… but it has its own risks. [click]
Each team reinvents the wheel. Some probably better than others.
Teams needing to grow or shift have more significant ramp up times
Different services will have different maturity and stability
Less people know the deep details of every backend. Bus factor.
Whether you grew as a matrixed organization or self-sufficient teams, you’re likely considering these tradeoffs [click]
Given prominence of Git, we seem to like decentralized nowadays.
What if we change the words a bit…[click]
Hmm. Well, innovation and freedom sound pretty good still, but standardization is not bad. [click]
Now the top doesn’t sound like a clear winner at all.
We like to not repeat ourselves. We like scale and consistency.[click]
The terms on the top and bottom are all valid expressions of the same forces to balance in an organization.
Depending on which side you’re arguing for you may use one or the other. As situations change you may jump between sides. This is normal.
Difference between Dev and Ops is a four letter word [click]
Traditional operations/security culture wants to minimize risk, but moving too slowly has its own risks of being overtaken by more nimble competitors [click]
Demands increase and systems decay so some non-code change can be inevitable. Nimbleness will help you for many origins of change.
The previous tensions are still applicable and valid regardless of your organizational structure
It just gets more polarized in a matrix.
Grossly simplified view. Certainly sales can suffer due to downtime and overall company revenue will suffer if features aren’t competitive and responsive.
So we’ve set the stage. How does DevOps get unfortunately introduced? [click]
How often do team managers plan for time for assisting with a new outside initiative? ALMOST NEVER!
Employees putting in extra time to help someone new that they don’t know or trust when they’re probably behind? UNLIKELY
This is far more likely. A little demotivation for the new person and not much help.
Oh, and if it’s a single full time hire and not a consultant? Maybe someone with “DevOps” in their title? [click]
Perhaps it’s a full time employee and not a consultant. Your team will likely be slightly nicer.
Maybe the new person will be pointed in a direction or even helped for a couple of hours.
Then it’s back to the grind.
The newest person is the wrong person to re-live all the sins of the past of a project ALONE
The DevOps team is still busy doing manual releases and whatever else they used to do, have received no time or training for their new roles, but they are still expected to save the day.
So this is starting to sound better. There’s at least some area of focus.
But still time and lack of concrete direction issues. [click]
On top of that we’ve made another silo and isolated teams with the same goals leads to confusion, delays, duplication of effort, and even turf wars. [click]
So based on these real examples, I’m clearly leaning towards a direction here now, but before we get there let’s take a step back and look at some tools on how we can be intentional about designing organizational structures and not going totally with gut feel.
Why all the anti-patterns? It’s not from ill intent.
&lt;summarize&gt;
We need a different diagram…
Take a step back…
If you’re planning out an office you don’t start with a physical view first.
Why is a logical view important? It focuses on responsibilities, skills, culture, and goals FIRST
NOT on management reporting structures
You need to agree on a logical view of what people are doing where first.
The same applies to your organization structure and the architect in me loves the ideas of a diagram for intentional organization planning and not just an org chart
We’ll look at some mapping tools from Simon Wardley
Early cloud pioneer and organizational thought leader
Creative Commons Attribution-Share Alike 3.0 License.
Pioneers, Settlers, and Town Planners
It’s a far different context building early products that aren’t monetized where maybe a fail whale is OK compared to having multimillion dollar contracts and SLAs to uphold. You don’t necessarily have a town planner mentality trying out new business models but once significant money is being paid to you for services you better have started thinking that way.
Note how work is moved/stolen forward and comes full circle where the most commoditized items can again be used by pioneers. If you have a great logging infrastructure that’s probably no longer a place of innovation. Pioneers can take that and focus efforts on innovation.
CULTURAL norms in different phases are key on to consider
It’s worth really digging into this slide in more time than we have here so definitely go back to it. If nothing else appreciate the value of each role in a mature and sophisticated organization or product.
Your next step is to align your products with an approximate mix of these 3 roles. These are made up examples and won’t all necessarily be at the same company. [click]
Product 1 – Legacy product bringing in a lot of revenue and still has customer growth. New features are useful and attract customers but not revolutionary changes. High desire for stability and economies of scale. Settlers and Town Planners. [click]
Product 2 – Product is 2-3 years old. Still innovating but bringing in paying customers as well. Pioneers still around. Mostly settler mentality helping move towards town planners. [click]
Product 3 – Released 6 months ago. We have paying customers, but still rapidly evolving. This is our first product so no town planner components to rely on yet internally. Probably some external equivalent SaaS offerings though… [click]
Product 4 – Released 2 months ago MVP spin off from original business idea product. We have some town planner infrastructure to help us out. Still innovating rapidly. Not making money yet. Probablly no settlers needed until we prove it out more. [click]
This classification was enhanced and extended by Wardley, but he recognizes he’s seen it elsewhere first. [click]
Robert X. Cringely in Accidental Empires called the roles Commands, Infrantry, and Policy.
The gist is strikingly similar to Pioneers, Settlers, and Town Planners.
Rather than bastardize this great narrative I left the original. You can read it later.
Spotify has self-contained delivery teams called squads. They are ANTI-MATRIX.
Chapters are cross-team virtual organizations of the SAME role (like QA or Dev for instance) for shared efficiencies in learnings
Guilds are a virtual cross-functional team across roles to increase consistency and context.
Tribes are functionally similar areas where multiple delivery teams work. Generally no more than 100 people in a tribe.
Read their paper and watch their videos. While not always perfect or exactly as planned even at Spotify, it’s worth considering compared to alternatives.
How does this help us? [click]
Yes, there are pioneers in DevOps. It’s not all standardization from the start or forever. You have to try out new things sometime before rolling out all over.
If you have a moderate sized organization you won’t have a single DevOps Guild. [click]
You’ll have a few that serve products with similar maturity needs.
This shows all the sysadmin in IT (plus network engineers/etc., just an example)
You’ll find successful people in your organization are unofficialy doing this through relationships.
Why not do it intentionally rather than have success and prioritization be decided unofficialy by relationships rather than business value?
Here’s where we are so far.[click to end]
First we want to clarify the role of the current DevOps team and perhaps rebrand it.
This may not happen
Side projects are good to explore, but they need to be socialized and operationalized
Management is part of this effort!
They provide time, budget, and cover from distractions.
What happens?[click]
Some activity but not a fast way to solution.
Now in this case who is accountable?[click]
Everyone. They were called out to help, but now someone can facilitate and prompt the group.
Email back and forth to solve a technical challenge get wasteful fast.
Sit together or screenshare.
Founder and creator of one of the early and most successful Unix security audit tools
Author of a prominent ITIL book
What does he think of DevOps?… [click]
He’s one of the people that helped catapult its popularity with the seminal book about it!
It is not incompatible to care about security and embrace DevOps. No one is asking to throw out quality or security. Not everything is a tradeoff. Done right those can improve alongside speed of delivery.
1. LISTEN to goals and processes of pre-existing groups AND business
2. Which existing rules and processes are structural (recall Conway’s Law) rather than logical (no pun intended)?
3. Can a different process meet the need BETTER than before for all involved?
Repeat this cycle periodically
--
For example if you have a sign off gate where a VP needs to approve a release or security review can that be solved better through automated security, performance, and quality checks and delegating to the team itself? What if you’re no longer sharing environments so a bad release won’t affect another team? Why slow down then?
Getting budget isn’t easy [click]
Quick aside on Starbucks
In the mid 2000’s they had a decline in sales.
Brainstormed a way to improve quality and they shut down all stores for 3 hours in 2008 so baristas can be re-trained to make the perfect cup of coffee
It cost them $6 million
Improved experience led to increased sales that made up for the one time loss and kept going [click]
Sometimes you have to stop doing the same thing and take a short term productivity hit to get to the next level and far exceed your ability to deliver future value
Not every initiative or customer feature is critical.
Consider what can wait a bit to ultimately build a better foundation for better productivity in the future?
General security practices like granular rights and audit trails can be MORE effectively implemented with automation
Use your providers monitoring/tagging/etc to its fullest, but for app config use AS LITTLE AS POSSIBLE
Almost all your app config should be driven by a modern configuration platform like Chef or Puppet. Pick ONE. Just ONE.
Adhoc scripts not called through Chef/Puppet should be minimized
What does this get you? [click]
Simplicity and consitency in environments.
Have a Dev environment per team, per version, spun up or down whenever needed.
Have your devs and sysadmins have a local way to troubleshoot and experiment
Plus more [click]
Truly mission critical as in life or death or millions of dollars on the line? DR to another cloud vendor [click]
Hybrid cloud if you have apps in a datacenter (or a company you buy does) [click]
Need to cut costs or be able to negotiate with your cloud vendor? Tell them you literally have apps running in a competitor’s cloud.
I snuck in Dev Laptop before. That’s actually a hugely powerful end goal. [click]
Shared data or services are a pain. Don’t worry about stepping on anyone else. Deal with your own test data.
Imagine the end state and then back track with how to get there.
Don’t use the one most complicated, problematic app as an excuse to not move something forward first
Your personal feedback loop -&gt; up to your team’s feedback loop -&gt; you company’s feedback loop
Imagine how fast a developer can troubleshoot and learn if the whole site is on their laptop
W. Edwards Deming philiosophy of quality AND cost improvement
Goldratt’s theory of constraints
Toyota lean manufacturing
Shu Ha Ri – Japanese martial arts stages of learning to mastery
All brought up for a few years now and well worth your time to become familiar with
You can consider aligning your teams across where in the product evolution they stand.