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

Agile Project Reporting

In the traditional project management, organizations spend big amounts on project reporting and have dedicated people to monitor them. The efforts spent in accommodating and maintaining the fine-grained details of tasks to have minimum risk on the success of the project have lead to the rigorous nature of the project reporting.

In Agile, the concept of just enough or barely sufficient documentation also applies to the project reporting part. Different Agile methodologies may have different standards and artifacts to report the status of an Agile project. In Scrum, commonly we need reporting for following things:

  • Product backlog describes how the whole product backlog is progressing across Sprints, how much backlog has been completed, and how much backlog is still remaining to be completed. Looking at the remaining and completed backlog items, we know how many feature requirements are still to be completed by the team and the road map to complete the same. To map to...