Some companies think that adopting devops means bringing in specialists or a host of new tools. With this practical guide, you’ll learn why devops is a professional and cultural movement that calls for change from inside your organization. Authors Katherine Daniels and Jennifer Davis provide several approaches for improving collaboration within teams, creating affinity among teams, promoting efficient tool usage in your company, and scaling up what works throughout your organization’s inflection points.
Devops stresses iterative efforts to break down information silos, monitor relationships, and repair misunderstandings that arise between and within teams in your organization. By applying the actionable strategies in this book, you can make sustainable changes in your environment regardless of your level within your organization.
Explore the foundations of devops and learn the four pillars of effective devops
Encourage collaboration to help individuals work together and build durable and long-lasting relationships
Create affinity among teams while balancing differing goals or metrics
Accelerate cultural direction by selecting tools and workflows that complement your organization
Troubleshoot common problems and misunderstandings that can arise throughout the organizational lifecycle
Learn from case studies from organizations and individuals to help inform your own devops journey
What Is Devops?
Chapter 1The Big Picture
A Snapshot of Devops Culture
The Evolution of Culture
The Value of the Story
Illustrating Devops with Stories
Chapter 2What Is Devops?
A Prescription for Culture
The Devops Equation
Chapter 3A History of Devops
Developer as Operator
The Advent of Software Engineering
The Advent of Proprietary Software and Standardization
The Age of the Network
The Beginnings of a Global Community
The Age of Applications and the Web
The Growth of Software Development Methodologies
Open Source Software, Proprietary Services
The Beginning of devopsdays
The Current State of Devops
Chapter 4Foundational Terminology and Concepts
Software Development Methodologies
Development, Release, and Deployment Concepts
Chapter 5Devops Misconceptions and Anti-Patterns
Common Devops Misconceptions
Chapter 6The Four Pillars of Effective Devops
Chapter 7Collaboration: Individuals Working Together
Sparkle Corp Weekly Planning Meeting
Individual Differences and Backgrounds
Opportunities for Competitive Advantage
Mindsets and Learning Organizations
The Role of Feedback
Reviews and Rankings
Communication and Conflict Resolution Styles
Empathy and Trust
Humane Staffing and Resources
Effective Collaboration with Sparkle Corp
Chapter 8Collaboration: Misconceptions and Troubleshooting
Chapter 9Affinity: From Individuals to Teams
Sparkle Corp Development Demo Day
What Makes a Team?
Teams and Organizational Structure
Finding Common Ground Between Teams
Case Study: United States Patent and Trademark Office
Benefits of Improved Affinity
Requirements for Affinity
Sparkle Corp Dev and Ops Affinity
Chapter 10Affinity: Misconceptions and Troubleshooting
Chapter 11Tools: Ecosystem Overview
Evolution of the Ecosystem
Chapter 12Tools: Accelerators of Culture
The Value of Tools to People
What Are Tools?
The Right Tools for Real Problems
Embracing Open Source
Standardization of Tools
Consistent Processes for Tool Analysis
Exceptions to Standardization
Irrelevance of Tools
The Impacts of Tools on Culture
Selection of Tools
Auditing Your Tool Ecosystem
Elimination of Tools
Motivations and Decision-Making Challenges
Sparkle Corp Effective Tool Usage
Chapter 13Tools: Misconceptions and Troubleshooting
Chapter 14Scaling: Inflection Points
Considering Enterprise Devops
Complexity and Change
Scaling for Teams
Case Studies: Growing and Scaling Teams
Team Scaling and Growth Strategies
Scaling for Organizations
Case Study: Government Digital Service, GOV.UK
Case Study: Target
Chapter 15Scaling: Misconceptions and Troubleshooting
We Don’t Know If We Need a Full Team for X
Bridging Devops Cultures
Chapter 16Building Bridges with the Four Pillars of Effective Devops
The Significance of Stories
Devops in Theory and in Practice
Chapter 17Bridging Devops Cultures: Learning from Our Stories
What Stories Can Teach Us About Culture
Encouraging Interorganizational Affinity
Chapter 18Bridging Devops Cultures: Fostering Human Connections
Jennifer Davis is a global organizer for devopsdays and a local organizer for devopsdays Silicon Valley, and the founder of Coffeeops. She supports a number of community meetups in the San Francisco area. In her role at Chef, Jennifer develops Chef cookbooks to simplify building and managing infrastructure. She has spoken at a number of industry conferences about devops, tech culture, monitoring, and automation. When she’s not working, she enjoys hiking Bay Area trails, learning to make things, and spending quality time with her partner, Brian, and her dog, George.
Katherine Daniels is a senior operations engineer working at Etsy. She has taken her love of automation and operations and turned it into a specialization in monitoring, configuration management, and operational tooling development, and has spoken at numerous industry conferences including Velocity, devopsdays, and Monitorama about subjects such as infrastructure automation, scaling monitoring solutions, and cultural change in engineering. Katherine is one of the co-organizers of devopsdays NYC and helps run Ladies Who Linux in New York. She lives in Brooklyn with a perfectly reasonable number of cats, and in her spare time enjoys playing cello, rock climbing, and brewing beer.
The animal on the cover of Effective DevOps is a wild yak (Bos mutus). This formidable yet friendly bovid occupies remote, mountainous areas of the northwestern Tibetan Plateau, the highest dwelling of any mammal.
The wild yak's distinguishing characteristics include high, humped shoulders and shaggy, dark fur that hangs nearly to the ground. It is one of the largest members of the Bovidae family, which also includes the American bison, the African buffalo, and domestic cattle. Males can reach between five and seven feet high at the shoulder and weigh up to 2,200 pounds; females are typically a third of that size.
Bos mutus is extremely well adapted to its high-altitude habitat, with a large lung capacity, high red blood cell count, and warm, woolly coat. In spite of their bulk, wild yaks are also very adept climbers, using their split hooves and strong legs to navigate rocky, icy terrain. Their dense horns, which curve out from the sides of their broad heads, allow them to dig through snow for food. Conversely, they are very sensitive to warm temperatures and move seasonally to avoid the heat.
Wild yaks are gregarious and peaceful herbivores, feeding on grass, herbs, and lichens. Female yaks gather with their young in herds of as many as 100; males tend to be more solitary, traveling in groups of around 10. Together they travel long distances to obtain vegetation.
Though the yak population is thought to number over 12 million worldwide, that figure mostly comprises the smaller domesticated yak (Bos grunniens). The wild species is considered vulnerable, reportedly declining more than 30 percent in the last 3 decades. Its most serious threat is poaching, although interbreeding with domestic yaks is another factor. The wild yak's average lifespan is about 23 years in the wild.
Many of the animals on O'Reilly covers are endangered; all of them are important to the world. To learn more about how you can help, go to animals.oreilly.com.
The cover image is from Lydekker's Royal Natural History. The cover fonts are URW Typewriter and Guardian Sans. The text font is Adobe Minion Pro; the heading font is Adobe Myriad Condensed; and the code font is Dalton Maag's Ubuntu Mono.
This book, is really not about devOps in a whole but really more about collaboration (devOps or not). A good idea it's to change the book title. It's Really tuff to read because the exemple are not representatif and some facts are base on occur studies.
Bottom Line No, I would not recommend this to a friend
I've read the book from the context of an agilist concerned with building an ops team. I've also ready negative review of this book provided here. What I come away with is a recognition that this book tackles the hard bits. Culture is difficult to describe and even more so to monetize. However, what I enjoyed about this book were some practical examples of applying the intangible aspects of DevOps - including Culture - to organizations who want to see meaningful change.
I get that this book isn't an exact blueprint. My thought is that DevOps lies in the complex domain of the Cynefin model. It's complex, it's emergent; it's hard and interesting. If you're looking for a by-the-numbers solution, then this will not help. If you're looking for building blocks and day-to-day insights that emerge out of the murk: then you've found the right book.
Bottom Line Yes, I would recommend this to a friend
Despite having been around for quite some year, there is still no agreement on what is DevOps. Etymologically, the word is the result of the merging of Developer and Operations. In this sense, the term suggests a person that has the knowledge to cover both positions, thus reducing the problems that use(d) to arise in between the development of an application and its deployment in production. This view is often coupled with the concept of automation, mainly in the cloud scenario. Still, some believe that this definition is very remissive and plain wrong, claiming DevOps is a movement, a way to think. Essential DevOps, a recently released book, enters this diatribe and tries to bring some light in this endless debate giving us all THE answer. The authors see DevOps as a culture and want to discuss the technical, cultural, and managerial challenges of implementing and maintaining a DevOps culture in a company.
Before getting into the details, a quick note: this book is not about technical stuff. There is not a single page dedicated to a tool, not even those meant to help team collaboration.
The first chapter of this very thin book tries to get the reader an idea of what DevOps truly is. The many different ways the community describes DevOps are given and then demystified. This is referred to as the DevOps misconceptions. Finally, we are revealed the truth: DevOps is a culture, the culture of teams working together, communicating their intentions and the issues that they run into, dynamically adjusting in order to work towards shared goals.
Next, now that the sinful reader has been enlighten, we find all the remaining chapters dedicated to the many different aspects of this team working smoothly in synergy. Through the pages the authors argument about team affinity and collaboration, from the hiring process up to collaboration. The many different types of people that populate planet Earth are described. There is not much more to say, really.
I have honestly not understood at all what this book has to do with DevOps: the first two chapters quickly tell what DevOps is not. The rest of the book seems a quick guide dedicated to HR Professionals with advices on how to hire people to build up a team with the perfect chemistry, taking into account skills, character and ambitions. While the information is interesting and possibly correct (I'm no HR), I see no relationship with DevOps, since all of this is true for every kind of profession and, in the case of IT, methodology.
The book feels like a sermon that paints DevOps as something similar to a religion of love and synergy. In this sense, the book strongly reminds me of Continuous Delivery and DevOps: A Quickstart Guide which has nothing to do with neither Continuous Integration nor DevOps.
As a final note, while I do recognize that everyone has the right to describe what DevOps is, I guess that Google is not willing to hire a gardener to cover a DevOps position, even if this person is a great team player with a very positive attitude towards work and people. Somehow I guess they are interested in people with knowledge and interest of automation, cloud and containers.
As usual, you can find more reviews on my personal blog: books.lostinmalloc.com. Feel free to pass by and share your thoughts!
Bottom Line No, I would not recommend this to a friend