User:EProdromou (WMF)/Core Platform Team tasks

This is how we set up initiatives, epics, and tasks for Core Platform Team projects.

Initiatives
An initiative is a high-level project, like "Make a REST API" or "Build an API portal." It is made up of one or more epics (see below).


 * Each initiative has a single base Phabricator task. The title is usually the name of the project. Example: Wikimedia API Gateway.
 * The initiatives task should be on the CPT Initiatives workboard.
 * There should also be a column on the CPT Initiatives workboard (different board!) for the initiative.

Epics
An epic is a deliverable set of functionality -- a group of user stories that should be delivered together.


 * Each epic should have its own Phabricator task, like user contributions API.
 * Its parent task should be the initiative it belongs to. It should be tagged with the Epic tag.
 * Every epic should be tagged with the CPT Epics workboard.
 * It should also be tagged with the initiative that it's a part of so it appears in the right column on the CPT initiatives workboard.
 * It's often useful to describe personae for the user stories in an epic in the epic description.

User stories
User stories are units of functionality.


 * User stories each have a task.
 * The parent of the user story task is the epic that it's a part of.
 * They usually have the first line as a user story sentence, "As a , I want to , so that ."
 * The title is often a variant on the user story sentence, like " s".
 * User story tasks are tagged with the Story tag.
 * User story tasks are tagged on the User Story workboard.
 * User story tasks are tagged on the colour team workboard, like Green Team workboard.