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)

To get the most out of this book

There aren't a lot of prerequisites for this book; just a couple of things that I thought would be helpful. First, you should have a basic knowledge of Scrum. We'll reference Scrum a fair amount as we're running an Agile project in JIRA, and I'll give you some helpful specifics. Second, it is nice to have at least one team of people that are looking to work together, because that's what JIRA is really great for: having a team of people work together instead of just one person working on something. Although you can use JIRA alone, having a team that you can apply these concepts to once you've learned them will be really powerful.

You will need to be familiar with the basics of JIRA, from both the end-user and administrator perspectives. Experience with workflows, custom fields, and other administrative JIRA functions will be useful.

Download the color images

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Let's create another Sprint. We'll call this one FP1 Sprint 1 and include This is my first Sprint as the Sprint goal."

Bold: Indicates a new term, an important word, or words that you see on screen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "If we go back to our Backlog in the upper right corner, we can see that we have our Board settings, so we'll click that, and then, under our SETTINGS, we've got Estimation."

Warnings or important notes appear like this.

Tips and tricks appear like this.