Page History

...

1. Two estimation teams will be selected: one for the Angular UI and one for the REST API.
2. Estimation spreadsheets (based on the Lullabot Wideband Delphi spreadsheet) have been created for tasks that require estimation. (See below "Estimation Spreadsheets" section)
3. Each task in those spreadsheets will be estimated (privately) by 2 different developers at separate institutions Developers are welcome to collaborate on their estimates with colleagues at their institution, but their estimates should not be shared with other estimators.
   1. Each task estimate consists of the following:
      1. A summary (a few sentences or paragraph) of the proposed solution that the developer is estimating. This summary should describe any assumptions you are making, and what development work you are specifically estimating for. Also, as needed, be sure to include any information about the type of developer (e.g. senior vs junior developer) you are assuming in your estimate. So, if a specific task likely requires a senior developer, note that, and estimate based on that assumption. 
      2. An estimate (in hours) of the design phase. For the REST API, this estimate should include development of the REST Contract PR & responses to feedback.  For the Angular UI, this estimate should include any mockups (as needed) & responses to feedback. Design review should not be included in this estimate, as the spreadsheet is setup to automatically add 20% to all estimates to cover the design review process.
      3. An estimate (in hours) of the development phase. This estimate should ONLY include development activities, including Test Driven Development (and estimates of amount of time to respond to PR feedbacke.g. unit and/or integration tests).  Code review should not be included in this estimate, as the spreadsheet is setup to automatically add 20% to all estimates to cover the code review process.
4. Completed estimates will be submitted to LYRASIS staff (Heather & Tim). At this point all estimates will be combined into a "master" spreadsheet.
5. An Estimation Meeting will then be called (for each estimation spreadsheet).  This meeting will include LYRASIS and anyone who contributed an estimate (though others are welcome to attend if they wish to add to the discussion)
   1. The meeting will concentrate primarily on tasks that had a large variance (i.e. difference) in the estimations.  All meeting attendees will discuss these tasks in greater detail (including further scoping as needed) and work on an estimate that everyone is comfortable with.
6. Final estimates will be entered into the master spreadsheet for each task.  These final estimates may be based on discussions in meetings, or (for tasks which were estimated very similarly) copied more directly from previously submitted estimates.
   1. It is important to note that final estimates are not simply an "average" of submitted estimates. The goal is to discuss any tasks where there is larger disagreement and come to a general consensus on what a reasonable estimate is.
   2. 20% is added to each estimate to cover the code review process
   3. 10% is added to each estimate to cover any additional project management activities
7. (These steps may be repeated as additional tasks are defined/scoped & new estimation spreadsheets are created. Once all outstanding tasks have been estimated from our DSpace 7 Development Planning spreadsheet, we will have a combined estimate of work effort to get to 7.0 Beta)

...