So you are now using Kanban and therefore utilising the 'Release' feature of Jira.
First things first, What is Kanban?
Kanban is a lean method to manage and improve work across human systems. This approach aims to manage work by balancing demands with available capacity, and by improving the handling of system-level bottlenecks - (thanks google!).
And how do we structure it in Jira?
For each release, we shall have a relevant version i.e. <Name of Product>_<Product Version>, this needs to have start/release dates and a relevant description.
For each release scope, we shall have an epic. For example in your <Name of Product>_<Product Version> plan you should have various components/cycles that need to be tested. For example, we have sustaining bug fixes, confidence testing and exploratory testing, so an epic will be created for each of those points of scope. This means that we'll only be picking up one epic at a time, so until one epic has been completed, another cannot be picked up.
Each ticket created within a release should have a fix version (i.e. the product version) and a link to the epic it relates to, for example if you are creating a ticket for exploratory testing, link the ticket to the exploratory testing epic.
Exploratory tickets will follow the same structure but will have an additional field for 'component' so that we can track the coverage of testing,When testing is complete, all tickets should be moved to a status of 'Done', until the stand up the following day, when the status will be changed to 'Closed'.
This is to ensure that we can track what has been done the previous day, any issues that needed to be resolved and use this status as a placeholder for discussions.
Team members should endeavor to pick only one task at a time to avoid context switching and a decrease in quality level.
How to structure a project/product release in Jira once your test plan has been completed:
1) Create a Release with a relevant name in your Jira project i.e.<Name of Product>_<Product Version> for example "Hannah 2.0" . Ensure this has a start and release date, along with a description of this release.
2) Create epics in your Kanban backlog for each relevant scope outlined in your release form.
3) Create a version that relates to your product release version i.e. 'Hannah 2.0'.
4) When adding in tickets for each of your scope points, you can then assign an epic and a fix version to the newly created tickets.
So here you will see that two tickets have been created for 2 different scopes for the Hannah 2.0 release.
Exploratory Testing Tickets
For exploratory testing tickets, an epic will be created and tasks will be created under that epic in the same way the rest of the tickets are structured.
However, in these tasks we shall be assigning components i.e Save, Delete, Modify etc.
This allows us to pull out reports where we can see what coverage Exploratory testing has given each component. Eventually we shall build a repository for components for each products.
How exploratory tickets shall look with components tagged:
Comments