Page History
...
| ISSUE TYPE | USAGE |
|---|---|
| Capability | Highest level in YNSEU. Used to split the project in L1 processes. Capabilities can only be closed if underlying MILESTONES are closed! |
| Milestone | Second level in YNSEU. Used to divide the project to the level of Process delivery document (PDD) (L2,3,4). Milestones can only be closed if underlying FEATURES are closed! |
| Feature | Third level in YNSEU. Used to group bigger activities (mini projects) under a PDD. Features can only be closed if underlying EPICS are closed! |
| EPIC | Fourth level in YNSEU, but not residing as issue type there. EPICS reside under YIS and are meant for the power teams to do the work in. It is used to break up the features in to manageable iterations. EPICS are open for the maximum period of a quarter, and are used to plan QRP (quarterly release planning). EPICS only have 1 responsible team. Multiple teams working on a feature, means multiple EPICS. EPICS |
| Task | Part of an EPIC, usually there to record non-development work. Can only be closed after completion of sub-tasks! |
| Story | Part of an EPIC, usually there to record development work. Can only be closed after completion of sub-tasks! |
| Sub-Task | Part of a story or task, usually there to break up work in smaller pieces. |
| Decision | Stand alone issue type in YNSEU, used to record any decision we need to record and report upon. |
| Defect | A non-production related bug, coming from a unit or user test that needs fixing. |
| Bug | A production malfunction that requires fixing |
...
PLANS are setup based upon filters. For the YNSEU project, we filter upon:
| Field | Value |
|---|---|
| Workstream | EU XXXXX |
| Component | YNS |
| Team | Drop down list |
These fields are expected to be filled out. If you forget either of them, you will not be seeing your issue in the roadmap overview.
...
Overview
Content Tools