See description and "issues in epic" for further details for each epic below. For associated resource loading and story points, S15_dbPlanning_v12.xlsx (v10 and up include mid-cycle replan)
02C.06.01.01 Catalogs Alerts and Metadata (2002)
02C.06.01.02 Image and File Archive (2003)
02C.06.02.01 Data Access Client Framework (2004)
02C.06.02.02 Web Services (2005)
02C.06.02.03 Query Services (2006)
02C.06.02.04 Image Services (2007)
02C.06.02.05 Catalog Services (2011)
Mid-cycle re-planning
Resources
| FTE/month | March | April | May | June | July | August | Total |
|---|
| original | 6.25 | 5.25 | 5.25 | 4.75 | 4.75 | 4.75 | 31.00 |
| mid-cycle | 6.50 | 5.70 | 5.20 | 5.20 | 5.20 | 4.95 | 32.75 |
Loosing key developer at the end of April (Daniel)
Shifting work to several part-timers, including 2 new people, 2 remote
- AndyH 20->40%
- Brian 0->40%
- TonyJ 0->10%
- Vaikunth extending for additional 2.5 months
- Fabrice: 30% starting May
Work plan difference
- +64 SPs
- unplanned work: switching to xrootd ssi v2, documentation
- unplanned research of MaxScale (follow up after mysql conf)
- unplanned switch to C++11
- +17 SPs
- unplanned improvements done triggered by multi-node integration tests
- discovered need for refactoring CSS
- +20 SPs
- takes longer than expected
and 
- +11 SPs
- doing more because unexpectedly we have a RESTful expert
and 
- -63 SPs
- driven by resource loading, expecting to delivered planned prototype will scale back in some areas
Corresponding spreadsheets: