Page History
...
- To Do: work has not yet started;
- In progress: the Decision subject is being discussed with stakeholders;
- On Hold: Status used if a Decision is set on hold;
- Done: The Decision has been made. Fields Fields Decision Type, Application(s), Workstream and Final Decision are mandatory to be filled before closing a Decision. Final decision should only be updated when all parties agree on the decision.
Once the decision is final and issue is marked as “Done”, the decision made will be shared via e-mail with the YNS project team members through an automated function. - Canceled: The situation about which a decision had to be made no longer occurs and has become redundant. Fields Workstream and Final Decision are mandatory to be filled before canceling a Decision.
YNS Decisions can be found on the following dashboard: YNS-YME Decisions Dashboard
YNS Issue creation Issue creation
YNSEU Issue creation
Users (licensed and authorized users) can use the 
button anywhere in Jira from the top bar.
...
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.
YNSEU Decision creation
| Anchor | ||||
|---|---|---|---|---|
|
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.
For YNS there are some specifics one must be aware off.
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