• Generate initial release plan

  last modified September 14, 2007 by jladage

### Click edit to see the widgets ###


Add stories in project view


During the first day we don't bother about iterations at first. The view should allow the customers and employee to easily create new stories. this can be done by providing a collapsable link "Add story". When clicking the link it should display the form elements to add an story (title and description), initial stories are created directly inside the project.

Add new story
Deze beschrijving wordt gebruikt om de feature te beschrijven. Het is aan te raden dit kort te houden, een story is slechts een herinnering aan een te voeren discussie.
Deze keuze bepaalt of de de story in de eerstvolgende iteratie toegevoegd wordt of in de laatste.
Zo snel mogelijk uitvoeren.
Aan het einde uitvoeren.

Note: the contents of the description field should be transformed using intelligent-text, so urls are transformed to anchor tags in the view.

Status: implemented see http://dev.plone.org/collective/browser/eXtremeManagement/branches/markvl-release-plan


Dividing stories in iterations

After creating and prioritizing the initial list of stories we now want to create a Release Plan.
The manager should be able to "Create initial release plan" . Which should expand the following form.

Create initial Release Plan
Select the first working day at which the first iteration should start.
/ /



Submitting that form will call a script that executes the following actions:
  • Calculate the total amount of story points
  • Divide that amount by the estimated velocity (defined in the project) to get the number of iterations needed and add one to it.
  • Create the calculated number of iterations, and fill in the start and end date based on the duration specified in the project.
  • From top to bottom start moving stories into the first iteration. If a story will overrun the estimated velocity, move to the next iteration and continue moving story until all stories are moved into iterations.
    When calculating overrun take 90% of the velocity (10% project management) and subtract 1 storypoint for Release management.
  • Add a Project management story of 10% of the estimated velocity worth in story points in each iteration.
  • Add a story for Release management in each iteration.

After this script has run the listing should show all stories grouped by iteration.

Current status: Working prototype made by markvl on http://dev.plone.org/collective/browser/eXtremeManagement/branches/markvl-release-plan


Drag and drop prioritize stories between iterations


This story is a continuation of Initial Release Plan. It explains what should happens after the initial release is created.


Iteration 1
 Points State
A User need to have a certain feature 2.0
 estimated
A User also needs this feature
 4.0
 estimated
A User need to have a certain feature 4.0
 estimated
Project & Release Management
 1.0
 estimated
+
Total

 11.0
Iteration 2
 Points State
A User need to have a certain feature 2.5
 estimated
A User need to have a certain feature 9.0
 estimated
A User also needs this feature 4.5
 estimated
A User need to have a certain feature 3.0
 estimated
Project & Release Management 1.0
 estimated
+
Total

Iteration 3
 Points State
A User also needs this feature 6.5
 estimated
A User need to have a certain feature 4.5
 estimated
A User also needs this feature 3.0
 estimated
A User need to have a certain feature 7.0
 estimated
A User also needs this feature 1.0
 estimated
A User also needs this feature 0.5
 estimated
A User need to have a certain feature 1.0
 estimated
Project & Release Management 2.0
 estimated
+
Total

iteration 4
 Points State
+ A User need to have a certain feature 4.5
 estimated
+ A User need to have a certain feature 3.0
 estimated
        Task 1 for feature X 1.0 estimated
        Task 2 for feature X 1.0 estimated
        Task 3 for feature X 1.0 estimated
        + Total 3.0
+ A User also needs this feature 1
 estimated
+ Project & Release Management 0.5
 estimated
+
Total

After creating the release plan the following list is shown. As you can see the project and release management stories are added in each iteration and the stories are spread evenly over the iterations.

We also want to provide drag and drop for this list, so a customer can easily change the priority of the stories.

There are a few conditions:
  • A management story can't be dragged
  • A management story always has lowest priority
  • When dropping a story at a different position within the same iteration it should be reordered.
  • When dropping a story inside a different iteration, it should be moved AND reordered, respecting the previous rules

By moving a story into another iteration, it might be that the total number of story points will exceed the estimated velocity of that iteration.
If an iteration contains more story points than the estimated velocity, the background should be displayed in pink.