|
= Release Planning =
|
|
# Release Planning
|
|
|
|
|
|
== Goals ==
|
|
## Goals
|
|
|
|
|
|
* Not have too much stuff left over at the end of a release
|
|
* Not have too much stuff left over at the end of a release
|
|
* Plan more accurately
|
|
* Plan more accurately
|
... | @@ -9,7 +9,7 @@ |
... | @@ -9,7 +9,7 @@ |
|
|
|
|
|
* What should we do with 0.3.5, 0.4.0, and 0.4.1 milestones?
|
|
* What should we do with 0.3.5, 0.4.0, and 0.4.1 milestones?
|
|
|
|
|
|
=== Personal Goals ===
|
|
### Personal Goals
|
|
|
|
|
|
* I want clear priorities
|
|
* I want clear priorities
|
|
* I want a very clear indication of which task is next
|
|
* I want a very clear indication of which task is next
|
... | @@ -25,11 +25,11 @@ |
... | @@ -25,11 +25,11 @@ |
|
* I sometimes hate how much time I spend on various administrative tasks
|
|
* I sometimes hate how much time I spend on various administrative tasks
|
|
* I want meetings to be very short and focused on the essential things that we all need to do
|
|
* I want meetings to be very short and focused on the essential things that we all need to do
|
|
|
|
|
|
== Discussion ==
|
|
## Discussion
|
|
|
|
|
|
Roadmaps tell us which tickets belong in which releases.
|
|
Roadmaps tell us which tickets belong in which releases.
|
|
|
|
|
|
=== What are we bad at? ===
|
|
### What are we bad at?
|
|
|
|
|
|
* Capacity Estimation
|
|
* Capacity Estimation
|
|
* Task Estimation
|
|
* Task Estimation
|
... | @@ -39,7 +39,7 @@ Roadmaps tell us which tickets belong in which releases. |
... | @@ -39,7 +39,7 @@ Roadmaps tell us which tickets belong in which releases. |
|
* Points in a release, and points left over
|
|
* Points in a release, and points left over
|
|
* Bugfix points: an estimate for unplanned fixes and their size
|
|
* Bugfix points: an estimate for unplanned fixes and their size
|
|
|
|
|
|
=== What could we possibly do? ===
|
|
### What could we possibly do?
|
|
|
|
|
|
* Proposal: marking things for a milestone is good
|
|
* Proposal: marking things for a milestone is good
|
|
* Proposal: putting tickets in a milestone after a capacity check is a good idea
|
|
* Proposal: putting tickets in a milestone after a capacity check is a good idea
|
... | @@ -58,7 +58,7 @@ Roadmaps tell us which tickets belong in which releases. |
... | @@ -58,7 +58,7 @@ Roadmaps tell us which tickets belong in which releases. |
|
* reference stories, to anchor estimates
|
|
* reference stories, to anchor estimates
|
|
* Proposal: order tasks by priority, and do the high-priority tasks first, with a time limit
|
|
* Proposal: order tasks by priority, and do the high-priority tasks first, with a time limit
|
|
|
|
|
|
=== What should we do in the next few weeks? ===
|
|
### What should we do in the next few weeks?
|
|
|
|
|
|
* We need to deal with 0.3.5 and 0.4.0
|
|
* We need to deal with 0.3.5 and 0.4.0
|
|
* Proposal: dump all 0.3.5 feature tickets in unspecified
|
|
* Proposal: dump all 0.3.5 feature tickets in unspecified
|
... | | ... | |