Defining Retention Metrics for Your Application Configuration Developer Tool

You are building an application configuration developer tool.

The Metric:

Weekly Active Developers Deploying Configuration Changes (WADDCC)

Why it Matters:

The number of developers who deploy at least one configuration change per week.

Regular configuration updates ensure their applications stay adaptable, secure, and optimized across all environments.

Quick Start Guide:

Track It

• Log all configuration deployments with developer IDs
• Set up a weekly script to count unique developers deploying changes

Measure

• Outstanding: >80% of developers deploying weekly
• On Track: 60-80% weekly deployment rate
• Needs Attention: <60% weekly deployment rate

Don'ts:

• Don't count config file edits without deployment
• Avoid focusing on total deployments instead of unique developers
• Beware of counting test environment deployments only

Your Customers Config Mission This Week:

1. Set up WADDCC tracking (Tip: Use your CI/CD pipeline logs!)
2. Aim to boost WADDCC by 10% in the next sprint
3. Plan a team retro on config management practices next week

WADDCC

Why WADDCC should be your application configuration customers' new favorite acronym:

1. Agility Indicator: High WADDCC suggests your team is actively adapting to changing requirements
2. DevOps Health: It reflects how well your team has embraced configuration-as-code practices
3. Risk Reduction: Regular small changes are often safer than infrequent large ones

WADDCC Implementation Playbook:

1. Tool Up: Choose a config management tool that integrates with your CI/CD pipeline
2. Define 'Deployment': Clearly outline what counts as a config deployment (e.g., prod vs. staging)
3. Educate: Ensure all devs understand the importance of regular config management
4. Automate: Use bots to remind devs of pending config reviews or necessary updates

Boosting Your Customers WADDCC:

1. Create config update templates to speed up common changes
2. Implement peer review for config changes to spread knowledge and responsibility
3. Set up automated tests for config changes to build deployment confidence
4. Use feature flags for gradual config rollouts, encouraging more frequent updates

Keep Building!