Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Agile Project Management with GreenHopper 6 Blueprints

You're reading from   Agile Project Management with GreenHopper 6 Blueprints Written by an Agile enthusiast, this comprehensive guide to GreenHopper will help you track and manage your projects in a way that achieves the best value for your team. Excellent reading for everybody from stakeholders to scrum masters.

Arrow left icon
Product type Paperback
Published in Aug 2013
Publisher Packt
ISBN-13 9781849699730
Length 140 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jaibeer Malik Jaibeer Malik
Author Profile Icon Jaibeer Malik
Jaibeer Malik
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Agile Project Management with GreenHopper 6 Blueprints
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. Getting Started with GreenHopper FREE CHAPTER 2. Planning Your Sprints with GreenHopper 3. Estimating and Time Tracking 4. Using the Work Board to Update Issues 5. Using Quick Filters and Highlighting Issues 6. Understanding the Burndown Chart 7. Ending a Sprint 8. Project Reporting Using Charts 9. Managing Kanban Team with GreenHopper Continuous Improvement 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image