| 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
MoSCoW prioritization
MoSCoW prioritization is a prioritization technique commonly used in DSDM. Daily-Scrum supports this throughout the system
MoSCoW was invented by Dai Clegg, Oracle UK consulting, used in the CASE Method Fast-Track, in the early nineties and has primarily been used as prioritization technique in the Agile framework DSDM (Dynamic Systems Development Method).
Normally, the first that slips out of customers’ lips is that all requirements are equally important – and, has top priority. If you try convincing the customer to prioritize in high, medium and low importance, most of the requirements will still be placed in the high priority lot. MoSCoW changes the way of thinking in terms of prioritizing.
Even though Daily-Scrum supports individual prioritization, it may help to prioritize top-down using MoSCoW before prioritizing individually. It will probably speed up the prioritization process. With Daily-Scrum comes described possible approaches for using MoSCoW prioritization which may or may not differ from the originally defined mindset.
Below is describes how MoSCoW is used in DSDM
| Priority | Description |
| Must have | The requirement is essential, key stakeholder needs will not be satisfied if this requirement is not delivered and the timebox will be considered to have failed. MUST can be considered a backronum from Minimum Usable SubseT |
| Should have | This is an important requirement but if it is not delivered within the current timebox, there is an acceptable workaround until it is delivered during a subsequent timebox |
| Could have | This is a nice to have requirement; we have estimated that it is possible to deliver this in the given time but will be one of the requirements de-scoped if we have underestimated |
| Won't have | The full name of this category is ‘Would like to have but Won’t Have during this timebox’; requirements in this category will not be delivered within the timebox that the prioritisation applies to |
This feature is included in both community and enterprise editions.