Page History
...
In this chapter below the Jira setup for Yamaha Motor Next Stage Project structure in Jira is explained. It includes an explanation of YNS Project Structure of working in Jira for project Yamaha Next Stage (YNSEU) is explained. and Yamaha IS Projects (YIS).
Never worked with Jira before? No problem. Please first read the Jira training Basics page.
...
| ISSUE TYPE | USAGE |
|---|---|
| Highest level in YNSEU. Used to split the project in L1 processes. Capabilities can only be closed if underlying MILESTONES are closed! |
| 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! |
| Third level in YNSEU. Used to group bigger activities (mini projects) under a PDD. Features can only be closed if underlying EPICS are closed! |
| 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 cannot be closed UNLESS the stories and tasks are completed. |
| Part of an EPIC, usually there to record non-development work. Can only be closed after completion of sub-tasks! |
| Part of an EPIC, usually there to record development work. Can only be closed after completion of sub-tasks! |
| Part of a story or task, usually there to break up work in smaller pieces. |
| A non-production related bug, coming from a unit or user test that needs fixing. |
| A production malfunction that requires fixing |
| Stand alone issue type in YIS, used to record any decision we need to record and report upon. Decision can only be closed when fields Workstream and Final Decision are filled! |
...
YNSEU Project structure in Roadmaps/Plans
ADVANCED ROADMAPS, an integrated feature of Jira, can be used to visualize the project structure and progress. It can also be leveraged to report on dependencies.
...
The project structure is stored in Jira PROJECT YNSEU. It ends at the level of FEATURE.
The YNSEU project also has some other issuetypes, like DECISION which are only used in the YNS project.
From EPIC level, the work is stored in the Jira PROJECT YIS (Yamaha Information Systems).IS Projects).
Also other Issue types on Issue level (Story, Task, Bug, Defect) are used in YIS.
Sub-Tasks is the underlying level which can also be used for Story, Task, Bug, Defect to break down the work.
DECISION Issue type is stored in YIS, but only used for YNS Project planning.
In there we have the following structure:
...
Yamaha Motor Next Stage (YNSEU)
YNSEU Issue Types
YNSEU issues overview
...
YNSEU Workflows
The YNSEU project contains 1 workflow that is used by all the issue types.
- To Do: work has not yet started;
- In Progress: The work on the high level structure issue has been started, Target end and Target start date must be filled.
- On Hold: High level structure item is put on hold when it is not possible to proceed
- Done: This high level structure item has been completed, including all underlying issues.
- Canceled: No further work will be done on this high level structure issue, it is not required anymore or has become obsolete.
YNS Issue creation
YNSEU Issue creation
...
Overview
Content Tools