Table of Contents

1. Introduction

Introduction

Agile is a framework for a way of working in which: 

• experts are empowered, to take ownership and create high-quality solutions,
• the gap between IT and Business is bridged, through input and validation by a business-representing Product Owner,
• transparency, alignment and early escalation (asking for help) are key,
• short cycles lead to adapting and improving plans,
• and we experiment with process improvements to gain efficiency.

Jira 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 JIRAJira, we should:

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

for then JIRA Jira can provide easy searching and automated reporting.

...

Jira setup - Portfolio management

The Project in JIRA Jira is much larger than an Information Systems ‘project’ – it is the full backlog for a product that your a 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 there will have be one single JIRA Jira Project for this entire portfolio, which will allow us to assign stories between the development teams easily.

Outside SDServicedesk, 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.

...

Value & measurement - why & how?

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

...

In Agile, this is the responsibility of the Product Owner, though others (like Business Analyst) can support.

Image Modified

It is done by writing a "User Story" that clarifies the why and "Acceptance Criteria" that clarifies the how.

...

Then <system response>

And remember:

Image Modified

...

A quick note regarding estimation:

• We estimate value in the Jira field "business value"
• We estimate complexity to develop in the Jira field "story points"

These estimations use a simplified Fibonacci range (0, 1, 2, 3, 5, 8, 13, 20, 40, 100).

The reason for this is that people are much better at estimating small numbers.

There is no real difference between a "48" and "49", because any estimate that large will include a large portion of uncertaintly. 

For this reason work with large estimates is broken down into smaller, workable pieces (that we can still test to validate a piece), and re-estimated.

A recommended tool/game for estimating together with a group is: https://planningpokeronline.com/

Sprinting or Continuous Flow

...

Scrum

We work in increments of two weeks, because it's easier to plan realistically when timelines are short:

...

Before starting a new sprint, we hold a retrospective - looking back at how people and processes behaved during the sprint, and how we can become more efficient and more happy together.

...

Kanban

Kanban has no limits on time, but on amount of work in process. By focussing focusing our efforts on a single task, we strive to move items to Done in short cycles.

...

If there is no limit on the amount of work in progress, or if those limitations are not honouredhonored, it is not Kanban but a simple to-do list.

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 or 'fix version/

...

s'

Either way of working needs to at certain points deploy software, in a production release.

In Jira, this is administered by assigning a 'fixFix Version/versions', 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:

1. We should use the naming convention when creating a new fix version/versions.
2. We should set status 'released' for release a fix version/version in s in Jira after the deployment is succesfulsuccessful.

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.

...

Inspect & adapt

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 gain higher efficiency, and grow together.

5.1 Reports

Each team board contains standard reports. –

• these are only as good as the data we put in

...

• for Scrum the Burndown Chart and Sprint Report are useful

...

• for Kanban the Cumulative Flow Diagram is useful

for higher level planning the Epic and Version report are useful, but we will need to grow into these reports yet at YME.

A Burndown Chart shows the progress during a sprint. The more the red line follows the grey line, the better:

A Sprint Report shows the results after a sprint. The fewer items have a * or are removed from sprint, the better:

A Cumulative Flow Diagram shows how WIP is limited and progress is made in Kanban. The slimmer the coloured colored line between backlog/resolved, the better:

5.2 Searching

There are multiple ways of finding data in Jira outside of a team board.

The easiest is using the top-right search box to find a specific issue. Simply type the number here and press enter:

Image Removed

It's good to know that it's also possible to:

– search across or within projects & teams

– use Basic or Advanced queries

– save search results as a filter

– Export search results to a file

– make Bulk Changes to search results

To learn how to do any of this, please read the Jira Training Basics - Search.

5.3 Dashboards

If there is any data you wish to check periodically, it is possible to collect filter queries and visual representations of Jira data onto a single page, called a Dashboard.

Image Removed

You can read more about using and creating Dashboards in Jira Training Basics - Dashboards.

6. Recommended learning

Recommended learning

• Agile Manifesto (free, self-paced 1 page)
• Scrum Guide (free, self-paced,  pdf 14 pages)
• Jira beginner's guide to Agile (free, self-paced, 90 minutes, certification option)
• Scrum Competencies on Scrum.org (free, self-paced, 30 minutes including sub-pages)
• Scrum Master Learning Path on Scrum.org (free, self-paced, 8 hours, certification can be bought)
• Scrum Master Practice Assessment on Scrum.org (free, 30 questions, 30 minutes, 85% pass rate)
• Product Owner Learning Path on Scrum.org (free, self-paced, 8 hours, certification can be bought)
• Product Owner Practice Assessment on Scrum.org (free, 30 questions, 30 minutes, 85% pass rate

...

• )