Set Up Trunk-Based Development on a 3-Branch Workflow
Overview
What this challenge is about.
Audit branch data, run a 4-week trunk-based pilot with feature flags, and deliver a migration plan. Earn a verifiable certificate.
The scenario
The marketplace (around 45 engineers across 6 teams, ships twice per sprint) has been losing two engineer-days per sprint to merge conflicts on a release branch that mostly exists for historical reasons.
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.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Version Control
Apply version control to solve real industry problems and demonstrate production-level capability.
- Trunk Based Development
Apply trunk based development to solve real industry problems and demonstrate production-level capability.
- Feature Flags
Apply feature flags to solve real industry problems and demonstrate production-level capability.
- Ci Cd
Apply ci cd to solve real industry problems and demonstrate production-level capability.
- Process Design
Apply process design to solve real industry problems and demonstrate production-level capability.
- Code Review
Apply code review to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles: