Book Image

Hands-On Agile Software Development with JIRA

By : David Harned
Book Image

Hands-On Agile Software Development with JIRA

By: David Harned

Overview of this book

As teams scale in size, project management can get very complicated. One of the best tools to deal with this kind of problem is JIRA. This book will start by organizing your project requirements and the principles of Agile development to get you started. You will then be introduced to set up a JIRA account and the JIRA ecosystem to help you implement a dashboard for your team's work and issues. You will learn how to manage any issues and bugs that might emerge in the development stage. Going ahead, the book will help you build reports and use them to plan the releases based on the study of the reports. Towards the end, you will come across working with the gathered data and create a dashboard that helps you track the project's development.
Table of Contents (8 chapters)

Sprint reports

In this section, we'll discuss the sprint report. We'll cover what it is, and we'll show how to read it. In the sprint report, there's a summary of the sprint iteration. It shows us the burndown, the work that was completed, the work that wasn't completed, and any work that was added and removed during the iteration.

Let's take a look at JIRA and get more information about a Sprint Report. You will need to have completed a sprint to have this data. We did run a one-day sprint in the SP project, so we have something to look at. First, click on Reports (on the left), and take a look at our Sprint Report:

View of the Sprint Report

Keep in mind that our burndown is not going to be beautiful, because this was a one-day sprint. Normally, the burndown would be more appropriate, based on the iteration length of our sprint. Let's pay closer...