...
Hereunder, also naming convention is mentioned for PDD, epics etc.
...
The issues synced between both Jira instances are limited to EU Rollout Projects workstreams only.
The “Workstream” field in YNS Jira is used to distinguish which project the items are linked to and is mandatory to be filled for syncing an issue between Jira PWC and Jira YME.
All related EU Rollout Projects in YNS Jira can be found under the following workstreams:
...
Yamaha Motor Next Stage project (EUYNS) is setup as a Jira Software delivery project in Jira YME.
This project is used by all teams to plan and track the progress the YNS work.
YNS Issue Types
ISSUE TYPE | USAGE |
---|---|
Capability | Highest level in YNSEU. Used to split the project in L1 processes |
Milestone | Second level in YNSEU. Used to divide the project to the level of Process delivery document (PDD) (L2,3,4) |
Feature | Third level in YNSEU. Used to group bigger activities (mini projects) under a PDD |
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. |
Task | Part of an EPIC, usually there to record non-development work. |
Story | Part of an EPIC, usually there to record development work. |
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. |
The YNS project is structured according level 1 processes:
...