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

Agile Project Reporting


In the traditional project management, organizations spend big amounts on project reporting and have dedicated people to monitor them. The efforts spent in accommodating and maintaining the fine-grained details of tasks to have minimum risk on the success of the project have lead to the rigorous nature of the project reporting.

In Agile, the concept of just enough or barely sufficient documentation also applies to the project reporting part. Different Agile methodologies may have different standards and artifacts to report the status of an Agile project. In Scrum, commonly we need reporting for following things:

  • Product backlog describes how the whole product backlog is progressing across Sprints, how much backlog has been completed, and how much backlog is still remaining to be completed. Looking at the remaining and completed backlog items, we know how many feature requirements are still to be completed by the team and the road map to complete the same. To map to...

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