5 min lecture • Guide 678 of 877
How to Use GitScrum for Growth Engineering Teams?
How to use GitScrum for growth engineering teams?
Manage growth engineering in GitScrum with experiment tracking, funnel optimization tasks, and metrics documentation in NoteVault. Track hypothesis results, coordinate with marketing, measure business impact. Growth teams with structured workflow improve conversion by 30% [Source: Growth Engineering Research 2024].
Growth engineering workflow:
- Analyze - Find opportunities
- Hypothesize - Form thesis
- Prioritize - By impact
- Build - Create experiment
- Test - Run experiment
- Measure - Analyze results
- Scale - Roll out wins
Growth labels
| Label | Purpose |
|---|---|
| type-growth | Growth work |
| funnel-acquisition | New users |
| funnel-activation | First value |
| funnel-retention | Keep users |
| funnel-revenue | Monetization |
| funnel-referral | Virality |
| experiment | A/B test |
Growth columns
| Column | Purpose |
|---|---|
| Backlog | Experiment ideas |
| Prioritized | Ready to build |
| Building | Development |
| Running | Active experiment |
| Analyzing | Review results |
| Shipped/Killed | Decision made |
NoteVault growth docs
| Document | Content |
|---|---|
| Funnel analysis | Current state |
| Experiment log | All experiments |
| Learning repository | What works |
| Metric definitions | How we measure |
| Roadmap | Planned experiments |
Growth experiment template
## Experiment: [name]
### Funnel Stage
- [ ] Acquisition
- [ ] Activation
- [ ] Retention
- [ ] Revenue
- [ ] Referral
### Hypothesis
If we [change], then [metric] will improve by [amount] because [reason].
### ICE Score
- Impact: [1-10]
- Confidence: [1-10]
- Ease: [1-10]
- Score: [average]
### Implementation
- Changes: [description]
- Audience: [who sees it]
- Duration: [how long]
### Results
- Control: [metric]
- Variant: [metric]
- Lift: [%]
- Significance: [%]
### Outcome
[ ] Ship variant
[ ] Keep control
[ ] Iterate
[ ] Inconclusive
### Revenue Impact
[Estimated annual impact]
AARRR funnel
| Stage | Metrics |
|---|---|
| Acquisition | Signups, CAC |
| Activation | First action |
| Retention | Return rate |
| Revenue | ARPU, LTV |
| Referral | Referral rate |
ICE prioritization
| Factor | Score |
|---|---|
| Impact | Expected lift |
| Confidence | Likely to work |
| Ease | Effort required |
| Score | Average of 3 |
Experiment velocity
| Metric | Target |
|---|---|
| Experiments/month | 8-12 |
| Win rate | 20-30% |
| Time to result | 2 weeks |
| Time to ship | 1 week |
Growth metrics
| Metric | Track |
|---|---|
| Conversion rate | Per funnel stage |
| LTV | Customer lifetime value |
| CAC | Cost per acquisition |
| Payback period | Time to recover CAC |
Quick wins vs big bets
| Type | Approach |
|---|---|
| Quick win | Ship in days |
| Medium project | 1-2 week experiment |
| Big bet | Multi-week project |
Common growth areas
| Area | Experiments |
|---|---|
| Onboarding | Reduce friction |
| Pricing | Optimize conversion |
| Re-engagement | |
| Referral | Viral loops |
| Retention | Reduce churn |
Learning documentation
## Learning: [date]
### Experiment
[Link to experiment]
### Key Finding
[What we learned]
### Applicable To
[Where else this applies]
### Next Steps
[Follow-up actions]
Common growth mistakes
| Mistake | Better Approach |
|---|---|
| No hypothesis | Clear prediction |
| Too many changes | Isolate variables |
| Short experiments | Sufficient data |
| Ignoring losers | Learn from failures |
Growth team metrics
| Metric | Track |
|---|---|
| Experiment velocity | Per month |
| Win rate | % successful |
| Revenue impact | $ generated |
| Funnel improvement | Stage conversion |