Page MenuHomePhabricator

Create Milestone Roadmap showing what would have to be true to do fully evidence-based FY17 planning in Jan-April 2016
Closed, DuplicatePublic

Description

Purpose: Demonstrate to the stakeholders requesting this [this = Core/Strategic work tracking, and the ability for teams to answer the question "what can I do next quarter" from evidence] what that entails, at a high-level, and what is feasible within the time period requested (e.g. "Q3").

  • Document TPG-related (and other?) necessary conditions for evidence-based annual planning
    • Work Breakdown added here
  • sanity-test this roadmap
  • if not practical, create roadmap for what is possible
    • Should contain
      • set definitions of Core/Maintenance
      • possibly produce some more numbers in time to be useful
      • continue piloting backlogs, milestone tracking, estimation, forecasting, SPDPP in 2-3 teams
        • This is out of scope for the Core measurement part
    • this should be covered by the Work Breakdown

Event Timeline

JAufrecht raised the priority of this task from to Medium.
JAufrecht updated the task description. (Show Details)

Kevin, would you like to take the first stab at this? My notion of a list is in these notes, if you want a starting point.

I took a first stab, and Joel is greatly expanding and improving it. In related news, I created this page: https://www.mediawiki.org/wiki/Team_Practices_Group/Tracking_core_and_strategic_work

ksmith set Security to None.
ksmith moved this task from To Do to In Progress on the Team-Practices (This-Week) board.
JAufrecht updated the task description. (Show Details)

@ksmith @JAufrecht could you please add the relevant page to review?

@JAufrecht I took a spin through and left comments on the relevant tasks.

IIRC, that rationale for doing this task was to demonstrate to the stakeholders requesting this work what is entailed (at a high-level) and what is feasible within the time period requested (e.g. "Q3"). It might be worth adding this to the task description.

Added the rationale to task description.

I saw a comment in T122839: [EPIC] A documented and agreed upon definition of ‘core work’ exists about breaking out not-critical portions; Kevin and I will discuss where and how that could happen. Are there other comments, and are they blockers for this particular task?

@JAufrecht the other comment was about merging two tasks, you should have received a Phab ping. Otherwise looks good.