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 MUST have a set of goals to achieve before considered complete.

Some aspects of Initiatives:

• 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.

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.

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

*Agile best practice is for Stories to be completed within a sprint. This is a guideline at Sage, not a hard requirement.