This page is for the Rice Roadmap Project team to collaborate and negotiate the last mile of defining release 1.1. The definition we're seeking includes:
- What is the effort available for working on research and enhancements?
- What will the release date be?
- What is the scope of the release that best meets stakeholder needs?
Determining the answers to these questions will require an iterative analysis since each has variables that impact the other.
Available Effort
Inputs:
- Available effort is 850 hours per month.
- Some items, such as research items, will require the Rice Lead Architect. S/he is not included in the 850 hour effort capacity.
Variables:
Variable |
Current Value |
|---|---|
Reserve for continued patch work on 1.0.x (includes support for Coeus 2.0 work) |
5% of available effort |
Reserve for miscellaneous bug fixes and minor improvements |
20% of available effort |
Quality Assurance (testing, documentation, bug fixing, etc.) |
25% of available effort |
Scale for estimating hours for Roadmap Items based on high-level estimates:
- epic = 1056 hours
- high = 528 hours
- medium = 176
- low = 40
- trivial = 8 hours
Release Date
According to the desired release cycle for Rice, and assuming a start date of January 1st for the 1.1 project, the target release date is between June 2010 and September 2010.
Application Release Date considerations:
- KS 1.0 and KC 2.0 are scheduled for Mar/Apr. 2010. Rice 1.0.x will be used.
- KC 2.1 is scheduled for May / June 2010. Rice 1.0.x will be used.
- KFS Release 4 is scheduled for October or so. Rice 1.1 is intended.
Variables:
Variable |
Current Value |
|---|---|
Release Date 1.1 |
September 2010 |
Release Date 1.2 |
April 2011 (assumes a 7 month project starting in October) |
Release Date 2.0 |
April 2012 (assumes a 30 month interval between 1.0 and 2.0) |
Working Assumptions:
- Effort available for 1.1 roadmap work (research and enhancements) is (9 months x 850 hours x .5) 3825 developer hours.
- Effort available for 1.2 roadmap work is (7 months x 850 hours x 0.5) 2975 developer hours.
- Effort available for 2.0 roadmap work is (12 months x 850 hours x 0.5) 5100 developer hours.
Scope
According to the initial prioritization done by the representative stakeholders, the following items are likely to fit into the available developer effort for the release.
There is about 29,000 developer hours worth of work represented in the Rice roadmap at this point!
Based on the available effort listed above, using a simple cutoff based on priority score and the working assumptions above, the following items will be included in release 1.1:
Using the attached Spreadsheet we can see how the effort adds up, and what kind of tradeoffs might be made to accommodate needs that are not met given the above release plan.
Other considerations:
Issues that one of the stakeholders considers critical, but which are not included in the 1.1 release plan at this time. These items collectively represent about 2100 developer hours worth of work. One of the items (KRRM-67) doesn't have an effort estimate because it requires more information. KRRM-67 may also be addressed with the 20% of available effort (1440 hours) reserved for bux fixes.