Jira configuration considerations

Owned by Jacques.DuToit (Unlicensed)
Last updated: May 31, 2023
2 min read

 

Overview

All of the work for our program is currently managed inside two Jira projects.

Our work breakdown structure is represented in the picture (left). It is important to note that we endeavour to always align work to the initiative that it supports. Epics and “story level” items are represented on team boards, whereas program epics and initiatives are managed on program boards.

Team boards

The physical backlog is split into multiple “team backlogs” using board filters; based on the team field.

Spatial example: project = NSSP AND Team = “NSP-Spatial” AND ….

It is key that we do not pull work from multiple Jira projects onto the same team boards - this will break the roadmap view and also create inconsistency in sprint management.

The CX-Design team will work from a Kanban board. Please do not pull their work into any team sprints.

Creating work in Jira

The virtualisation and clear delineation of teams depend on the following:

Project:

Ensure that all work items are created in the right project - as depicted in the picture above. If a mistake is made then use the “move” function in Jira to migrate the item to the right project. Bulk amendments can also be made using this function.

Team:

When creating Jira items, please select the appropriate team from the drop-down menu (see right) to ensure the work is visible in the team’s Scrum board.

Advanced Roadmap:

https://nhvr.atlassian.net/jira/plans/1/scenarios/5/timeline

When creating items in Jira Advanced Roadmap the same can be achieved, as shown in picture below. Ensure the correct project is selected, correct entity type is selected and then update the team field.