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

Working with control chart


The control chart is a measurement criterion to determine if the process/data under analysis will produce the desired result in future. By examining the data over a period of time, we can analyze if it is running at a sustainable pace or not. By looking at huge variations in the data, we will be able to decide if we need to introspect the process or flow, or not.

To access the control chart, go to your team board, click on the Report link and select Control Chart.

The preceding screenshot shows a sample control chart for an Agile team. The x axis represents the time (number of days) for an issue to be in single workflow state, and the y axis represents the time frame.

The statistical analysis helps us to introspect the process from a planning perspective. The aggregate mean and standard deviation of the time helps us to focus on bottlenecks and see if any action is required or not.

The cycle time for an issue represents how much time it spends in a particular state...