Page History
Table of Contents
| Table of Contents | ||
|---|---|---|
|
Introduction
In this chapter below the Jira setup for Yamaha Motor Next Stage project (YNS) is explained.
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 Jira. To prevent double maintenance in two systems addon Backbone Sync is used to sync YNS project between Jira PwC US Jira and Jira YME.
The issues synced between both instances are limited to EU Rollout Projects only.
Backbone sync between Jira YME and Jira PWC US
Jira issue synchronization between YME and PWC US only supports specific issue types:
- Action Items (stand alone tasks)
- Tasks (originating from PROJECT/EPIC)
- Sub-Task (originating from task)
- Issues (originating from EPIC)
- Risks (originating from EPIC)
- EPICS (Project)
- FEATURES (Project)
- Decision (Project)
The issues synced between both Jira instances are limited to EU Rollout Projects only.
The “workstream” field in YNS Jira is used to distinguish which project the items are linked to.
All related EU Rollout Projects in YNS structure:Jira can be found under the following workstreams:
Yamaha Motor Next Stage project (YNS)
YNS structure
01_YNS_JIRA_ProjectManagementPolicy_EN_v1.08 (1).pptx
YNS Issue Types
YNS Structure
In JIRA, the main person in charge and sub-person in charge will be assigned to each task.
Link YNS and YIS
Create YIS Epic per interface
Story if needed for design/development
Sub-tasks per story to break down the work.
...
Overview
Content Tools