- Stakeholders determined
- Conceptual approaches broken down or otherwise documented as outlines
- the WMF timeline that Wes described, for meeting Annual Planning (is already in notes; link to official version?)
- a hypothetical timeline based on our thorough work breakdown (of which we have a 1st draft) for MF definition and implementation
- a timeboxed version of previous that is possible and may be acceptable to
- Full sequence for helping WMF engineering teams do full evidence-based planning, including enumerating and estimating backlogs, forecasting, prioritizing, etc. (is roughly sketched out in notes; not clear we need much more detail for now, just this perspective)
- timeline that balances goals and achievability selected and circulated to stakeholders
- timeline approved by stakeholders
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | • ksmith | T122838 [EPIC] Engineering teams can communicate their capacity for core vs new work | |||
| Declined | • ksmith | T122842 [EPIC] Audience-facing product teams able to produce evidence-based data about the proportion of time spent on core vs. non-core work | |||
| Declined | None | T122849 [EPIC] Agreement on plan to achieve Core vs. Maintenance | |||
| Resolved | • JAufrecht | T127773 Document and circulate proposed next steps for Core Fraction from CFO review |
Event Timeline
Comment Actions
Are we setting all tasks that apply to TPG Q3 goals with the tag, or only the very top, parent tasks? As in:
Task 1 (TPG-2016Q3)
\
Task 2 (Milestone)
\ \ \
Task 3 Task 4 Task 5Comment Actions
This overlaps with T122256: Create Milestone Roadmap showing what would have to be true to do fully evidence-based FY17 planning in Jan-April 2016; need to figure out if they should be merged or what.
Comment Actions
@JAufrecht I advocate to merge this with T122256: Create Milestone Roadmap showing what would have to be true to do fully evidence-based FY17 planning in Jan-April 2016