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

Summary


In this chapter, we created the team Agile board to get it started with Scrum way of working. We started the Agile team with a new Jira project and also with the existing project.

The board displayed the backlog items which the team will be working on. The team created different types of backlog items on the Plan mode. We created Epic and Story issues as part of the product backlog. We also covered creation of technical task items as part of Sprint planning meeting.

We also moved the items in the Plan mode to rank the items based on business prioritization. We will be covering the backlog items estimations in detail in the next chapter, where the team will learn to assign complexity points to each backlog item as part of backlog grooming and estimating.

Using Plan mode, the team created Sprint and committed on backlog items to be completed in a Sprint. The team started a Sprint and set the Sprint timelines to continue the Sprint. In later chapters, we will cover how to track a Sprint...