| 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
Sprint/iteration planning
Measure and track capacity when planning your iterations, whether there is one or many teams.
Daily-Scrum will help you in planning your sprints. There can be multiple teams planning together. The team will select the item of highest priority, and if the product backlog has been planned in releases will allow the team to select items from those releases.
Daily-Scrum keeps track on whether a team is under- or over allocated, taking into consideration public holidays and planned absence. The selected backlog can be re-prioritized together with the Product Owner independently of the Product backlog. After selecting from the backlog what to be worked on in the sprint, the team can start planning tasks for each deliverable, stating estimates and optionally assign resources for each task. During this process, Daily-Scrum will keep track on whether the team is under/over allocated, and allow the team to revoke or add deliverables as needed.
This feature is included in both community and enterprise editions.