Files
roboco/.tasks/initiatives/_template/timeline.md
T
2025-12-10 02:49:54 +01:00

132 lines
3.2 KiB
Markdown

# Timeline: {Initiative Name}
> **Last Updated**: YYYY-MM-DD
> **Overall Status**: {on_track / at_risk / delayed}
---
## Summary
| Metric | Value |
|--------|-------|
| **Start Date** | YYYY-MM-DD |
| **Target Completion** | YYYY-MM-DD |
| **Current Progress** | X% |
| **Days Remaining** | X days |
| **Status** | {on_track / at_risk / delayed} |
---
## Milestones
| # | Milestone | Target | Actual | Status | Notes |
|---|-----------|--------|--------|--------|-------|
| 1 | Requirements Finalized | YYYY-MM-DD | - | pending | |
| 2 | Design Complete | YYYY-MM-DD | - | pending | |
| 3 | Backend API Ready | YYYY-MM-DD | - | pending | |
| 4 | Frontend Integration | YYYY-MM-DD | - | pending | |
| 5 | QA Complete | YYYY-MM-DD | - | pending | |
| 6 | Documentation Complete | YYYY-MM-DD | - | pending | |
| 7 | Launch | YYYY-MM-DD | - | pending | |
---
## Gantt View
```
Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
------------|---|---|---|---|---|---|---|---|
Requirements| ██| | | | | | | |
UX Design | | ██| ██| | | | | |
Backend | | ██| ██| ██| | | | |
Frontend | | | | ██| ██| ██| | |
QA | | | | | | ██| ██| |
Docs | | | | | | | ██| |
Launch | | | | | | | | ██|
██ = Planned work
░░ = Buffer/contingency
▓▓ = Completed
```
---
## Weekly Schedule
### Week 1: {Date Range}
**Focus**: Requirements & Planning
| Day | Activity | Owner |
|-----|----------|-------|
| Mon | Requirements review | Product Owner |
| Tue | Technical planning | Main PM |
| Wed | Task breakdown | Main PM |
| Thu | Task assignment | Cell PMs |
| Fri | Kickoff | All |
---
### Week 2: {Date Range}
**Focus**: Design & Backend Start
| Day | Activity | Owner |
|-----|----------|-------|
| Mon | Design begins | UX-Dev |
| Tue | Backend planning | BE-Dev |
| Wed | {activity} | {owner} |
| Thu | {activity} | {owner} |
| Fri | Design review | UX-QA |
---
## Critical Path
The critical path is:
1. Requirements → Design → Frontend → QA → Launch
**Critical dependencies**:
- Frontend cannot start until design is complete
- Frontend cannot integrate until Backend API is ready
- QA cannot begin until Frontend is complete
**Parallel tracks**:
- Backend API can proceed in parallel with Design
- Documentation can proceed in parallel with QA
---
## Risk Assessment
| Risk | Probability | Impact | Mitigation | Status |
|------|-------------|--------|------------|--------|
| Design delays | Med | High | Start with wireframes | Watching |
| API complexity | Low | Med | Early technical spike | Mitigated |
| {risk} | {prob} | {impact} | {mitigation} | {status} |
---
## Buffer & Contingency
| Phase | Planned | Buffer | Total |
|-------|---------|--------|-------|
| Design | 5 days | 1 day | 6 days |
| Backend | 7 days | 2 days | 9 days |
| Frontend | 10 days | 2 days | 12 days |
| QA | 3 days | 1 day | 4 days |
**Total buffer**: X days
---
## Timeline Adjustments
| Date | Adjustment | Reason | Impact |
|------|------------|--------|--------|
| YYYY-MM-DD | {change} | {reason} | {impact} |
---
## Notes
{Additional timeline considerations, holidays, team availability, etc.}