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


In this chapter, we covered how to mark a Sprint as completed. We covered how to handle the unfinished issues in a Sprint. We also learned to mark issues as done for all tasks already completed, and how to move back the unfinished backlog items to backlog.

We learned to generate the Sprint report on completion of a Sprint. The generated Sprint report helped us to understand team's work Burndown chart for the just ended Sprint in comparison to earlier Sprints. We can always have a complete list of items completed in a Sprint from Sprint report.

We also covered how to end an Epic which automatically generates the Epic report for us. The generated Epic report displays how a particular functionality has been completed over a span of possibly multiple Sprints. In the next chapter, we will be covering generating Epic Report in detail.

In the upcoming chapters, we will be covering how to generate Agile project reports like Velocity report, Control chart, Cumulative flow diagram, and so on...