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


Based on industry survey, the majority of Agile practitioners practice either Scrum, a combination of Scrum and XP, or a hybrid nature of Scrum to match team requirements. Scrum is a time-boxed iterative and incremental framework for Agile development process. It consists of teams, roles, events, artifacts, and rules. Let us understand each role and common artifacts in brief first.

Scrum team

The typical roles in a Scrum team are:

  • Product owner: A product owner manages the product backlog in a prioritized form to deliver the best business value, thus grooming backlog items and helping teams with requirements and clarifications.

  • Development team: A development team consists of self-organizing cross functional individuals (developers) working as team, who do the work in increments to deliver potentially shippable products.

  • Scrum master: A Scrum master runs the Scrum team to make sure that Scrum theory, practices, and rules are implemented, and it works closely with the product owner, the development team, and the organization too.

Based on hybrid Scrum process, different teams also have dedicated roles for Architect and Project Manager in the team to meet specific team requirements.

Scrum events

The main Scrum events are:

  • Sprint: A time-boxed period of nearly one month or less to deliver potentially shippable product increment based on prioritized backlog items committed by the team.

  • Sprint planning meeting: In this, the team commits on what can be delivered from prioritized backlog items and how it will be achieved.

  • Daily Scrum: A time-boxed daily stand-up meeting in which each team member explains what has been achieved since last meeting, what will be done before next meeting, and impediments, if any.

  • Sprint review: In this, the team demonstrates the Sprint work and gathers feedback. It is a bi-directional communication platform for the team and stakeholders on functionality delivered in a Sprint.

  • Sprint retrospective: An opportunity for the team to introspect what went well, what needs improvement, and action items for the selected improvements.

Depending on the nature of hybrid Scrum process and team dynamics, the variations of the Scrum events, like local daily Scrum and distributed daily Scrum, are also used by various teams. Similarly, the planning and estimations process events are executed that matches best to the Scrum team requirements.

Scrum artifacts

The common Scrum artifacts are:

  • Product backlog: AN ordered list of requirements that is required in the product. It can be anything like requirements, features, enhancements, bugs, and so on.

  • Sprint backlog: This consists of selected and ranked product backlog items planned to be delivered in a Sprint.

  • Increment: Consists of delivered product backlog items in all earlier Sprints/Releases, and are very much usable as part of existing potentially shippable product.