|
At Step
2 we had defined development teams.
Step 3 was about story
templates definition.
In this step
product owner and development team will try to plan
project releases.
Who

Product Owner |

Scrum Master |
|
|
|
Planning in SCRUM
SCRUM is based on development in time boxes called
Sprint. Sprint is a time needed to complete selected
stories (features, bugs, requirements, tasks,...). Length of the
sprint is typically 30 days, but it depends on a
development
strategy and product owner requirements.
Every sprint usually ends with a demo of
the work completed. At the end of the sprint
the development team shows
all completed stories to the product owner, stakeholders,
management and to anyone who is interested in. These stories are
also typically shipped to product owner.
Customers get a product version shipped in one or more releases.
Release contains completed work of the one or more
sprints.
In SCRUM are all the sprint stories released typically in one
release. ScrumDesk enables to develop more releases in one
sprint. To support this advantage feature, ScrumDesk support
Planning matrix.
Planning matrix is a matrix of the releases and sprints. Every
cell is storyboard filled with stories that will be shipped
in given release and developed in time of the sprint.

| Product Development |
| |
| Product Backlog |
|
|
        |
|
|
 |
| |
| Release A |
Release B |
 |
 |
| Sprint 1 |
Sprint 2 |
Sprint 3 |
| Completed |
Completed |
To Do |
Checked Out |
Solved |
Completed |
 |


 |
 |

 |
 |
 |
ScrumDesk:
Release plan
Product owner needs to know details of the release plan. Release plan is plan
of dates when completed product version will be shipped to
customers.
As example, we are going to release RSS Reader in two releases, one called
Release A (alpha) and second release called Final release.
Release planning in ScrumDesk is supported in view
Planning.
After the start, top row is displaying Product Backlog stories
that are unassigned to any sprint (we don't have stories yet, so
its empty).
Bottom row displays sprint
selected in combo box.

New Release
No release is created by default. To create new release, log in
as Product Owner. Only product owner (and Scrum Master in case
of the problems) can create new release.
Click on New link on the right upper corner in Backlog row.

Release dialog will appears. Enter release name, description and
estimated date of the release. At the bottom of the dialog will
be automatically calculated statistics for this release.

Close the Release dialog and look on the timeline. Small black
rectangle will appears
indicating newly created release. Clicking on this rectangle marker, Release dialog details
will be displayed.

Now lets create second, and the final, release of the RSS Reader
sample.


In release combo box you can see all defined releases and extra
items to easy filtering stories unassigned to some of the
release or all the stories.

|