...
Initiatives MUST have a set of goals to achieve before considered complete ready for team.
Some aspects of Initiatives:
...
All of the goals defined in the Initiative are achieved.
- OR -
Priorities have changed and LT/Stakeholders agree that the initiative is no longer necessary.
Notice, and an Initiative's completeness is not dependent on the underlying issues being completed (though that may be necessary to meeting the goals.
...
Tasks are smallest increment of work created by the delivery team to manage their work in completing stories or epics. A typical use of Tasks is to track work that can be parallelized across members of the team to complete a story.
A Task MUST BE estimated to complete within a sprint
A Task MUST only be assigned to one individual
Initiative | Epic | Story | Task | Bug | |
Spans Projects | ✔ | ✔ |
|
|
|
Spans Teams | ✔ | ✔ |
|
|
|
Spans Sprints | ✔ | ✔ | * |
|
|
Dependent on Hierarchy | ✔ | ✔ |
✔
Who can create? |
PO |
✔
Anyone can create
✔
PO | Anyone | Only Team Members |
✔
Anyone | |||||
Requires Estimation |
|
| ✔ | ✔ | ✔ |
|
|
|
|
|
|
*Agile best practice is for Stories to be completed within a sprint. This is a guideline at Sage, not a hard requirement.
...
Questions/Issues/FAQs
How do we track a grant project that has items that span across initiatives, epics, teams?