Table of Contents
Introduction
In this chapter below the Jira setup for Yamaha Motor Next Stage project (YNS) is explained.
Per December 2023 YME solely leads the overall program for Yamaha Next Stage (YNS) EU roll-out .
Previously Ownership was at YMC and PWC EU was leading the overall program, with the handling over towards YME some changes in the Jira setup have been made.
Per all activities related to YNS YME Rollout will documented in YME Jira and Confluence.
EUYNS Project will not be used anymore on short term and the Backbone Issue sync towards YMC (hosted in Jira PWC US) will be stopped, also the Backbone issue sync between EUYNS and YIS project in YME Jira has been stopped.
Yamaha Motor Next Stage project EU Rollout progress will further be tracked under a new Jira project called Yamaha Motor Next Stage (YNSEU). Team related activities will be tracked under Yamaha IS Projects
YME documentation related to YNS for SAP and Informatica and YNS Teams - Procedures Guidelines Onboarding WoW is stored under Confluence Space IF.
Yamaha Motor Next Stage Projects (YNS) has been setup as supporting platform to check the progress between YMC and PwC at the same time in the YNS project.
By managing the project in Jira the progress is visualized and can be used for managing the relationship of tasks across teams, the relationships between stakeholders can be strengthened and appropriate methods can be considered within the YNS project.
YME will maintain all work done for all EU rollout Project in YME Jira, project YNSEU.
YME documentation related to YNS for SAP and Informatica and YNS Teams - Procedures Guidelines Onboarding WoW is stored under Confluence Space IF.
Yamaha Next Stage (YNS) Jira Project Management Policy
The Yamaha-motor Next Stage Jira Project Management Policy includes information like purpose of Jira implementation, progress management and rules.
Note: This presentation explains full setup done for YNS in PWC US. Jira YME is limited to EU Rollout Projects information only.
Loading of the presentation will take a while, please download the presentation to view the slides.
In principle, particularly for the YME integration team (TRANSFORMERS), all work relates to specific PDD FEATURES. Under a FEATURE, the Project team will specify more specific PDDs.
In there, the YME teams involved in integration will collaborate. Collaboration with YME teams is only done in Jira YME YIS project. Team information can be found under YNS Teams - Procedures Guidelines Onboarding WoW .
Hereunder, also naming convention is mentioned for PDD, epics etc.
WoW agreements
RISK management
- Changing the YNS project by adding EPICS that INCREASE the SCOPE, requires requires communication towards PMO, Rins and Vikas.
Planning
- Changing the YNS project by removing or downscaling scope requires communication towards PMO
Jira USAGE
- Any EPIC, story, task needs to be parent linked to the correct YNSEU FEATURE (PDD or project). This is the responsibility of the PO's and WS Leads. Do not link them via more, link, and any relation link option.
- Any change on EPIC, story or task, any communication on them, must be reflected in status, timing and comments on the respected issue types only. We do not e-mail as that will cause the risk of losing information.
- EPICS, stories and tasks must be created with a COMPONENT YNS if created in YIS. Any issuetype created in YNSEU will get this automatically. (reason: filters in Advanced roadmap use this to reflect the work for YNS)
- EPICS, stories and task must be created with the WORKSTREAM that corresponds the team working on it. (reason: filters in Advanced roadmap use this to reflect the work for YNS)
- EPICS, stories and task must be created with a TEAM. (reason: filters in Advanced roadmap use this to reflect the work for YNS per team)
- STORIES and TASKS must belong to EPICS via EPIC LINK alone (do not link them via more, link, and any relational link option). Meaning: stories and task cannot be created stand alone, else they will drop out of the project and therewith follow up.
Workstream
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:
Field "Dependent Workstream" is also synced but is not mandatory for having an issue synced between Jira PWC and Jira YME.
Yamaha Motor Next Stage project (YNSEU)
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. |
YNS Structure
The YNS project is structured according level 1 processes:
Highest level, it the L1, which can be Quote to Cash (QtC) or e.g. Deliver to Replace. L1 processes can be found here.
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).
In there we have the following structure:
Software Development and task execution within YME is done in project Yamaha IS Projects (YIS). YIS Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS).
ADVANCED ROADMAPS - project visualization
For all teams, Jira is provided with PLANS, which enables you to track the progress of (a section) the YNS project.
This feature in Jira enables you to quickly update your epics, stories, tasks and sub-tasks with e.g. dates, notes and enables you to (parentlink) new epics to Features.
---- elaborate further here.
Workstreams
Team
Field in EUYNS called: Client Team
Field in YIS called: Yamaha Team
Overview
Content Tools