Remove 2004 Remove Continuous Integration Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Continuous Integration

James Shore

Continuous Integration. Most software development efforts have a hidden delay between when the team says “we’re done” and when the software is actually ready to release. Continuous integration is a better approach. Teams using continuous integration keep everyone’s code working together and ready to release.

article thumbnail

AoAD2 Practice: Feature Toggles

James Shore

Continuous Integration. Continuous Deployment. That doesn’t work for teams using continuous integration and deployment. Other than short-lived development branches, they only have one branch: their integration branch. Kent Beck calls it a “Keystone” [Beck 2004] (p. Test-Driven Development.

article thumbnail

AoAD2 Practice: Feature Flags

James Shore

Continuous Integration. Continuous Deployment. That doesn’t work for teams using continuous integration and deployment. Other than short-lived development branches, they only have one branch: their integration branch. Beck 2004] (p. Test-Driven Development.