打造协作文化：Effective DevOps 实践指南

需积分: 10 117 浏览量更新于2024-07-20 4 收藏 6.43MB PDF 举报

"Effective DevOps (O'Reilly, 2016) 是一本由 Katherine Daniels 和 Jennifer Davis 合著的实践指南，旨在帮助组织内部理解并实施 DevOps 文化和理念，而非仅仅引入专家或新工具。这本书强调在团队间进行迭代改进，打破信息孤岛，监控和修复团队间的关系与误解，以及通过选择合适的工具和工作流程来加速文化变革。书中还包含实际案例研究，提供了解决常见问题和误解的策略，以促进个人和团队之间的合作与持久关系的建立。" 在这本书中，作者探讨了DevOps的基础，并介绍了实现有效DevOps的四个支柱： 1. **协作**：DevOps的核心是鼓励团队间的合作，以增进个人之间的协同工作能力，建立稳固且持久的工作关系。书中强调了如何在组织内推动合作文化，促进跨部门沟通，共同解决问题。 2. **亲和力**：创建团队间的亲和力意味着要平衡不同团队的目标和指标，尽管这些可能有所冲突。书中提供了方法来确保各个团队能够围绕共同目标协作，同时保持各自的特点和效率。 3. **规模化工具使用**：选择适合组织文化的工具和工作流程是加速文化变革的关键。有效的DevOps不仅关注技术工具，还关注如何使工具适应组织需求，以提高整个组织的效率。 4. **解决组织生命周期中的问题**：作者提供了应对组织生命周期中可能出现的常见问题和误解的策略。这包括识别和修复沟通障碍，确保在组织的不同阶段都能持续改进。书中的案例研究涵盖了来自不同组织和个人的经验，为读者提供了一个理解和应用DevOps的实用视角，帮助他们在自己的DevOps旅程中找到方向。这些案例揭示了成功实践DevOps的实例，同时也揭示了一些常见的误区，如认为DevOps只适用于初创公司、成本高昂，或者是一个需要填补的职位，这些误解阻碍了DevOps精神的传播。 "Effective DevOps" 不仅仅是一本关于技术的书籍，更是一本引导组织进行文化和流程改革的指南，它提供了实用的策略和深入的见解，帮助任何级别的员工在他们的组织中实现可持续的改变。无论你是技术团队的一员还是业务线上的领导者，这本书都能提供宝贵的洞见，推动你朝着更高效、更具协作性的DevOps文化迈进。

17. Bridging Devops Cultures: Learning from Our Stories. . . . . . . . . . . . . . . . . . . . . . . . . . 315

What Stories Can Teach Us About Culture 315

Values 316

Prohibitions 320

Myths 321

Rituals 323

Ideas and Knowledge 325

Interorganizational Interactions 327

Conferences and Travel 327

Other Community Events 329

Engineering Exchanges 330

Encouraging Interorganizational Affinity 331

Discouraging Fixed Mindsets 331

Start with Small Changes 332

Summary 333

18.

Bridging Devops Cultures: Fostering Human Connections. . . . . . . . . . . . . . . . . . . . . . 335

Individual Stories and Narratives around Work 335

Taylorism and the Value of Individual Stories 336

Celebrating Individuals 337

Going Remote 339

Leaving a Company 341

Cultural Debt 343

The Health of Systems 344

Examining Sick Systems 344

Creating Healthy Systems 346

Organizational and Individual Health 348

Identifying Healthy and Unhealthy Cultures 350

Summary 351

19.

Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Your Next Steps 354

Creating Effective Devops 355

20.

Further Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

xiv | Table of Contents

Foreword by John Allspaw

There is a sea change happening in software development and operations, and it is

not simply the introduction of a new word into our lexicon—it’s much more than

that. It is a fundamental shift of perspective in the design, construction, and operation

of software in a world where almost every successful organization recognizes that

software is not something you simply build and launch—it is something you operate.

What makes this shift unique is that it’s more encompassing, more holistic, and more

reflective of the reality that engineering teams face on a daily basis. Long gone are the

days that manufacturing and assembly-line metaphors could be used in software

development and operations. Long gone are the days that products are things that are

designed, planned, and then finally launched. There is no “finally” anymore. There is

only an endless cycle of adaptation, change, and learning.

What Katherine and Jennifer have laid out in this volume is a myriad of threads to

pull on as engineers in teams and organizations cope with the complexity that comes

with trying to make their work “simple.”

Katherine and Jennifer do not paint a picture of one-size-fits-all or deterministic sol‐

utionism. Instead, they describe a landscape of topic areas, practices, and observa‐

tions of teams and organizations that understand the idea that at the heart of good

products, good user experiences, and good software is the elegantly messy world of

human cooperation, thoughtful critique, effective collaboration, and judgment.

In 2009, my friend Paul Hammond and I gave a presentation at O’Reilly’s Velocity

Conference entitled “10+ Deploys a Day: Dev and Ops Cooperation at Flickr.” While

some of the material was about perspectives on continuous deployment, many chose

to focus on the “10+ Deploys” part rather than the “Cooperation” part. I believe it is a

mistake to think that the technology or “hard parts” can be seen as somehow distinct

or separate from the social and cultural “soft parts”—they cannot. They are inextrica‐

bly linked and equally critical to success. In other words, people and process influ‐

ence tools and software in more ways than most are willing to admit or even know.

Foreword by Nicole Forsgren

In 2003, Nicholas Carr declared to the world that IT didn’t matter—and because he

said it in Harvard Business Review, organizations (and the executives that run them)

believed him. Well, times have changed, and so has IT. Since 2009, the most innova‐

tive teams and organizations have shown that technology can play a key role in deliv‐

ering real value and competitive advantage. This technology revolution is known as

DevOps, and this book can show you how to join those innovative companies to

deliver value with technology as well.

Here, Jennifer and Katherine draw on their experiences at innovative companies as

well as their backgrounds as prominent experts in the community to highlight what it

really takes to do DevOps—or as they call it, devops—effectively. This vantage point

brings unique insights that can be applicable and useful to any reader, because they

combine knowledge from several companies and across industries. This gives readers

something to take away regardless of where you are in your journey, no matter how

big (or small) your organization is.

The tales and advice found in

Eective DevOps parallel those I’ve seen in my own

work for the past decade. As a leading researcher in the field and the lead investigator

on the State of DevOps Reports, I know that a strong organizational culture that pri‐

oritizes information flow and trust is a key component of any DevOps transforma‐

tion, and the factor that sets the DevOps movement apart from traditional IT. Data

I’ve collected from over 20,000 DevOps professionals also shows that this culture

drives IT and organizational performance, helping the best IT organizations see

double productivity, profitability, and market share when compared to their peers. It’s

no mistake that Jennifer and Katherine start the book with a discussion on aspects of

culture, communication, and trust, and devote a good portion of their time address‐

ing the importance of these factors to any transformative work. As technologists, we

love to start with the tools and maybe even the processes, but time and again, the data

shows that culture is essential for tooling and technology success in addition to the

aforementioned IT and organizational performance. Parts II–III on collaboration and

affinity, respectively, are must-reads here, whether you are just starting your DevOps

xvii

transformation and want to know what to implement and watch for, or you are taking

your existing DevOps practice to the next level and looking for ways to optimize and

troubleshoot.

As a consultant to some of the most innovative companies, I’ve found that the most

challenging part of implementing DevOps and planning a technology transformation

roadmap is helping teams and organizations understand that there isn’t just one right

answer—it always depends on what is right for your team and your organization. I

love that Katherine and Jennifer embrace the ambiguity so well in this book, knowing

that there is no way to “plug and play” a single solution, and lay out the tools and

pieces you need to construct your own DevOps solution and journey successfully. In

addition to Parts II–III, be sure to check out Part IV on tools, which are essential to

any DevOps transformation. I especially love how they’re framed as not only technol‐

ogy, but also key components of the culture in which they perform.

My favorite aspect of this book is how accessible it is to so many different audiences.

Part V on scalability is particularly relevant for individual contributors and team

leaders, and I’ll be using it as a reference both personally and for my clients. Chap‐

ter 4 on terminology and Chapter 11 on ecosystem overview come in handy both for

technologists (to make sure we’re all on the same page, as different tribes often use

different words) and for executives who could use a current reference. The whole

book is a welcome and much-needed introduction to the field for university students

who just don’t get this training in their studies, and I wish I’d had it when I was

a professor.

We live and work in exciting times, and the integration of technology into our core

businesses has made every firm a software firm. Technology now provides opportuni‐

ties to deliver features to customers in new ways and at speeds not possible before.

Organizations often find themselves struggling to keep up. Old IT and waterfall

methods just don’t allow organizations to deliver value fast enough—I’ve seen it in

the data, and I’ve seen it among the customers and companies I work with to create

solutions for their own DevOps journeys. Jennifer and Katherine have also seen the

challenges to technology transformation in the old way, and the exciting opportuni‐

ties that are possible with DevOps, and they’ve responded by writing this book to

guide us all through our own journeys. So read through, and choose your own adven‐

ture! Iterate, learn, grow, and choose your own adventure again!

—Nicole Forsgren, PhD

Director, Chef

Soware

Seattle, WA

xviii | Foreword by Nicole Forsgren

剩余409页未读，继续阅读

vanridin

粉丝: 108
资源: 1188

打造协作文化：Effective DevOps 实践指南

Effective DevOps

OReilly.Effective.DevOps.Building.a.Culture.of.Collaboration.Affinity.and

有什么devops书籍推荐吗

学习devops的网站地址

devops pdf

Azure devops 面试题

EXIN DevOps证书怎样

EXIN DevOps证书有用吗

devops落地与转型

如何学习使用devops

最新资源