...

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.

...

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

for then JIRA can provide easy searching and automated reporting.

...

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

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.

...

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

1) Clearly state your goal: why does it have value to do what you propose?

2) Clearly define how you will measure whether that goal has been reached.

In Agile, this is done by writing a User Story and Acceptance Criteria. Your Scrum Master can help you summarise your needs as such:

User Story

As a <position <role of benefitter>the one benefitting>

I want to be able to <software function>feature>

So that <business goal>

Acceptance Criteria

...

When <user action>

Then <system response>

Image Removed

4. Sprinting or Continuous Flow

...