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 Kanban
Kanban is a catalyst for change through small, incremental improvements to your existing process – be it Scrum or otherwise.
Rooted in Lean manufacturing, Kanban is a signalling system that can be effectively applied to software development, DevOps, IT Operations, and many other processes.
Visualize Your Workflow
Map columns on the board to the steps of your existing workflow. Add or remove columns as the process evolves over time.
Kanban teams will often map a longer value stream on their board and add columns for wait states, for instance "Waiting on Customer".
Horizontal Swimlanes
Separate issues on your board using swimlanes to help map out your value stream by class of service, for instance "Expedite".
Swimlanes may be configured using the JIRA Query Language, giving the team complete control over the issue selection criteria.
Limit Work In Progress
Kanban teams use a pull system to optimize flow from right to left across the board. The team pulls from the left when they have available capacity.
Set minimum column constraints to identify spare capacity (yellow) and maximum column constraints to identify bottlenecks (red).
Measure Cycle Time
Cycle time is the time an issue spends in progress. Lead time is the total time from when an issue was raised to when it was completed.
Having stories of the same size helps teams obtain consistency in the cycle time, and this can in turn provide predictability for customers.
Analyze Trends
Monitor current trends and analyze past progress with the cumulative flow diagram. See where work is building up and bottlenecks occur.
