Page History
...
For YNS the following two Backbone syncs are active:
- Backbone sync YNS project between Jira PWC US (YMC) (CON0000585) and Jira YME for YNS(EUYNS)
Backbone sync between Jira YME
YNSEUYNS project and YIS project
The issues synced between both instances are limited to EU Rollout Projects only.
In short it means that any change done in PWC JIRA or YME JIRA is synchronized to each other for agreed issues types, workstream and team.
All YNS issues are connected and updated as soon as a change is done: e.g. CON0000585-54579 <-> EUYNS-1546 <-> YIS-11225
In Jira YME in EUYNS project both Backbone Syncs are visible in the right panel under Backbone Issue Sync.
Example: EUYNS-1546
Visual overview Backbone Sync PWC and YME
...
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 YME Jira YIS project. Team information can be found under Team Procedures .
Hereunder, also naming convention is mentioned for PDD, epics etc.
Backbone sync YNS project between Jira PWC US (YMC) and Jira YME
| Anchor | ||
|---|---|---|
|
...
|
...
|
The Jira Project name in both instances is similar: Yamaha Motor Next Stage project (YNS)
...
In Jira, the main person in charge and sub-person in charge will be assigned to each task.
All assigned persons need to exist in both Jira instances to prevent errors in Backbone Sync.
Backbone sync between Jira YME EUYNS project and YIS project
| Anchor | ||||
|---|---|---|---|---|
|
Software Development 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).
...
Overview
Content Tools