What's New In GreenHopper 6.1
Crush the Product Backlog Like David vs Goliath
Sometimes a team may feel like they have an insurmountable challenge ahead - 'how do we tackle this huge pile of work?!'
Make the team feel in control of the product backlog by grooming the backlog and putting some structure in place. Break a large problem down into manageable chunks, and beat Goliath.
View the full release notes »
Own GreenHopper OnDemand?
You've already been upgraded!
When is the battle won?
The team can be confident they have conquered that once insurmountable challenge once they have completed all of the stories linked to an epic.
Product owners know how many outstanding epics remain to be completed and how much work is present in each. Of course, if you have delivered sufficient customer value there is no need to perservere, simply close the epic as complete and resolve the stories as unneeded.
An Epic tale has many Stories
A team can now use Epics to cover large areas of functionality and they can break the Epic in to a number of stories. These stories can then be completed over the course of one, two, or more, sprints.
Arrange stories from an epic into future sprints to identify how long it may take the team to complete the whole epic. Each story is always linked back to its epic so you never lose track of the work yet to be completed.
Groom a Balanced Backlog
Group stories on the backlog that are related by functionality, personas or customers into epics. Build a sprint backlog using stories from a combination of epics, or focus all the team's energy on one epic to complete it faster.
This enables the product owner and team to quickly scan a sprint backlog and see which epics they are focusing their energy on, and adjust if needed.
Auto-Refresh As You Work
Distributed teams will forever be on the same page with GreenHopper 6.1. The team board now automatically updates itself when there are changes to be shown.
For instance, Bob moves a story from In Progress to Done on his computer and Sally sees this change on her own computer a million miles away, all without a reload.