Scrum Item Breakdown (R6) – iceScrum

Obsolete iceScrum documention (R6#14+) This documentation applies only to old iceScrum R6. For new iceScrum v7, click here.

A product is divided into features, which are essential to users. iceScrum gathers features in the backlog and can prioritize them. Then, you can easily associate stories to features.

The Features

Each feature represents a part of the project, it can be of any kind. Features regroup the stories among them regarding their type or origin. Each feature is often given a unique colour and each story associated to a feature get its colour. Thanks to this very effective visual marker you can see instantly if you are concerned by a story or not.

The Stories

Each story represents an idea, (a piece?) of the project. Each idea is first submitted to the team in the sandbox. If it is acknowledged as a valuable idea for the project by the PO or the Scrum Master it goes to another “box” called The Product Backlog.

The Tasks

A story is generally a large idea. Therefore it has to be distributed in various tasks. All tasks should be compulsory to achieve the goal of a story, and so they must be all done before a Story is declared finished and delivered to the P.O. (client?)

Try it for free now
All you need for your Agile project management