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
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Completing a Sprint


The team works hard during the course of the Sprint to complete the Sprint backlog items. The Burndown chart shows the regular progress of the team and how the backlog burns over the course of the Sprint. At the end of the Sprint, the team needs to get ready for the Sprint review or demo. And finally, the team completes the Sprint backlog.

While working on the backlog items, the team finishes the technical tasks created during the Sprint. Multiple team members work on different technical tasks for a Story. During the course of the Sprint, we also need to mark the Story as completed or done. While working on the task board in GreenHopper, if you are completing the last technical task for a Story, it allows you to change status for the parent task or Story also.

To change the status of a Story during the course of the Sprint once it is done (when you mark the last technical task as done), you can also mark the Story as done.

As shown in the preceding screenshot, you can choose...