awebfactory - web application factory pattern

According to Chapter 20 of User Stories Applied, the following steps are necessary for release planning:

1. Select an iteration length.
2. Estimate the velocity.
3. Prioritize the stories.
4. Allocate stories to the one or more iterations.

This means, actually: create a release, with a date, then based on how much time separates then and now, and how long you want your iterations to be, decide how many iterations there will be.

Once the iterations are there, user stories can be allocated to them.

There is no allocation of user stories to releases; they are either allocated to an iteration or not implemented.

Releases should have a number (like 8.10 according to an arbitrary scheme) and a name (like Gutsy). The Drupal title of a release should be automatically formed from these.

Note that thanks to the many to many character of node 2 node relations, a user story can be allocated to more than one iterations.

So we first install Automatic Nodetitles. Then create the release and iteration content types.

[field_project_short_name-raw] [field_release_version-raw] [field_release_name-raw] [field_release_date-yyyy][field_release_date-mm][field_release_date-dd]

So project short name has to be required; we need it anyway.

To prioritize the user stories, just create an initial release and iteration, allocate all the user stories to the first iteration, then use the ordering of children found on the edit form of the iteration to order the user stories.