- Create project directory structure
- Set up Python virtual environment
- Install all dependencies from requirements.txt
- Verify installation with test imports
- Research food delivery app pain points
- Brainstorm 15+ feature ideas across categories:
- Customer Retention
- Order Value Increase
- User Experience
- Operational Efficiency
- Discovery & Exploration
- Document each feature with description
- For each feature, estimate:
- Reach: % of MAU affected
- Impact: Qualitative score (Massive/High/Medium/Low)
- Confidence: Based on research/precedent (High/Medium/Low)
- Effort: Engineering time in person-months
- Run
prioritization.pyto calculate RICE scores - Review top 3 features
- Document rationale for estimates
- Select top 3 features from RICE analysis
- Write complete PRDs including:
- Problem statement
- User stories
- Acceptance criteria
- Success metrics
- Technical considerations
- Launch plan
- Save in
prds/directory
- Select #1 ranked feature for testing
- Design test parameters:
- Control vs Treatment groups
- Sample size calculations
- Test duration
- Primary and secondary metrics
- Guardrail metrics
- Document test plan
- Run
ab_test_simulator.py - Generate synthetic user behavior data
- Perform statistical analysis:
- Chi-square test
- Z-test for proportions
- Confidence intervals
- Power analysis
- Interpret results
- Run
visualization.py - Generate all charts:
- RICE score rankings
- Effort vs Impact matrix
- A/B test funnel
- Conversion trends
- Executive dashboard
- Review and annotate key insights
- Compile final report
- Write executive summary
- Document recommendations
- Prepare presentation deck (optional)
- Update README with results
- Document methodology
- Add comments to code
- Create architecture diagram
- Run all tests
- Verify all outputs generated
- Check for broken links/paths
- Final review of documentation
Total Time: ~9 hours spread over 2-3 days
- RICE framework provides objective prioritization
- Statistical validation prevents false positives
- Data visualization crucial for stakeholder buy-in
- Documentation as important as analysis
- Estimating confidence levels without real data
- Balancing detail vs simplicity in PRDs
- Choosing right sample size for simulation
- Making visualizations executive-friendly
- Build interactive Streamlit dashboard
- Add more sophisticated ML models
- Include multi-variant testing
- Create video walkthrough