Starting CD
Migrating your system to Continuous Delivery
3 minute read
These are the core skills we recommend everyone learn to execute CD.
Every step in CD requires clear, testable acceptance criteria as a prerequisite. BDD is not test automation. BDD is the discussion that informs acceptance test driven development.
Continuous integration is a requirement for CD. It requires very frequent integration of non-breaking code.
“Any organization that designs a system will produce a design whose structure is a copy of the organization’s communication structure.” - Melvin Conway
Loosely coupled teams create loosely coupled systems. The opposite is also true.
This is another key design tool both for organizational and system design. This is a critical skill for developing microservices.
Architecting a system of delivery is about designing efficient quality gates for the system’s context.
TDD highly correlates with application architecture that is easy to maintain and easy to upgrade.
The core principles that define DevOps:
The primary process analysis tool used to help identify and attack constraints to delivery.
Our goal is to remove waste daily. We must first learn to recognize it.
Migrating your system to Continuous Delivery
Breaking down work to enable small batch delivery, faster feedback, and predictable outcomes through story slicing and clear acceptance criteria
Practices for managing team workflow, making work visible, and optimizing flow from backlog to done
Test patterns, principles, and best practices for building fast, reliable test suites that enable Continuous Delivery
An overview of key metrics for measuring and improving Continuous Delivery performance
Glossaries, checklists, and reference materials for Continuous Delivery practices