| 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
Velocity tracking/charts
Track velocity - follow it from one sprint to the next throughout the project. Track each teams velocity.
Velocity is the number of units (story points) a team can deliver in a sprint.
Velocity is used to determine the amount of work a team can take on in a future sprint, as such, velocity is used during sprint planning when the team is selecting items from the product backlog. If the team has not yet started on the project, the team will not have any velocity. The system allow you to define a velocity if it is not already calculated.
When a sprint is closed the final velocity will be calculated and accounted the sprint, team and the project. Since number of days in sprints may vary, a velocity factor is stored on team members. This velocity factor will be used as a basis for forcasting a teams velocity in the next sprint.
The velocity is also used for release planning and forcasting milestones in the project.
See also Burndown charts, Release forecasting
This feature is included in both community and enterprise editions.