Page MenuHomePhabricator
Create Task
Maniphest T122838

[EPIC] Engineering teams can communicate their capacity for core vs new work
Closed, DeclinedPublic
Actions

Description

This is a TPG FY2016Q3 quarterly goal.

To ultimately answer this question, teams will also have to be able to address the following. However, these are out of scope for the FY2016Q3 goal and should be rolled into followup goals.

  • Teams have backlogs
  • Backlogs are prioritized
  • Backlogs are estimated/quantified
  • New work is identified
  • New work is estimated
  • New work is prioritized relative to current backlogs

Related Objects
Search...

Event Timeline

• JAufrecht created this task.Jan 4 2016, 8:32 PM
• JAufrecht assigned this task to • ksmith.
• JAufrecht raised the priority of this task from to Needs Triage.
• JAufrecht updated the task description. (Show Details)
• JAufrecht added projects: Team-Practices, Phlogiston-Category.
• JAufrecht added subscribers: Aklapper, • JAufrecht.
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptJan 4 2016, 8:32 PM
• JAufrecht moved this task from Backlog to Team Practices Group on the Phlogiston-Category board.Jan 4 2016, 8:59 PM
• JAufrecht updated the task description. (Show Details)
• JAufrecht removed a project: Phlogiston-Category.
• JAufrecht set Security to None.
• JAufrecht added a project: TPG-2016Q3.Jan 4 2016, 9:31 PM
• JAufrecht updated the task description. (Show Details)Jan 6 2016, 12:08 AM
• JAufrecht added a subtask: T122256: Create Milestone Roadmap showing what would have to be true to do fully evidence-based FY17 planning in Jan-April 2016.Jan 6 2016, 12:11 AM
• ksmith renamed this task from Engineering teams can communicate their capacity for core vs new work to [EPIC]Engineering teams can communicate their capacity for core vs new work.Jan 14 2016, 10:43 PM
• ksmith triaged this task as High priority.
• ksmith added a project: Epic.
• ksmith moved this task from To Triage to In-progress EPICS on the Team-Practices board.
• ksmith moved this task from In-progress EPICS to General backlog on the Team-Practices board.Jan 14 2016, 10:49 PM
• JAufrecht removed a subtask: T122839: [EPIC] A documented and agreed upon definition of ‘core work’ exists.Jan 25 2016, 7:45 PM
• JAufrecht added a subtask: T122839: [EPIC] A documented and agreed upon definition of ‘core work’ exists.Jan 25 2016, 8:36 PM
• JAufrecht updated the task description. (Show Details)Jan 25 2016, 8:39 PM
• JAufrecht renamed this task from [EPIC]Engineering teams can communicate their capacity for core vs new work to [EPIC] Engineering teams can communicate their capacity for core vs new work.Jan 25 2016, 8:46 PM
• JAufrecht updated the task description. (Show Details)Jan 25 2016, 8:48 PM
• KLans_WMF moved this task from Backlog to Epics on the TPG-2016Q3 board.Mar 25 2016, 10:40 PM
• KLans_WMF closed this task as Declined.Mar 30 2016, 8:50 PM
• ksmith closed subtask T122839: [EPIC] A documented and agreed upon definition of ‘core work’ exists as Declined.Jun 30 2016, 10:29 PM
• ksmith closed subtask T122842: [EPIC] Audience-facing product teams able to produce evidence-based data about the proportion of time spent on core vs. non-core work as Declined.
• ksmith closed subtask T122841: [EPIC] Product-facing teams have agreed upon method for tracking core/strategic work as Declined.
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits