Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Rate it:
Kindle Notes & Highlights
19%
Flag icon
Oriented) Bureaucratic (Rule-Oriented) Generative (Performance-Oriented) Low cooperation Modest cooperation High cooperation Messengers “shot” Messengers neglected Messengers trained Responsibilities shirked Narrow responsibilities Risks are shared Bridging discouraged Bridging tolerated Bridging encouraged Failure leads to scapegoating Failure leads to justice Failure leads to inquiry Novelty crushed Novelty leads to problems Novelty implemented
20%
Flag icon
asking them to rate how strongly they agree or disagree with a statement. When people answer
20%
Flag icon
culture is valid and reliable from a statistical point of view.
20%
Flag icon
indicator of the level of organizational culture that prioritizes trust and collaboration in the team—
20%
Flag icon
organizations with a generative culture,
20%
Flag icon
people collaborate more effectively
20%
Flag icon
higher level ...
This highlight has been truncated due to consecutive passage length restrictions.
20%
Flag icon
put aside their personal issues
20%
Flag icon
The mission is primary. And third,
20%
Flag icon
‘level playing field,’ in which hierarchy plays less o...
This highlight has been truncated due to consecutive passage length restrictions.
21%
Flag icon
“ensure fairness by applying rules to administrative behavior.
21%
Flag icon
where following the rules is considered more important than achieving the mission—
21%
Flag icon
WHAT DOES WESTRUM ORGANIZATIONAL CULTURE PREDICT?
21%
Flag icon
good culture requires trust and cooperation between people across the organization,
21%
Flag icon
better organizational culture can indicate higher quality decision-making. In
21%
Flag icon
decisions are more easily reversed
21%
Flag icon
cultural norms are likely to do a better job with their people,
21%
Flag icon
metrics: lead time, release frequency, time to restore service, and change fail rate.
21%
Flag icon
software delivery performance it is defined using only the combination of those three metrics.
22%
Flag icon
common factors among its best-performing
22%
Flag icon
“who is on a team matters less than how the team members interact, structure their work, and view their contributions
22%
Flag icon
team dynamics.
22%
Flag icon
to choke”: Investigations aim to find the person
22%
Flag icon
start of the investigation.
22%
Flag icon
improve information flow so that people have better or more timely information,
22%
Flag icon
change culture is not to first change how people think, but instead to start by changing how people behave—what they do”
23%
Flag icon
Extreme Programming (XP) was one of the most popular Agile frameworks.
23%
Flag icon
test-driven development and continuous integration.
23%
Flag icon
treated technical practices as secondary compared to the management and team practices that
23%
Flag icon
technical practices
23%
Flag icon
team burnout and deployment pain.
23%
Flag icon
Continuous delivery is a set of capabilities that enable
23%
Flag icon
safely, quickly, and sustainably.
23%
Flag icon
“Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place”
23%
Flag icon
where we can detect any issues quickly,
23%
Flag icon
Work in small batches.
23%
Flag icon
plan work in big chunks—
23%
Flag icon
Computers perform repetitive tasks; people solve problems.
23%
Flag icon
invest in simplifying and automating this work.
23%
Flag icon
improving the design of our systems and processes in response to feedback.
23%
Flag icon
Relentlessly pursue continuous imp...
This highlight has been truncated due to consecutive passage length restrictions.
23%
Flag icon
development focuses on throughput, testing on quality, and operations on stability.
23%
Flag icon
the state of these system-level outcomes transparent,
23%
Flag icon
measurable, achievable, time-bound goals for these outcomes,
23%
Flag icon
Comprehensive configuration management. It
23%
Flag icon
This still leaves room for manual approvals—but once approved, all changes should be applied automatically.
24%
Flag icon
keep branches short-lived
24%
Flag icon
should be run against every commit to version control to give developers fast feedback on their changes.
24%
Flag icon
high-quality software gets delivered to users more frequently and more reliably.
24%
Flag icon
THE IMPACT OF CONTINUOUS DELIVERY
1 6 11