| Feature | Community edition | Enterprise edition | |
|---|---|---|---|
|
Users
|
Up to 10 | Unlimited | |
|
Project teams
|
Unlimited | Unlimited | |
|
Plan and track progress on all levels
|
 |
|
|
|
Supports stories/deliverables, possibly grouped into epics, quantified in story points and business value
|
 |
|
|
|
Measure and track capacity when planning your iterations, whether there is one or many teams.
|
 |
|
|
|
Plan and forecast releases and predict end of project
|
 |
|
|
|
A task-board/scrum-wall where changes are updated across clients at all times.
|
 |
|
|
|
Daily-Scrum delivers burndown charts on all levels, project, sprint and team. On personal level either burndown or burnup chart is used depending on how the project is configured.
|
 |
|
|
|
Track velocity - follow it from one sprint to the next throughout the project. Track each teams velocity.
|
 |
|
|
|
Daily-Scrum measures the value of each feature as they are completed
|
 |
|
|
|
Daily-Scrum can automatically prioritize your backlog based on your estimates, business value and MoSCoW
|
|
|
|
|
MoSCoW prioritization is a prioritization technique commonly used in DSDM. Daily-Scrum supports this throughout the system
|
|
|
|
|
Project and role based security
|
|
|
|
|
Daily-Scrum comes with a REST-ful API for integration with other systems
|
|
||
|
Saas (hosted online)
|
|
|
|
|
On site install*
|
|
||
|
Customer support
|
Online | Full | |
|
Subscription
|
Free 1st 2 months | USD 24/user/month | |
|
Perpetual
|
USD 352** / user |
*Additional consultant fee may apply. Please request price quote
** Plus annual support and maintenance fee
Unique prioritization mechanism
Daily-Scrum can automatically prioritize your backlog based on your estimates, business value and MoSCoW
In Daily-Scrum, there are two ways of prioritizing the backlog:
- Manual prioritization
- Automatic prioritization
Manual prioritization is done by dragging items up or down in the backlog.
Automatic prioritization is done by clicking the Re-prioritize button located above the backlog.
In a project without MoSCoW prioritization enabled the system will order the backlog so that the items with least estimates and highest business value are placed first.
In a project where MoSCoW is enabled, the system will use the same algorithm as above, but MoSCoW will take precedence, so that Must priorities are placed on top, followed by Should etc. Unprioritized items will have higher priority than Wont priorities.
After re-prioritizing, the backlog can of course be manually prioritized as you like.
This feature is included in both community and enterprise editions.