Organisation

Work/Task Breakdown

Proof of Concept

1. Confirm POC requirements (REACH, Dev Team)
2. Configuration of supporting tools: GitLab, Bamboo, JIRA (Dev Team, Service Management)
3. Create back end database (Dev Team)
4. Create back end application with data maintenance features (Dev Team)
5. Specification and provisioning of infrastructure for front end (WGI)
6. Implementation of registration form in Drupal (WGI)
7. Integration of registration form with back end (WGI, Dev Team)
8. Internal testing (WGI, Dev Services)
9. User acceptance testing (REACH, WGI, Dev Services)

Release 1 - Minimum viable product - Web form and back-end - for initial REACH launch ( for Mon 2-Oct 2017)

1. Create technical spec/SDS for back end and overall architecture (Dev Team)
2. Confirm that planned architecture conforms to regulations (REACH, Dev Team)
3. Create technical architecture document (TAD) (Dev Tech)
4. Provisioning of infrastructure for back end (Dev Tech)
5. Integration of registration form with back end (WGI, Dev Team)
6. Internal testing (WGI, Dev Services)
7. User acceptance testing (REACH, WGI, Dev Services)
8. Create support documentation (SDD) (Dev Team, WGI)
9. Deployment

Release 2a - Minimum viable product - REACH Front-end website - for initial REACH launch ( for Mon 2-Oct 2017)

1. Implementation of ‘supporting information’ pages, with CMS to allow REACH to update them (WGI)
2. Implementation of researcher application form (WGI)
3. Integration of researcher application form with back end (WGI, Dev Team)
4. Internal testing (WGI)
5. User acceptance testing (REACH, WGI)
6. Update support documentation (SDD) (WGI)
7. Deployment

Release 2b - Data Exports ( after initial go-live ) 

1. Refinement of requirements for data export features (Dev Team, REACH)
2. Design and build of data export features (Dev Team)
3. Internal testing (Dev Team)
4. User acceptance testing (REACH, Dev Team)
5. Update support documentation (SDD) (Dev Team)
6. Deployment

Release 3 - Project Workflows ( after initial go-live)

1. Requirements gathering for project workflow features (Dev Team, REACH)
2. Design and build of project workflow features (Dev Team)
3. Internal testing (Dev Team)
4. User acceptance testing (REACH, Dev Team)
5. Update support documentation (SDD) (Dev Team)
6. Deployment

Resources, Skills and Costs

Initial estimate from 01/08/17

16 days for LTW WGI team for Web front-end 

90 days for IS Apps , Dev and operations , and IS Project Services for Web form integration and back-end data management

The total estimated costs are 16 + 90 = 106 days

IS  day rate is currently £320 giving a total estimated project cost of £33,920 for initial project effort.

Effort by LTW WGI team and IS ADO and IS Project services will be invoiced separately

This excludes annual business-as-usual on-going  support costs , to be agreed as part of separate SLA

This also excludes any additional infrastructure costs - eg. subsequent move to the ITI 'Safe Haven' or to dedicated virtual machines

Project Governance

Colin Simpson is Project Sponsor

Bill Lee is Senior Supplier

Muriel Mewissen is the IS Project services - MVM Portfolio Manager

The MVM315 project sits within the MVM RES programme

Project Stakeholders

The IS Applications Division Team will include:

• John Allison
• Martin Jones
• Peter Jackson
• Bill Lee
• Jamie Thin

The IS LTW Division Team will consist of

• Arthur Wilson
• Aileen Robertson
• Craig Campbell

The REACH Team will consist of

• Colin Simpson
• Abby King
• Ireneous Soyiri
• Susan Buckingham

Project Estimations

Initial estimate from 01/08/17

16 days for LTW WGI team for Web front-end 

90 days for IS Apps , Dev and operations , and IS Project Services for Web form integration and back-end data management

Outline breakdown of the IS Apps , Dev and operations , and IS Project Services estimate