Core Platform Team/PET Work Processes/PET Task Process

Task life cycle edit

Internal CPT Projects edit

  • All projects must go through the planning process defined by our CPT Initiative Planning process
  • When projects reach the Create Phabricator Epic stage the following happens:
    1. An Epic(Milestone) column is created on the Core Platform Team (CPT) board
    2. A set of Tasks that completely describe the work to be done to complete the project are created
    3. Each Task goes through the Task Process to be ready to be worked on
  • Epics should be
    1. Scheduled
    2. Assigned to a specific Team
  • 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.
    1. Tasks selected to be worked on next will move to the Ready column of the Team’s Work board
    2. Tasks will then move through the work board until completed when they reach Done
      1. Task progress should be checked at the sprint check in and the board adjusted - worked scoped up/down as appropriate
    3. At the end of a sprint Tasks in Done should move to Done with CPT


 


Task Preparation Process edit

In order for a Task to be ready to work on it should meet the CPT Task Criteria and:

  1. Have a complete description
  2. Acceptance Criteria
  3. Testing Criteria
  4. Have a work estimation/story point(using fibonacci numbers for bucketing) Tasks with Story Points > Threshold should be decomposed into smaller blocks of work
  5. Have been prioritised

External Tasks edit

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


 

Task scheduling edit

  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