Child pages
  • Jira in Scrum sprints
Skip to end of metadata
Go to start of metadata

How can the Jira task management system be used in Scrum teams to optimally support your work?

In this article, we will explain how Jira can be used over the course of a sprint.

Sprint preparations

The product owner manages his product backlog in Jira. This is where he records and prioritizes his user stories and error messages. The user stories and their acceptance criteria are shown in Jira tickets.

Corresponding wireframes, if present, are stored in the project wiki and are often realized using draw.io, a company wiki plugin for diagrams, processes and organization charts.

The Jira ticket is linked to the corresponding wiki document. This is where the wireframe is stored in addition to other information, such as workflow descriptions for the entire process that the user story is supposed to contribute to.

Using the InstaPrinta plugin, the product owner prints out the stories and error messages he wants to discuss with the team during the sprint planning meeting. After determining the sprint objective and the required activities for achieving the sprint objective, Jira tickets are created for all activities. These Jira tickets are then printed out using the Agile Scrum Cards plugin and put on the team’s task board.


During the sprint

Over the course of the sprint, the team works on completing the tasks. The product owner and the team discuss how precisely tasks need to be completed. These discussions are documented in the corresponding Jira ticket so they are always visible to all team members and can be used later for the test approvals and review meeting. Any layouts that still need to be created to complete the tasks are stored in the wiki where the customer can access and approve them.

Team members log their work hours daily using the Universal TimeTracker by //SEIBERT/MEDIA and simultaneously log their hours on the Jira tickets they are working on.

During the daily scrum, team members update the analog task board in the team office. After the daily meeting, the employees close the completed Jira tickets. Jira updates the burn-down chart automatically. This makes it clear which activities, story points and/or hours in the sprint are still remaining.

At the end of the sprint

Based on the acceptance criteria in the Jira tickets, the layouts in the Confluence wiki and the definition of done, stories are approved at the end of the sprint. The test results are stored in the Jira tickets.

With the Jira Capture (formerly Bonfire) plugin, conducting test sessions is a breeze. The browser plugin lets you easily take screenshots and screencasts with comments and create Jira tickets.

We are happy to assist you

We are happy to consult with you individually and introduce you to Jira and/or Bonfire in a workshop or desktop sharing session. Feel free to contact us with no obligation. And by the way, //SEIBERT/MEDIA is an official Atlassian distribution partner and offers a 10% discount on all licenses in the form of consultation services.

 

Siehe diese Seite auf Deutsch

  • No labels