Table of Contents

1. Introduction

JIRA can bring a new level of transparency to an Agile team, opening up the backlog and work in process beyond the team’s location.

...

for then JIRA can provide easy searching and automated reporting.

2. Jira setup - Portfolio management

The Project in JIRA is much larger than an Information Systems ‘project’ – it is the full backlog for a product that your team (and maybe others) manages.

...

Each team will have their own team board (either Scrum or Kanban), with their chosen team name in the title. Thanks to the "Yamaha Team" field only stories assigned to this team are visible on their own board.

3. Data maturity - what & why?

When wishing to change the status quo, it is vital to do two things:

...

When <user action>

Then <system response>

4. Sprinting or Continuous Flow

4.1 In Scrum

• Creating a sprint
• Setting a sprint goal
• Choosing stories to fulfil that goal
• Starting the sprint

Work for 2 weeks to complete this selection of work. Then review the work meets the acceptance criteria, and plan when to release the results.

4.2 In Kanban

• Choose a limited selection of work (one item per person)
• Do not take up new work until the old work is completed
• If an item gets blocked, the entire team works together to resolve the block before continuing work

Work to provide continuous flow: processing work items through the required workflow (development, peer review, testing, uat, release) as soon and smoothly as possible.

5. Inspect & adapt

Releases – manage your versions

...

–Export to file

–Bulk change

6. Recommended learning

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

...