Feature Development Cycles | Discovery to Release
Structure feature development from discovery through release with repeatable processes, phase gates, and milestone tracking in GitScrum.
7 min read
Feature development involves multiple phases from ideation through release, each requiring different activities and stakeholders. GitScrum's workflow templates, milestone tracking, and checklist features help teams create repeatable feature development processes that consistently deliver quality features on time.
Feature Development Phases
| Phase | Goal | Deliverables |
|---|---|---|
| Discovery | Validate problem | User research, data analysis |
| Design | Define solution | Specs, designs, technical plan |
| Development | Build solution | Working code, tests |
| Testing | Verify quality | Test results, bug fixes |
| Release | Deploy safely | Production deployment |
| Measure | Validate outcomes | Metrics, learnings |
Feature Development Framework
FEATURE LIFECYCLE
1. DISCOVERY
┌─────────────────────────────────────────────────┐
│ Goal: Validate problem worth solving │
│ │
│ Activities: │
│ ├── User interviews/surveys │
│ ├── Data analysis │
│ ├── Competitive research │
│ └── Problem statement definition │
│ │
│ Exit criteria: │
│ ☐ Problem clearly defined │
│ ☐ User need validated │
│ ☐ Business case established │
│ ☐ Go/no-go decision made │
│ │
│ Duration: 1-2 weeks │
└─────────────────────────────────────────────────┘
│
▼
2. DESIGN
┌─────────────────────────────────────────────────┐
│ Goal: Define solution approach │
│ │
│ Activities: │
│ ├── Solution ideation │
│ ├── UX/UI design │
│ ├── Technical design │
│ ├── Estimation │
│ └── Design review │
│ │
│ Exit criteria: │
│ ☐ Requirements documented │
│ ☐ Designs approved │
│ ☐ Technical approach validated │
│ ☐ Effort estimated │
│ │
│ Duration: 1-2 weeks │
└─────────────────────────────────────────────────┘
│
▼
3. DEVELOPMENT
┌─────────────────────────────────────────────────┐
│ Goal: Build the solution │
│ │
│ Activities: │
│ ├── Implementation in sprints │
│ ├── Code reviews │
│ ├── Unit/integration testing │
│ ├── Documentation │
│ └── Continuous integration │
│ │
│ Exit criteria: │
│ ☐ All tasks completed │
│ ☐ Code reviewed and merged │
│ ☐ Tests passing │
│ ☐ Documentation updated │
│ │
│ Duration: 2-6 weeks (varies) │
└─────────────────────────────────────────────────┘
│
▼
4. TESTING
┌─────────────────────────────────────────────────┐
│ Goal: Verify quality and fix issues │
│ │
│ Activities: │
│ ├── QA testing │
│ ├── Bug fixing │
│ ├── Performance testing │
│ ├── Security review │
│ └── User acceptance testing │
│ │
│ Exit criteria: │
│ ☐ All critical bugs fixed │
│ ☐ QA sign-off obtained │
│ ☐ Performance acceptable │
│ ☐ Security review passed │
│ │
│ Duration: 1-2 weeks │
└─────────────────────────────────────────────────┘
│
▼
5. RELEASE
┌─────────────────────────────────────────────────┐
│ Goal: Deploy to production safely │
│ │
│ Activities: │
│ ├── Deployment preparation │
│ ├── Feature flag configuration │
│ ├── Staged rollout │
│ ├── Monitoring setup │
│ └── Announcement │
│ │
│ Exit criteria: │
│ ☐ Deployed to production │
│ ☐ Monitoring in place │
│ ☐ Rollback plan ready │
│ ☐ Stakeholders notified │
│ │
│ Duration: 1-2 days │
└─────────────────────────────────────────────────┘
│
▼
6. MEASURE
┌─────────────────────────────────────────────────┐
│ Goal: Validate outcomes │
│ │
│ Activities: │
│ ├── Monitor usage metrics │
│ ├── Collect user feedback │
│ ├── Compare to success criteria │
│ ├── Document learnings │
│ └── Plan iterations │
│ │
│ Exit criteria: │
│ ☐ Metrics reviewed (2-4 weeks post-launch) │
│ ☐ Success evaluated │
│ ☐ Next steps defined │
│ ☐ Retrospective completed │
│ │
│ Duration: Ongoing │
└─────────────────────────────────────────────────┘
Feature Epic Template
FEATURE EPIC STRUCTURE
┌─────────────────────────────────────────────────┐
│ Epic: User Search Feature │
│ Owner: @product-manager │
│ Target: Q2 2024 │
│ Status: In Development │
│ │
│ Phase: Development (3/6) │
│ ████████████░░░░░░░░░ 60% │
│ │
│ Discovery Tasks: ✓ Complete │
│ ├── ✓ User interview analysis │
│ ├── ✓ Competitor feature review │
│ └── ✓ Problem statement document │
│ │
│ Design Tasks: ✓ Complete │
│ ├── ✓ UX wireframes │
│ ├── ✓ UI designs │
│ ├── ✓ Technical design doc │
│ └── ✓ Design review │
│ │
│ Development Tasks: In Progress │
│ ├── ✓ Search API endpoint │
│ ├── ✓ Search indexing │
│ ├── ○ Search UI component │
│ ├── ○ Filters implementation │
│ └── ○ Search analytics │
│ │
│ Testing Tasks: Not Started │
│ ├── ○ QA test plan │
│ ├── ○ Performance testing │
│ └── ○ UAT │
│ │
│ Release Tasks: Not Started │
│ ├── ○ Feature flag setup │
│ ├── ○ Staged rollout plan │
│ └── ○ Documentation │
│ │
│ Success Criteria: │
│ • Search usage: 50% of active users │
│ • Search success rate: >80% │
│ • Search latency: <200ms P95 │
└─────────────────────────────────────────────────┘
Phase Transition Reviews
PHASE GATE REVIEWS
DISCOVERY → DESIGN GATE:
┌─────────────────────────────────────────────────┐
│ Review checklist: │
│ ☐ Problem statement is clear and validated │
│ ☐ User need is supported by evidence │
│ ☐ Business case is compelling │
│ ☐ Rough scope is understood │
│ ☐ Stakeholders aligned on priority │
│ │
│ Decision: Proceed / Pivot / Stop │
└─────────────────────────────────────────────────┘
DESIGN → DEVELOPMENT GATE:
┌─────────────────────────────────────────────────┐
│ Review checklist: │
│ ☐ Requirements are documented and approved │
│ ☐ Designs are complete and reviewed │
│ ☐ Technical approach is validated │
│ ☐ Effort is estimated and resourced │
│ ☐ Dependencies are identified │
│ ☐ Success metrics are defined │
│ │
│ Decision: Proceed / Needs more design │
└─────────────────────────────────────────────────┘
TESTING → RELEASE GATE:
┌─────────────────────────────────────────────────┐
│ Review checklist: │
│ ☐ All P1/P2 bugs are fixed │
│ ☐ QA has signed off │
│ ☐ Performance meets requirements │
│ ☐ Security review passed │
│ ☐ Documentation is complete │
│ ☐ Rollback plan is documented │
│ │
│ Decision: Release / Fix issues first │
└─────────────────────────────────────────────────┘
Best Practices
Anti-Patterns
✗ Jumping straight to development
✗ Skipping discovery for "obvious" features
✗ No measurement after release
✗ Phases without clear exit criteria
✗ Testing as afterthought
✗ No phase visibility in tracking