Page History
...
| Table of Contents | ||
|---|---|---|
|
Introduction
In this chapter below the Jira setup for Yamaha Motor Next Stage project (YNS) is explained.
...
YNSEU) is explained.
...
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 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 where the integration teams collectively work in.
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. We do advise you to check the Way of Working summary first, as this is the latest version and focused on team collaboration in a more concise manner.
| View file | ||||
|---|---|---|---|---|
|
YNS project structure
In principle , particularly for the YME integration team (TRANSFORMERS), all work relates to specific PDD FEATURESMILESTONES. Under a FEATUREMILESTONE, 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. FEATURES of a PDD where the teams can connect their EPICS to. See the project org structure in Jira below.
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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)
...
Collaboration with YNS teams is done in Jira via the YME YIS project. Teams information can be found here.
The YNS teams procedures, way of working agreements etc can be found here: YNS Teams - Procedures Guidelines Onboarding WoW .
Taxonomy YNS Issue Types
| ISSUE TYPE | USAGE |
|---|---|
| Capability | Highest level in YNSEU. Used to split the project in L1 processes. Capabilities can only be closed if underlying MILESTONES are closed! |
| Milestone | Second level in YNSEU. Used to divide the project to the level of Process delivery document (PDD) (L2,3,4). Milestones can only be closed if underlying FEATURES are closed! |
| Feature | Third level in YNSEU. Used to group bigger activities (mini projects) under a PDD. Features can only be closed if underlying EPICS are closed! |
| 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. EPICS |
| Task | Part of an EPIC, usually there to record non-development work. Can only be closed after completion of sub-tasks! |
| Story | Part of an EPIC, usually there to record development work. |
Can only be closed after completion of sub-tasks! | |
| 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. |
| Defect | A non-production related bug, coming from a unit or user test that needs fixing. |
| Bug | A production malfunction that requires fixing |
ADVANCED ROADMAPS (PLANS)
ADVANCED ROADMAPS, an integrated feature of Jira, can be used to visualize the project structure and progress. It can also be leveraged to report on dependencies.
It can be found under PLANS and then YNS ROADMPAP.
Prerequisites for seeing / viewing FEATURES, EPICS, STORIES and TASKS in Advanced Roadmaps
PLANS are setup based upon filters. For the YNSEU project, we filter upon:
| Field | Value |
|---|---|
| Workstream | EU XXXXX |
| Component | YNS |
| Team | Drop down list |
These fields are expected to be filled out. If you forget either of them, you will not be seeing your issue in the roadmap overview.
Workstream
The “Workstream” field in YNS Jira is used to distinguish which project the items are linked to and is mandatory to be filled in ANY issue type for proper project structure in Advance Roadmaps or any other dashboard PMO is using.
All related EU Rollout Projects in YNS Jira can be found under the following workstreams:
Field "Dependent Workstream" is also available but is not mandatory. This is more to specify dependencies. Dependencies on tasks, stories or epics MUST be indicated/visualized via a BLOCKED BY link in the respective issue type.
Teams
Display YNSEU Project structure
...
Opening PLANS and then particularly the YNS Program Roadmap will give you a similar look as the screenshots below. Explanation on how to read the project structure is provided there.
The YNS project is structured according level 1 processes:
...
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
...
CREATING an EPIC
CREATING a STORY or TASK and LINK it to the correct EPIC
CREATE an EPIC parentlink to a FEATURE
CREATE a FEATURE parentlink to a MILESTONE
...
Overview
Content Tools