Book Image

Agile Project Management with GreenHopper 6 Blueprints

By : Jaibeer Malik
Book Image

Agile Project Management with GreenHopper 6 Blueprints

By: Jaibeer Malik

Overview of this book

Agile methodologies like Scrum focus on customer values in an incremental way. Regular planning, tracking, reporting, and improving can become equally challenging from a project management perspective. GreenHopper is a tooling support for JIRA that offers easy adoption of agile practices through rich interfaces for effective team collaboration and project management. Agile Project Management with GreenHopper 6 Blueprints is a step-by-step guide that teaches you how to manage agile projects using the GreenHopper tooling system. With easy adoption using pre-sets for Scrum & Kanban, the rich interface focuses on the work at hand, increasing team productivity. Executing sprints, tracking sprints, and reporting on agile projects has never been so easy. The integration with different development environments helps teams to focus on collaboration, communication, and continuous improvement. This book covers agile project management concepts using GreenHopper. You will learn about backlog management for your agile team, how to create projects and boards for your agile team, and how to create new backlog items, prioritize items, estimate backlog items, create sprints, and update technical task status and report on the same. You will learn everything you need to know about managing an agile project using GreenHopper and how to achieve the best value for your team.
Table of Contents (17 chapters)
Agile Project Management with GreenHopper 6 Blueprints
About the Author
About the Reviewer

Understanding the task board

Before we start using a task board, let's understand the uses and importance of a task board and what makes a great task board.

A task board represents the visual information of work in progress. It shows how much work still needs to be done, how much work is in progress, and how much work has already been completed. Every Scrum team day starts with the daily standup status in front of the task board, covering basic questions of how much work each team member has finished since the last meeting, and what work will be in progress till the next meeting, and if there are any impediments.

To answer the question of what makes a task board a great one, we need to understand a typical day in a developer's life, the team dynamics, and a bit of high level view from project a and organization perspective. Some of the requirements from a task board which differs from one to another are:

  • Alignment to the development process

  • Prioritized backlog of Story and technical tasks

  • Must...