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

Push model versus Pull model

The old methodology usually follows the push model where the work is pushed or assigned to a team member or a team. Usually the team leader or manager assigns tasks to different team members as shown in the following diagram:

There are multiple issues with the push model, such as a lot of waste in the process, individual backlog burdens, no team collaboration, no clear visibility in bottlenecks in the system, and work may get stuck at different levels in the system.

A typical pull model looks as shown in the following diagram:

Some of the pull system benefits are:

  • It supports the continuous flow of work

  • Work is done as a team

  • There is a clear indication of state of work

  • Work in progress is limited for each status

  • There is a lesser burden on individual backlog

  • It allows better planning and prioritization of work

  • It allows improved continuous delivery

Kanban system implements the pull model for continuous delivery by eliminating the waste and focusing on continuous improvement...