Pricing Overview
10 users$10/mo |
15 users$25/mo |
25 users$50/mo |
50 users$100/mo |
100 users$150/mo |
500 users$250/mo |
2,000 users$500/mo |
10 users$10 Starter |
25 users$600 |
50 users$1,100 |
100 users$2,000 |
101+ users$4,000 |
The GreenHopper Feature Tour
Principles of Scrum
Scrum is an Agile methodology in which teams plan work in blocks of time called sprints.
The team makes a commitment to deliver working software to the customer at the end of the sprint.
Backlog Grooming
In a backlog grooming session the team will estimate stories in preparation for the sprint planning session.
Stories may also be broken down into tasks or have acceptance criteria added so that the team is clear about the Definition of Done.
Sprint Planning
The Product Owner will take a subset from the top of the product backlog and turn it into the sprint backlog using the sprint marker.
All stories above the sprint marker will be discussed in the sprint planning session and the issues above the marker become the teams commitment when the sprint is started.
Visualise Sprint Progress
Story swimlanes allow the team to see progress on individual stories.
When the final technical task reaches the Done column the Product Owner is prompted to accept and resolve the story.
Burndown Chart
The team tracks their progress towards their sprint commitment using the burndown chart.
If the scope of the sprint has changed, by for instance adding another story to the sprint, this will be reflected on the chart.
Sprint Retrospectives
Start the sprint retrospective discussion using the Sprint Report. The report details the original commitment, changes in scope and what the team delivered.
Scrum + Kanban = Scrumban
Apply basic principles of Kanban to your existing Scrum process and improve the flow of stories across the board.
Use column constraints based upon story points or issue counts to avoid bottlenecks and highlight spare capacity.
