|
Intro, User stories, Strategy, Iteration 1, Iteration 2, Iteration 3, Iteration 4, Iteration 5, Iteration 6 (Download!), Theory
Iteration 5
At this point I have more or less given up on using AgilePlanner while coding
it. Although eco offers excellent tools for database schema evolution, the extra
complexity of making sure that everything is backwards compatible all the time
does not weigh up for the gain I get. After all I am alone in this project with
no real users to support so far. If I would have real users using some release
of AgilePlanner I would need to take extra care of course.
|
10
|
As a team leader I want to manage a release plan, coordinated with the iteration planning
so that we know when to deliver
|
3
|
-
Treat this the same as a MileStone, with a specific Release MileStoneKind enum
value.
|
|
13
|
As a product owner I want to see multiple teams iteration planning at the same time and add team
coordination milestones if necessary so that we do get one team waiting for
another more than necessary
|
4
|
-
Add a milestone class associated to project
-
Add Gui to edit MileStone
-
Add milestones to iteration view
|
|
17
|
As a product owner I want to see a burn down chart so that I can judge if I should worry
or not
|
3
|
-
Since the burndown chart always follow the iterations implement it in the project
view.
|
|
18
|
As a team leader I want to mark user stories as “known from the start”, “added along the way” or “Removed
along the way” in order to explain changes in release dates
|
1
|
-
Introduce DateTime properties DateIntroduced and DateRemoved
-
Set DateIntroduced to Today on creation of a UserStory
|
|
|
|
|
-
|
The milestones shows up on the line called “Iterations” as icons.
The Burn down chart was implemented as a
shine thru overlay; turned out pretty good:
|
Press NEXT to continue
|