Software Delivery Performance - dennisholee/notes GitHub Wiki

Change lead time
Deployment frequency
Mean time to restore (MTTR)
Change fail percentage https://www.thoughtworks.com/radar/techniques/four-key-metrics

New work Unplanned work Rework

Westrum Organization Culture

Pathological	Bureaucratic	Generative
Power oriented	Rule oriented	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

Make large-scale changes to the design of their systems without the permission of somebody outside the team or depending on other teams.
Make large-scale changes to the design of their system without depending on other teams to make changes in their systems or creting significant work for other teams.
Teams are able to complete work without needing fine-grained communication and coordination with people outside the team.
Teams deploy and release their product or service on demand, independently of the services it depends on or of other services that depend on it.
Teams do most of their testing on demand, without requiring an integrated test environment.
Teams can deploy during normal business hours with negligible downtime.

One main development branch develop branch strict access create feature branches from main branch

main branch reach maturity for release

Suitable

Not Suitable

Suitable:

Not Suitable