1. Jira basics

Never worked with Jira before? No problem. In this chapter we cover some of the basics, so you know how to get started.

Projects

Data inside Jira is organised in 'projects'. A project is a collection of items that relate to the same topic.

...

• 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.
• Yamaha Portfolio Board (YPM) 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 projects capture work for teams that have not yet joined the Agile Transformation.

Team board

The data within projects can be filtered and visualised per team, in specific team boards. You can see a team board as the coloured glasses through which we look at project data - we can customise a board to show the exact data you want to see.

There are two flavours available: Scrum boards and Kanban boards.

Scrum board

In the Agile Scrum framework, focus lies on short iterations of work: planning what can be done within (at YME) 2 weeks of time. 

• As such, we see an active sprint with items in it (centre screen).
• These items are organised into larger topics called Epics (left screen list, but also the coloured labels on centre screen items).
• When one item is clicked, the details are shown (right screen sidebar).

Kanban board

In the Agile Kanban framework, focus lies on limiting multi-tasking: by choosing fewer items to start, it's possible to complete each more quickly.

• Here we see no epic list on the left.
• In the centre we see all items progress through a workflow, with columns turning red if there are too many items in it.
• When clicking one of the item cards, the details are shown on the right hand side.

Issues

At the top of both Scrum and Kanban screens we see a big red "Create" button, which allows us to add new items. When doing so, the correct project and issue-type needs to be chosen.

...

The easiest way to look at issues is on a team board, but it's also possible to Search or use Dashboards. 

Search

Sometimes you may want to look for data that is not shown on a team board. For example, tickets that are done no longer show up for the team, allowing them to focus on remaining work. 

...

You can choose which details are shown about the results, by choosing the Columns that should be displayed.

Dashboard

If you are not part of a development team, but wish to understand more about how tickets are processed or other processes, it's possible to build a custom Dashboard that shows you all you require.

...

If you'd like to understand trends in Jira, but don't know how to build your own dashboard, feel free to contact the Jira COP so we can help you build what you need. (In the future we'll write a manual on how to create your own)

Recommended learning

Jira fundamentals (free, self-paced, 90 minutes, certification option)

Jira beginner's guide to Agile (free, self-paced, 90 minutes, certification option)

2. Jira SD for operational support

Customer portal

Issuetypes

Workflows

Field configuration

SD Classification field

New field SD Classification has been created. This field replaces the current EPIC’s used in Servicedesk.

Problem with the current epics is that these are having to many linked issues and as result these cannot being opened anymore or transitioned through the workflow.
The old values will be set for all tickets to the new field and when done below epics will be closed.
! This change has effect on (Dashboard) filters and boards. Please check your personal filters and change the selection of the epics to the new field SD Classification value.

3. Jira YPM for portfolio planning

Issuetypes

Workflows

Field configuration

Yamaha Team(s) field, for Programme and Project

Upon request of PMO team a multi select field Yamaha team(s) for Issue type  Programme and Project has been created.
This field replaces the old Team Yamaha field for these two Issues types. If assistance for a bulk update is required, please contact a Jira Administrator.

...

Team(s) can be selected via a drop down menu and pressing CTRL to select multiple teams.
When no values are set, select the edit button to add field values.

Responsible Architect field, for Programme and Project

Upon request of Architect Working Group A User Picker field for Responsible Architect has been setup.
This field will be used by the Architect Working Group  to select the Responsible Architect for  Programme and Project.

When no value is set, select the edit button.


This  field works similar as the Assignee field.  When you start typing, suggestions will be made of matching users. Select the user to confirm your choice.

When set it will appear in the people section on the right hand side:

4. Jira YIS for development

Issuetypes

Workflows

Field configuration

Yamaha Teams

Fix/version

When closing an item, you are often prompted to fill in the mandatory field for Fix/Version.

Jsox compliance

5. Smart use of YIS

Quick keys

Quick filters

Card colours

DOR

PO boards