更新时间：2021-06-10 19:49:01
coverpage
Title Page
Packt Upsell
Why subscribe?
Packt.com
Contributors
About the author
About the reviewers
Packt is searching for authors like you
Preface
Who this book is for
What this book covers
To get the most out of this book
Download the color images
Conventions used
Get in touch
Reviews
The Evolution of Software Delivery
ACME systems – evolution phase 1.0
Software-delivery process flow Version 1.0
ACME systems evolution phase 2.0
Software-delivery process flow Version 2.0
An outsider's perspective from the inside
ACME systems evolution phase 3.0
Software-delivery process flow version 3.0
ACME systems beyond Version 3.0
The evolution in a nutshell
Where am I on the evolutionary scale?
Summary
Understanding Your Current Pain Points
Elephant in the room
Defining the rules
Including (almost) everyone
Identifying key people
Too many cooks
Openness transparency and honesty
Secrets hiding the truth
Location location location
It's all happy-clappy management waffle – isn't it?
The great elephant disclosure
Tools and techniques to expose the obvious
Timeline
Value stream mapping
Culture and Behaviors are the Cornerstones to Success
All roads lead to culture
Defining culture
Processes
Communications
Tools and techniques
An open honest and safe environment
Openness and honesty
Courageous dialogue
The physical environment
Encouraging and embracing collaboration
Fostering innovation and accountability at a grass-roots level
The blame game
Blame slowly learn quickly
Building trust-based relationships across organizational boundaries
Rewarding good behaviors and success
The odd few
Recognizing how Dev and Ops teams are incentivized can have an impact
Embracing change and reducing risk
Changing people's perceptions with pudding
Being transparent
Planning for Success
Some common problems
Setting and communicating goals and vision
Standardizing vocabulary and language
A business change project in its own right
Dev + Ops + Org
The pros and cons of a dedicated team
The importance of evangelism
The courage and determination required throughout the organization
Understanding the cost
Seeking advice from others
Approaches Tools and Techniques
Engineering best practices
Source-control
The binary repository
Small frequent and simple changes
Automated builds
Test-automation
Continuous integration
Fail fast and often
Architectural approaches
Component-based architecture
Layers of abstraction
Never break your consumer
Open and honest peer-working practices
Incremental delivery of features
Using the same binary across all environments
How many environments is enough?
Developing against a like-live environment
CD and DevOps tooling
Automated provisioning
No-downtime deployments
Monitor monitor monitor
