1. ExampleApp Vision Statement Version 3, Tony Heap, 19/10/2009

2. Purpose (Agenda) A description of the project, including –Background –Objectives –Scope –Timelines –Delivery approach –Stakeholders –Risks and Issues A living document

3. Project Background ExampleApp been in existence for 7 years (since 2003) Grown over that time –19,000 users –15,000 organisations –13 organisation types (aka “views”) –505 individual widgets

4. Key Issues Widget set unmanageable –500+ XL spreadsheet tabs –1000+ Word docs (Guidance Docs & Checklists) –Huge amount of repetition –Some inconsistencies Not very user friendly –Especially for infrequent users –Different user types have different needs Online/offline usage model issues –Missing features prevent online use –No facility to export for offline use

5. Project Scope Key Feature Area Description Widget authoringTool to allow XYZ team to write and update widgets much more easily. Single document per source Consolidation of the on-screen content, guidance documents and checklists into a single document for each widget. DownloadAbility to easily download the widgets in both spreadsheet (e.g. Microsoft XL) and document (e.g. Microsoft Word) format. Online improvement planning and evidence upload Ability to allocate improvement plan tasks to individuals, apply deadlines and send reminders. Ability to mark actions as complete and upload appropriate evidence. UsabilityVarious improvements to the usability and look-and-feel of the application in order to make the ExampleApp experience more pleasurable (or perhaps less vexing!) ReportingEnhancements and additions to reporting functionality

6. Detailed Scope List Detailed scope and priorities to be managed on an ongoing basis as an XL sheet

7. Delivery Approach Multiple increments (cycles) –Timeboxed 3-week cycles fixed end date, not fixed scope –Priority items delivered first –Changing priorities managed ongoing Single go-live –Probably

8. Timeline MilestoneDate Start19 July 2009 Vision Statement agreed (initial scope and priorities defined) 16 October 2009 Widget authoring tool ready for use by XYZ team 20 November 2009 System requirements “ready for development” 18 Dec 2009 Development cycle 1 begins4 Jan 2010 Development cycle 8 ends11 June 2010 Go live30 June 2010

9. Stakeholders (1) StakeholderResponsibilitiesInterest XYZ TeamOwn ExampleApp Author widgets Provide 3 rd Line support Ease of administration Quality of content Users – SHAs and TrustsComplete assessments (frequent users) Advanced features (e.g. Online action planning) Users – Type AComplete assessments (occasional users) User friendly Easy and quick to use Users – Type BComplete assessments (occasional users) User friendly Easy and quick to use Technology OfficePromote widgets throughout the NHS Content of requirements DevelopmentDevelop and maintain software Easy to maintain SupportSupport softwareMinimise support calls

10. Stakeholders (2) StakeholderResponsibilitiesInterest National Widget BoardVarious audit and reporting responsibilities Appropriate auditing functionality available Appropriate reports available Widget Office Widget Quality Commission Widget Information Centre Widget Commission Internal Audit

11. Risks and Issues Deliver wrong thing due to lack of consultation with –Type A users –Various governance bodies (XXX, YYY) Don’t deliver enough due to development resource constraints