Changes between Initial Version and Version 1 of org/meetings/2019BrusselsNetworkTeam/Notes/ReleasePlanning


Ignore:
Timestamp:
Feb 1, 2019, 12:08:58 PM (18 months ago)
Author:
teor
Comment:

Release planning notes

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2019BrusselsNetworkTeam/Notes/ReleasePlanning

    v1 v1  
     1= Release Planning =
     2
     3== Goals ==
     4
     5* Not have too much stuff left over at the end of a release
     6* Plan more accurately
     7* Do higher-priority things first
     8* Make the process easy to understand and implement
     9
     10* What should we do with 0.3.5, 0.4.0, and 0.4.1 milestones?
     11
     12=== Personal Goals ===
     13
     14* I want clear priorities
     15* I want a very clear indication of which task is next
     16* I want to know how much time I should spend on a task
     17* I want limits on the amount of tasks I can have in progress
     18* I want to know when I should stop and ask for help
     19* I want to feel like I am making progress every day
     20
     21* I want to spend less time on tasks that drag and I don't feel like I am making progress
     22  * I want to know what I should do when a task blows up into something much larger
     23  * I don't know if I am expected to read all the IRC backlog
     24  * I often hate how much time I spend on email
     25  * I sometimes hate how much time I spend on various administrative tasks
     26* I want meetings to be very short and focused on the essential things that we all need to do
     27
     28== Discussion ==
     29
     30Roadmaps tell us which tickets belong in which releases.
     31
     32=== What are we bad at? ===
     33
     34* Capacity Estimation
     35* Task Estimation
     36* Roadmapping
     37* Post-Roadmap Extra Tickets
     38* We don't have a concept of a full release
     39  * Points in a release, and points left over
     40  * Bugfix points: an estimate for unplanned fixes and their size
     41
     42=== What could we possibly do? ===
     43
     44* Proposal: marking things for a milestone is good
     45* Proposal: putting tickets in a milestone after a capacity check is a good idea
     46* Proposal: one person checks capacity, and we should try to automate that check
     47* Proposal: when a milestone or sponsor is full, we stop adding tickets
     48* Proposal: regressions and security tickets go into the milestone
     49* Proposal: put really important must-do tickets in the release milestone
     50* Proposal: we allocate time for unspecified bugfixes and urgent things, and we reduce that time when we add a ticket
     51  * make a ticket with that time, and make it smaller when we spend the time
     52  * create a few buckets of time:
     53    * routine work
     54    * urgent work
     55    * technical debt reduction
     56* Proposal: tag nice-to-have tickets and put them in unspecified
     57* Proposal: track story points and velocity, rather than days of time
     58  * reference stories, to anchor estimates
     59* Proposal: order tasks by priority, and do the high-priority tasks first, with a time limit
     60
     61=== What should we do in the next few weeks? ===
     62
     63* We need to deal with 0.3.5 and 0.4.0
     64  * Proposal: dump all 0.3.5 feature tickets in unspecified
     65  * Proposal: dump all 0.4.0 feature tickets in unspecified
     66  * Proposal: triage 0.3.5 and 0.4.0 bugs
     67* We need to create 0.4.1
     68  * Make the roadmap good
     69    * Proposal: under-promise and over-deliver
     70    * Proposal: work out our staff capacity for 0.4.1 in each month:
     71      * 238 person-coding days in 0.4.1
     72      * 72 person-coding days for February
     73      * 72 person-coding days for March
     74      * 63 person-coding days for April
     75      * 31 person-coding days for May
     76    * Proposal: work out the sponsor deadlines, and put sponsored work before the deadline
     77      * sbws finishes at the end of March, and has 18 person-coding days
     78      * Sponsor V finishes in September, and has 24 person-coding days
     79      * Sponsor 19 finishes in May, and has ??? person-coding days
     80      * Sponsor 31 finishes in November, and has 110 person-coding days
     81      * Sponsor 2 finishes in August, and has 42 person-coding days
     82  * Proposal: remove everything from 0.4.1 that isn't on the roadmap
     83  * Proposal: add tickets to 0.4.1 based on the roadmap
     84  * Proposal: add time to 0.4.1 for unexpected bugfixes etc.