Page History
...
Issues can also being created via the Board or backlog. Detailed instructions can be found in Jira training Basics - Issue Creation.
...
YNSEU Decision creation
| Anchor | ||||
|---|---|---|---|---|
|
An EPIC YNS DECISION is ALWAYS created in the YIS YNSEU project. YNS EPICS DECISIONS are the responsibility of the PO's and WS leads and PMO team to maintain. They are the owners.
Creating an EPIC Decision is considered to be a basic skill for members (via CREATE). See also the Jira Basics Training. You need to follow that training first, before you continue this manual.
For YNS there are some specifics one must be aware off.
Here you see the component being filled with YNS, you see a correct parent link to the feature and the workstream is correctly filled out (EU S&L (UNITS)).
To plan for a QRP, PO's will also set the TICKETGROUP(s) to the quarter of delivery (e.g. QRP-2024-Q1). This helps to create a special advanced roadmaps filter solely focusing on what teams have committed to for a quarter.
...
An YNS DECISION is ALWAYS created in the YNSEU project. YNS DECISIONS are the responsibility of the PO's and WS leads and PMO team to maintain. They are the owners.
Creating an Decision is considered to be a basic skill for members (via CREATE). See also the Jira Basics Training. You need to follow that training first, before you continue this manual.
...
Phase: Select the relevant Phase when necessary
Workstream: Select the workstream that has started the Decision
Dependent Workstream: Select the those other workstreams that are relevant.
Decision Type: Always select “YME Internal”. “YME-YMC Liaison” is only for PMO.
Applications: Select all relevant applications that are affected by this decision
Yamaha Teams: Select the relevant Yamaha Team(s) involved in the decision making
Target start date: Select the start date of the decision making
Target end date: Select the end date when the decision has to be made.
If further explanation of the decision is required you can link it to the Parent or Epic or any other concerned issue(s). For example, if there is a decision linked to PDDs, you can add the Parent/Epic link to the respective PDD topic
YIS Epic creation
An EPIC is ALWAYS created in the YIS project. YNS EPICS are the responsibility of the PO's and WS leads to maintain. They are the owners.
Creating an EPIC is considered to be a basic skill for members (via CREATE). See also the Jira Basics Training. You need to follow that training first, before you continue this manual.
For YNS there are some specifics one must be aware off.
Here you see the component being filled with YNS, you see a correct parent link to the feature and the workstream is correctly filled out (EU S&L (UNITS)).
To plan for a QRP, PO's will also set the TICKETGROUP(s) to the quarter of delivery (e.g. QRP-2024-Q1). This helps to create a special advanced roadmaps filter solely focusing on what teams have committed to for a quarter.
Phase: Select the relevant Phase when necessary
Workstream: Select the workstream that has started the Decision
Dependent Workstream: Select the those other workstreams that are relevant.
Decision Type: Always select “YME Internal”. “YME-YMC Liaison” is only for PMO.
Applications: Select all relevant applications that are affected by this decision
Yamaha Teams: Select the relevant Yamaha Team(s) involved in the decision making
Target start date: Select the start date of the decision making
Target end date: Select the end date when the decision has to be made.
If further explanation of the decision is required you can link it to the Parent or Epic or any other concerned issue(s). For example, if there is a decision linked to PDDs, you can add the Parent/Epic link to the respective PDD topic
Issue link
| Anchor | ||||
|---|---|---|---|---|
|
...
Overview
Content Tools