Scribd
Upload
98 views

Maturity Checklist: Continuous Delivery

This document provides a maturity checklist for assessing an organization's continuous delivery capabilities. It covers key areas like source control, build processes, testing and quality assurance, deployment, and visibility. For each area, it lists practices at different maturity levels from baseline to expert. Organizations can check which practices they perform and tally their scores to evaluate their overall continuous delivery maturity.

Uploaded by

spam.recycler1048
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
98 views

Maturity Checklist: Continuous Delivery

This document provides a maturity checklist for assessing an organization's continuous delivery capabilities. It covers key areas like source control, build processes, testing and quality assurance, deployment, and visibility. For each area, it lists practices at different maturity levels from baseline to expert. Organizations can check which practices they perform and tally their scores to evaluate their overall continuous delivery maturity.

Uploaded by

spam.recycler1048
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

excerpt from DZone’s 2014 GUIDE TO Continuous Delivery

Continuous Delivery MATURITY CHECKLIST


Check the boxes next to the practices you currently perform to see your maturity in each area of Continuous Delivery.
Add up your score at the end based on the highest levels you checked.

Source Control Deployment


Baseline Baseline
FF Early branching FF Fully scripted deployments
FF Branches tend to remain apart
N ov i c e
N ov i c e FF Push-button deployments to test environments
FF Branches are used for isolating work
I n t e r m e d i at e
FF Merges are common
FF Auto deploy to first test environment
I n t e r m e d i at e FF Standard deployments across all environments
FF Pre-tested commits FF Push-button deployments to production
FF Integration branch is pristine
Adva n c e d
Adva n c e d FF Automated deployments after tests pass
FF All commits are tied to tasks FF Database deployments
FF History used to rewrite features before pushing to central FF Multi-tier deployments
repository
FF Version control DB schema changes expert
FF Ability to implement continuous deployment
Expert
FF Traceability analysis and release notes auto-generated Visibility
FF Commits are clean enough for the master branch/trunk
Baseline
FF Build status notification is sent to committer
Build Process
N ov i c e
Baseline
FF Latest build status is available to all team members
FF Official builds are not performed on developers’ machines
FF Self-service build or nightly build I n t e r m e d i at e
FF Trend reports are automatically generated from build server
N ov i c e events
FF System polls source control and builds on commit FF People outside the team can subscribe to build statuses
FF Build artifacts are managed, some manual scripts still used
Adva n c e d
I n t e r m e d i at e FF Stakeholders have dashboards with real-time product and
dependency stats
FF Build artifacts are managed by purpose-built tools, no
manual scripts
Expert
FF Dependencies are managed in a repository FF Cross-team data mining and analysis
Adva n c e d
FF Distributed builds on build cluster, can be done in sequence
FF Source control tells system when to build, no polling
Overall Maturity scorecard
Expert
For each check mark add the assigned number of points and
FF Build environments based on VMs
total them for each section:
FF Streams are never “broken”
FF Gated commits TALLY YOUR SCORES:

Testing & QA POINT KEY: Source Control


Baseline • Baseline 0 points
FF Automatic unit testing with every build • Novice 1 point Build Process
FF Code coverage is measured • Intermediate 2 points
N ov i c e Testing & QA
• Advanced 3 points
FF Peer-reviews
• Expert 4 points DEPLOYMENT
FF Mockups & proxies used

I n t e r m e d i at e Visibility
FF Periodic static code analysis
FF Automated functional testing
TOTAL
Adva n c e d
FF Integrated management and maintenance of the test data 0-7 Adequate 8-11 Average 12-14 Skilled
FF Automated performance & security tests in target environments 15-17 Adept 18-20 Master
Expert
FF Automated acceptance testing
Inspired by Chris Shayan and Eric Minick

excerpt from DZone’s 2014 Guide to Continuous Delivery DOWNLOAD NOW

You might also like