project flow & tracker
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.
At this point we just want to be able to get the user stories into the PFT system
Edit 2009-02-25: Using node2node module for drilling down and zooming out because it allows many to many relationships AND semantic role names, so not using NAT anymore.
Again, functionality of PFT will be based on its own genesis. That means that I will create the functionality of PFT according to my concrete needs in wanting to use an agile approach to its building.
So far, I have implemented the project business object, and have used that to specify the project and added functionality for each authenticated user to be able to flag the projects she is working on and to be able to see them towards the top on the homepage.
According to the process we are following for website application development, based on Chapter 1 of my book Leveraging Drupal: Getting your site done right (available for free download here), I now need to specify the roles: the actual users who will be interacting with the website application.
I've decided not to use Trac (which comes installed automatically with my repository instance) but PFT itself to build PFT. That way, its functionality will be based on its own genesis.
You know: project -> roles -> user stories -> releases and iterations -> planning -> tasks/defects/change requests -> build -> test and all the viewing and editing that goes on all the while...
- team leader
- team member
- create some example users
So, ...must ...create ...project PFT said to itself.