Set Up Trunk-Based Development on a 3-Branch Workflow
Overview
What this challenge is about.
Audit the current branch + merge data over 8 weeks (frequency, conflict count, time-to-green). Pick one product team for a 4-week pilot: introduce a feature-flag system (Unleash or LaunchDarkly OSS), drop the release branch, enforce a 24-hour max-age policy on feature branches, and add a green-trunk CI gate. Measure conflict count, merge time, and deploy frequency before and after. Deliver a 6-page migration plan covering tooling + policy, a runbook for managing trunk-based incidents, the 4-week pilot measurement report, and a recommendation memo to the VP of engineering on whether to scale to the other 5 teams.
The Brief
What you'll do, and what you'll demonstrate.
Migrate one team from a 3-branch workflow to trunk-based development with feature flags and produce evidence on whether to scale.
Earning criteria — what you'll demonstrate
- Migrate a real team from long-lived branches to trunk-based development
- Design a feature-flag taxonomy that does not become permanent dead code
- Enforce a green-trunk policy without becoming the merge police
- Measure version-control workflow changes with concrete metrics
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.