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
About the Author
About the Reviewer

Appendix A. Continuous Improvement

The traditional approach of capturing the improvements for the project execution used to be at the end of the project in order to improve the future projects. One of the core aspects of Agile is the idea of continuous improvement while you are currently working on the project.

The Agile way of improvements for lessons learned is a deliberate and frequent approach. It ensures that the team regularly considers adaptation and improvement which makes it part of their normal way of working. Some of the common forms of improvements are as follows:

  • Retrospective

  • Knowledge sharing

  • Process improvements

  • Wiki integration

  • Testing collaboration

  • Team communication

  • Continuous integration

  • Technical debt

  • Code reviews

  • Reporting and Dashboard

  • Notifications (Email/SMS)

  • IDE integration

  • Plugins