...

Introduction

Never worked with Jira before? No problem. Please first read the Jira training Basics page.
In this chapter below the Jira setup for Information Systems Jira-projects is explained.

Jira projects

Information Systems Division is using the following Jira projects:

...

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

J-sox compliance

J-SOX requires Japanese companies to enhance internal control reporting and demonstrate the effectiveness of their internal controls. 

...

Beforehand it is not known if a database correction or program change is required, to prevent delay in resolving reported requests the users manager is automatically added to the request (Jira issue/ticket).
YME and distributor users are directly synchronized in Jira with Active directory including users manager. The users manager is added via a automation after request creation in the Yamaha Applications Support Desk (SD). 
Active directory is maintained by Servicedesk.

Yamaha Applications Support Desk (SD) 

Anchor
Yamaha Applications Support Desk (SD) Yamaha Applications Support Desk (SD)

In Yamaha Applications Support Desk all operational support (BAU- Business As Usual) requests are registered that relates to IT Application Issues/errors for existing functionality, data correction and authorization requests.

...

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

Yamaha Portfolio Board (YPM) 

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

Before work is ready for development, any initiative (idea) for software development is first vetted by the portfolio management, to understand whether the proposal is of strategic value to YME.
Once it is agreed that the initiative should be implemented, a selection of what to do first is made based on business case, priority, and urgency. This way we ensure that time is spent on the most valuable topics.
In Jira these initiatives are created within Jira-Project Yamaha Portfolio Board (YPM). After a initiative is approved in the Yamaha Portfolio Board (YPM), development items for implementation will be created by the teams in a Jira Software Delivery Project.

Jira Training documentation can be found under: Jira training for Yamaha Portfolio Planning (YPM).

Software delivery projects

...

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 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) 

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.

...

Yamaha Motor Next Stage (YNSEU)

Anchor
Yamaha Motor Next Stage (YNSEU) Yamaha Motor Next Stage (YNSEU)

YNSEU has been setup 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 for Yamaha Motor Next Stage (YNSEU)

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 and YNSEU
   2. Single select field Yamaha Team is used for all other Jira Projects and Issue types used by Information Systems Division.

Overview Solution group and Yamaha Team / Yamaha Team(s)

Within Information Systems Division there are four Agile Release Trains

...

Incoming issue handling for Yamaha Application Support Desk (SD)

For all incoming SD issues the following field selections need to be checked if the correct one is selected, if not please adjust or add:

1. Adjust or add correct Yamaha Team
   After Changing Yamaha Team the Solution group will automatically be corrected via automation rule.
   
2. Adjust if not the correct SD Classification is selected
3. Adjust the Application-Module if wrongly selected
4. Check if request includes are requires information, if not ask customer to provide more information. 
5. An Issue can be allocated to a person when starting on the request/taking care of the request.
   When issue has been assigned before then only re-assign the issue.
   Re-opened issues also need to be re-assigned via the Re-assigned-comment button. 

Assigning an issue to different team

For moving a issue/ticket to a different train/team follow below procedure:

...

The persons who are handling the queues from the train/team will take further care of the ticket and move them to the second line if needed.

Add-ons used by Information Systems

• Agile Tools & Filters for Jira Software
• Checklist for example used for Custom field DOD in Software projects.
• Doublecheck for Jira Service Management 
• Eazy BI
• Jenkins Integration for Jira Server and Data Center
• ProForma: Forms for Jira
• Status Time Free
• Timesheet Reports and Gadgets
  This addon is used by Information Systems, Business train to log hours spend on Projects, issues. When hours are logged there is more insight in the velocity of teams and specifically projects.
  Secondly we expect to see the exact number of hours that are contract wise in place per person per month. In order to get a clear overview, we also expect hours to be registered to the correct issues.
  As you all will have time which can not be related to a issue/project directly, e.g. a meeting, you can add these to running tickets (as long as they are booked in the correct month it is correct).
  During the hour logging you can indicate in the comment it concerned a meeting or so.
  Specifically for consultants it is important the total hours in Jira correspond to the hours declared, these will be compared to the sign off hour sheet.
  We do not consider time registration limited to consultants only. It is meant for the whole Business Applications train.
  
• Version manager Naming convention to create versions:  application-major.minor.patch 
• Xray Test Management tool (app)

...