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

Scope management for Sprint

In ideal cases, we assume that the scope for a Sprint is closed when we start a Sprint. The team commits at the start of a Sprint that they will be delivering in a Sprint. But, in many of the practical scenarios that does not work well.

Based on new insights and priority changes, the product owner asks to change a Story during the Sprint. Usually from the team side, if work on a particular Story is not started and a new Story is of equal size, then team agrees to switch the Story during the Sprint. Another scenario can be that you finish your work earlier and the team can pick some Story from the backlog. All the scope changes are reflected in the Burndown chart in terms of addition or removal of work from the Sprint backlog.

To remove a Story from a Sprint, as shown in the following screenshot, click on the Story issue key and the Story details panel will be displayed. Go to Actions and select Remove from Sprint. This option only appears in the Action menu for...