| 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
Product planning
Supports stories/deliverables, possibly grouped into epics, quantified in story points and business value
You plan the project by first collecting requirements (called deliverables in the system). The deliverables are placed in a product backlog for the project. In DSDM this is called the Prioritized Requirement List.
Each deliverable can be detailed by defining a user story, stating a business value and estimate the scope of work needed to complete the requirement. Once business value and estimates has been stated you can automatically prioritize the backlog based on the highest business value requiring least effort to be complete. Prioritization can also be done individually, and you may also set MoSCoW priorities on each deliverable to have even more control over the prioritization. It is also possible to define criteria per deliverable for acceptance.
Deliverables can also be commented on to provide more information on the requirements, progress status etc. All comments are traceable through out the project from different perspectives. If deliverables are considered huge they may be broken down into multiple deliverables by changing a deliverable into an epic.
This feature is included in both community and enterprise editions.