...
Initially, we will have one single JIRA Project for this entire portfolio, which will allow us to assign stories between the development teams easily.
Each Outside SD, 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, which contains an entry for each team, only stories owned by this team are visible on their own board.
...
When wishing to change the status quo, it is vital to do two things:
...
It's not easy to work though blocks sometimes, but remember that if you explain to a requester why something is not possible and they change or cancel their request, that resolves the block as well.
Releases – manage your versions
Reports – only as good as the data we put in
–for Scrum
–for Kanban
–Dashboards
Either way of working needs to at certain points deploy software, in a production release.
In Jira, this is administered by assigning a 'fix/version, which bundles together everything that goes live on a specific date. Release managers use the fix/version to understand what needs to be prepared for deployment together.
Two things are important in this:
The first helps everyone understand which system the release is for, and which period it took place in; while the second clears deployed items from the 'done' column of Kanban boards.
Using the tool Jira consistently, means that we obtain transparency of our process and progress. This allows our team to Inspect how we are doing, and Adapt in order to grow together.
Searching – across or within projects & teams
...
–Export to file
–Bulk change
– only as good as the data we put in
–for Scrum
–for Kanban
If there is any data you wish to check periodically, it is possible to collect both filter queries and visual representations of Jira data onto a single page, called a Dashboard.
Jira beginner's guide to Agile (free, self-paced, 90 minutes, certification option)
...