...

In a future state for 2023 only the Jira Projects in black text above will remain for Information Systems.

• Yamaha Applications Support Desk (SD) captures all requests from end-users, who experience difficulties with their day-to-day use of IT applications. These items are validated, then if valid resolved as soon as possible.
  
• Yamaha IS Projects (YIS) captures all work of (scrum) teams in the Agile Transformation. These processes are being streamlined to support scrum processes, and make Jira a tool for collaboration more than administration.
• B2C-Apps (B2C) captures all work for B2C /EPAM team(s) working with waterfall methodology. Processes are being streamlined with new Yamaha way of working.
• Yamaha Portfolio Board (YPB) collects all ideas for IT initiatives, and validates the business case and expected rewards for implementing such initiatives before assigning work to development teams. It's very much about preparing work.
• Other Software delivery projects capture work for teams that have not yet joined the Agile Transformation and will be phased out when moved to YIS.

• Yamaha Motor next Stage Project (EUYNS) 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.
  

In due time, Information Systems teams working in Jira Software projects will be onboarded to the YIS project, so this can become our mutually agreed way of working for Software delivery.
Any team joining will be coached through the (Agile) transition and will be able to provide input on unique ways of working that will need to be integrated. Together we will make it a success.
For now, these Information Systems projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS. 

The Change Advisory Board (CAB) captures approval of fixes and creation of a functional/technical conceptional design document , this will be phased out completely as it will be covered by the Yamaha Portfolio Board and Software project(s).

•  
  Per 01 Jan 2024 this project will be replaced by a new structure Yamaha Motor Next Stage (YNSEU) after the lead has been handled over to YME.

• Yamaha Motor Next Stage (YNSEU) captures the high level Project tracking for Yamaha Next Stage project EU rollout. 

In due time, Information Systems teams working in Jira Software projects will be onboarded to the YIS project, so this can become our mutually agreed way of working for Software delivery.
Any team joining will be coached through the (Agile) transition and will be able to provide input on unique ways of working that will need to be integrated. Together we will make it a success.
For now, these Information Systems projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS. 

The Change Advisory Board (CAB) captures approval of fixes and creation of a functional/technical conceptional design document , this will be phased out completely as it will be covered by the Yamaha Portfolio Board and Software project(s).

In paragraphs below In paragraphs below you can find a short summary per project and links to the more detailed Jira-project documentation.

...

More detailed documentation for this project can be found under  Jira training for Yamaha Applications Support Desk (SD).

Change Advisory Board (CAB) 

Anchor
Change Advisory Board (CAB) Change Advisory Board (CAB)

Change advisory Board (CAB) project  project is used for approval of fixes and creation of a functional/technical conceptional design document.

One of the two following conditions must be met to create a CAB issue.

1. Image ModifiedBug: Bugfix to deliver a functional/technical solution for the original SD issue. SD issue remains open until the fix has been applied.
2. Image ModifiedStory: Non-bugfix for internal improvement, prevent (recurring) issues for the future. SD issue can be closed, user will be informed that current issue is fixed but there will still be worked on in the background to prevent from happening again or improvements.

Under the SD issue the reporter and requested participants can be informed about the change applied/ to be applied but is also used to collect information from the requester.

Function design (FD) and  and Technical design (TD) documents  documents can be found in Confluence under space  space  Functional Conceptional Designs.
At the main page instructions can be found how a Functional/Technical Conceptional Design document can be created (via standardized template).
Image Modified

More detailed documentation for this project can be found under Jira Training for Change Advisory Board (CAB)

Yamaha Portfolio Board (YPM) 

Anchor
Yamaha Portfolio Board (YPM) Yamaha Portfolio Board (YPM)

...

In due time, Information Systems teams working in Jira Software projects will be onboarded to the YIS project, so this can become our mutually agreed way of working for Software delivery.

Any team joining will be coached through the (Agile) transition and will be able to provide input on unique ways of working that will need to be integrated. Together we will make it a success.

For now, these Information Systems teams working in Jira Software projects will be onboarded to the YIS project, so this can become our mutually agreed way of working for Software delivery.

Any team joining will be coached through the (Agile) transition and will be able to provide input on unique ways of working that will need to be integrated. Together we will make it a success.

For now, these Information Systems projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS. 

Jira project B2C-Apps (B2C) will remain for B2C teams working with Waterfall methodology. Processes are being streamlined with new Yamaha way of working.

...

projects will keep on using their current of way of working. With time and proper preparation, they will migrate into YIS. 

Jira project B2C-Apps (B2C) will remain for B2C teams working with Waterfall methodology. Processes are being streamlined with new Yamaha way of working.

Yamaha IS Projects (YIS)  

Anchor
Yamaha IS Projects (YIS) Yamaha IS Projects (YIS)

Project YIS is set up as a single space to allow Information Systems and Business to align on an Agile way of working, as part of the Agile Transformation.

Together we strive to arrive at a Jira configuration that is usable for all teams, supporting all YME Information Systems processes in a comprehensive, simplified manner.

Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS) 

B2C-Apps (B2C) 

Anchor
B2C-Apps (B2C) B2C-Apps (B2C)

Project B2C

...

Project YIS is set up as a single space to allow Information Systems and Business to align on an Agile way of working, as part of the Agile Transformation.for Consumer Train to work with a Waterfall methodology.

Together with EPAM and Yamaha teams Together we strive to arrive at a Jira configuration that is usable for all teamsB2C, supporting all YME Information Systems processes in a comprehensive, simplified manner.

Documentation can be found on the following page: Jira training for Yamaha IS Projects (YIS) 

...

B2C-APPS (B2C)

Yamaha Motor next Stage Project (EUYNS) 

Anchor

...

Yamaha Motor next Stage Project (EUYNS) Yamaha Motor next Stage Project (EUYNS)

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.
Only some Information Systems and Business users are having access to this project

...

Project B2C is set up as a single space for Consumer Train to work with a Waterfall methodology.

Together with EPAM and Yamaha teams we strive to arrive at a Jira configuration that is usable for B2C, supporting all YME Information Systems processes in a comprehensive, simplified manner.

Documentation can be found on the following page: Jira training for B2C-APPS (B2C)

...

Yamaha Motor Next Stage Project (EUYNS)

Yamaha Motor Next Stage (YNSEU)

Anchor
Yamaha Motor Next Stage (YNSEU

...

) Yamaha Motor Next Stage

...

(

...

YNSEU)

YNSEU has been setup as supporting platform to check the progress between YMC and PwC at the same time in the to track the high level planning for Yamaha Next Stage project EU rollout. 
By managing the Yamaha Motor Next Stage 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.
Only some Information Systems and Business users are having access to this project.

Documentation can be found on the following page: Jira training Yamaha Motor Next Stage Project (EUYNSYNSEU)

Issue assignment 

For all Jira-Projects used by Information Systems except for EUYNS the following issue assignment information applies.
If action from a Information Systems team is required or of it has been wrongly addressed some settings need to be changed to address it to the correct team/Train.
Visibility of issues in a queue/dashboard/board depends for all Information Systems Teams on the following 2 settings:

1. Solution group (all Projects used by Information Systems except YNSEU)
2. Yamaha Team or Yamaha Team(s)
   1. Multi select field Yamaha Team(s) field is used in YPM project for issue type: Program, Project, Enhancement and Epicand YNSEU
   2. Single select field Yamaha Team is used for all other Jira Projects and Issue types used by Information Systems Division.

...

Within Information Systems Division there are three four Agile Release Trains

• Consumer Train 
• Business Train
• Enable/ Shared Services Shared Services Train
• Data and Integration Train

The train is made up of multiple agile teams, an overview can be found on the following page: Team details - all trains

Incoming issue handling for Yamaha Application Support Desk (SD)

...