Core Platform Team/PET Work Processes/PET Task Process

Internal CPT Projects

 * 1) All projects must go through the planning process defined by our Project Planning Workboard
 * 2) When projects reach the Create Phabricator Epic stage the following happens:
 * 3) An Epic(Milestone) column is created on the Core Platform Team (CPT) board
 * 4) A set of Tasks that completely describe the work to be done to complete the project are created
 * 5) Each Task goes through the Task Process to be ready to be worked on
 * 6) Epics should be
 * 7) Scheduled
 * 8) Assigned to a specific Team
 * 9) Once a Project has been scheduled to be worked on the PM, EM and Team Lead/Team should meet to determine the work that will go into the next sprint.
 * 10) Tasks selected to be worked on next will move to the Ready column of the Team’s Work board
 * 11) Tasks will then move through the work board until completed when they reach Done
 * 12) Task progress should be checked at the sprint check in and the board adjusted - worked scoped up/down as appropriate
 * 13) At the end of a sprint Tasks in Done should move to Done with CPT

Task Preparation Process

 * 1) In order for a Task to be ready to work on it should:
 * 2) Have a complete description
 * 3) Acceptance Criteria
 * 4) Testing Criteria
 * 5) Have a work estimation/story point(using fibonacci numbers for bucketing)
 * 6) Tasks with Story Points > Threshold should be decomposed into smaller blocks of work
 * 7) Have their priority set

External Tasks

 * 1) A task arrives in the CPT board Inbox
 * 2) The task is evaluated during the Triage meeting
 * 3) If and only if the task is to be worked on it should
 * 4) Be determined which team should work on it
 * 5) Go through the Task Preparation Process
 * 6) Be scheduled
 * 7) Move to the Inbox for the assigned Team
 * 8) Whether or not an internal task goes into a sprint is a negotiation between the sprint owner(PM) and stakeholders

Task scheduling

 * 1) The Product Manager is responsible for identifying, with consultation from the EM/Tech Leads, which tasks can be worked on in which order
 * 2) The PM is responsible for determining which tasks will be selected for a sprint
 * 3) The Next column of a team’s board should be used to store tasks for the next sprint
 * 4) A Pre-sprint meeting is held and tasks for the immediate sprint are selected from the Next column and moved to the Ready column

Triage Meeting
The boards this meeting reviews are:


 * Core Platform Team (CPT)
 * CPT Kanban
 * CPT Backlog


 * 1) Review Inbox for each board
 * 2) For each item in each inbox determine
 * 3) Status
 * 4) Ask
 * 5) Next step
 * 6) Review Backlog board to determine high priority tasks that should be scheduled in future sprints
 * 7) Move tasks to be scheduled for future sprints to Non-Core Epic column on Core Platform Team (CPT) board

Triage Process


 * How is external - not UBN work - scheduled?
 * Triage can proxy for technical details
 * But Product and Management should determine scheduling
 * When, where?

Asana -> Create Initiative -> Create Epics as columns on Initiative board

When work is ready to be done

Move task from Epic on Initiative Board to Team board