Initiative

Initiatives are large Platform objectives that are strategically aligned with Sage’s goals. These are reserved for big items we expect to move the needle for the platform.

...

• Initiatives are created and managed by the Product Owner and approved by LT.

• Initiatives WILL HAVE one or more child Epics, which do not have to be completely defined to start an Initiative.

• Initiatives span across scrum teams, sprints and Jira projects.

Definition of Done

Initiatives are considered Done when the following are complete:

• All of the goals defined in the Initiative are achieved.

• Priorities have changed and LT/Stakeholders agree that the initiative is no longer necessary.

Notice, and Initiative's completeness is not dependent on the underlying issues being completed (though that may be necessary to meeting the goals.

Epic

Epics are feature-level work items that span teams and/or sprints. A typical Epic might require initial work from Design, the output of which informs requirements (Acceptance Criteria) for later stories by SWC. PLFM may have one or more stories that must be completed for SWC to complete their stories. An Epic may be a child of an Initiative, or may live on its own.

Definition of Done

Epics MAY BE considered Done when the following are complete:

• All of the goals defined in the Epic are achieved.

• All of the sub-issues (Stories and Tasks) are closed

Story

Stories are individual issues that represent work that a single delivery team can perform to provide value to a stakeholder.

• A story may be a child of an epic or may be independent

• Stories SHOULD be completed within a sprint

• Stories MAY have child Tasks or Bugs

• Stories MAY NOT span teams

Task

Tasks are smallest increment of work created by the delivery team to manage their work in completing stories or epics.

• A Task MUST BE estimated to complete within a sprint

• A Task MUST only be assigned to one individual

...