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.

The platform can be used for Scrum or Kanban, but ultimately it’s just a tool: it’s only as good as the data we put in.

If we want to use JIRA, we should:

• populate it with clearly written stories,
• maintain it daily, sharing our progress and refinement.

for then JIRA can provide easy searching and automated reporting.

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.

YME management has decided that we have three Information Systems release trains – Consumer Processes, Business Processes, and Enablement. 

Initially, we will have one single JIRA Project for this entire portfolio, which will allow us to easily assign stories between the development teams.

Each team will have their own 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.

Data maturity - what & why?

Sprinting or Continuous Flow

Inspect & adapt

Recommended learning

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