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

GreenHopper glossary


To get started with GreenHopper, let us first get familiar with common GreenHopper terminology, which we will also be using further in this book:

  • Backlog consists of a list of items for a product like feature, enhancements, bugs, support tickets, and so on. It can be product backlog or Sprint backlog.

  • Scrum is an Agile development methodology to deliver in an iterative way in fixed amount of time.

  • Sprint is an iteration in Scrum to deliver a product functionality in a time box of nearly a month or less.

  • Product backlog is a list of requirement items for a product such as features, bugs, and so on.

  • Sprint backlog is a list of items from product backlog picked up to deliver in a Sprint.

  • Epic is a large functionality for the product which can further be divided into user stories to be picked up in several Sprints.

  • Story is a conversation requirement for a part of the functionality which can be independently delivered and tested in a Sprint.

  • Task is a technical task or subtask for a Story to be done or performed by the team members and developers to deliver a user Story.

  • Story point is a number given to a Story to decide its relative complexity.

  • Burndown chart is a chart to display actual and estimated amount of work, in Story points, hours or business value points over time in a particular Sprint.

  • Velocity is the measurement of work either in Story points, custom business value, or hours that can be delivered by a team in a Sprint.

  • Kanban is a system to reduce waste to deliver business value by controlling and limiting the work in progress.

  • Cycle time is the time taken by an issue to change status in a flow, the time taken from work started until work finished on an issue.

  • Filter is a query with conditions to restrict the number of issues displayed on the screen.

  • Quick filters are configurable filters which can be stored and displayed on board to quickly filter the displayed results.

  • Swimlane is a way of grouping and categorizing lists of issues to be displayed on the task board in horizontal bands.