WP1304 - Transformation Map Requirements

Tender description

Summary of the work Develop a dynamic mapping tool of government transformation strategy across government, highlighting dependancies and programme information. Expected Contract Length 2 Months (Until the beginning of May 2017) Latest start date 9th March Why the Work is Being Done The Transformation Peer Group (TPG) has been commissioned to map transformation programmes across government. This will take the form of a digital tool that Civil Servants can access to see dependancies and other data about programmes. A public beta of the tool should be ready for early April 2017. Problem to Be Solved Departments cannot currently see how their programme relates to other programmes across government. This in turn leads to activities being duplicated across government. Departments cannot see how other programmes depend upon them, leading to poor decisions for the whole of government being taken. Ministers cannot see how their department has to work with other departments to achieve their priorities. This leads to resourcing being improperly allocated across the department. Treasury cannot plan cross government programmes as they cannot not see how these programmes fit into wider government transformation. Who Are the Users As someone involved in a programme, I need to see projects/programmes who we have a dependancy on, so that the collaboration can be managed. As a SRO, I need to see where a programmes critical dependancies are, so those risks can be managed and prioritised. As a Programme Director, I need to see which programmes have similar outcomes to mine, so that I can see if we should be working together. As a Senior Civil Servant, I need to see how my department is currently working with other departments, so that I understand how best to manage the relationship. Early Market Engagement None. Work Already Done A Proof of Concept has already been done and a video of the work can be viewed here: https://www.youtube.com/watch?v=HLlylQ4AiYw&feature=youtu.be Existing Team The supplier will be expected to work with a Non Technical policy team for 3 civil servants. Current Phase Discovery Skills & Experience • Have experience designing over 5 services using data to extract value and insight with ease • Have over 5 years professional experience delivering at pace with tight fixed deadlines • Proven successful development of back-end technologies, databases, developing APIs, meeting data standards, and experience of GitHub • Over 3 medium size projects (3-6 months each) worth of experience with front end data visualisation such as data mapping and/or dependancy mapping. • Have 4 years of experience developing open source products • Demonstrate experience of delivering agile projects in sometimes non-agile environments for at least 2 projects. • 5 years of technical expertise of front-end, UI web development and responsive web design (HTML5/CSS/JS) • 5 years of experience of prototyping, testing and iterating with users and stakeholders • 3 years proven experience in using robust metrics, analytics, search data and user feedback to audit and define key content and services Nice to Haves • At least 1 project of experience of delivering services designed for internal government use • At least 3 projects worth of experience of building a dependancy mapping project, programmes, organisations or services • At least 3 projects worth of experience scrapping data from a variety of data sources, programmes and organisations Work Location Westminster, London Working Arrangments Working offsite 5 days a week (mon-fri) roughly 9am-5pm, with daily check in calls with the team, and face-to-face meetings at the request of the supplier (roughly 1 per week). Security Clearance BPSS Security cleared Additional T&Cs Standard Cabinet Office terms and conditions will apply No. of Suppliers to Evaluate 5 Proposal Criteria • Technical solution • Approach and methodology • How the approach or solution meets your organisation’s policy or goal • Estimated timeframes for the work • Value for money Cultural Fit Criteria • Work as a team with our organisation and other stakeholders • Transparent and collaborative when making decisions • Have a no-blame culture and encourage people to learn from their mistakes • Be able to deliver even with uncertainty surrounding the programme • Can work with clients with low technical expertise • How they’ve identified risks and dependencies and offered approaches to manage them • Be transparent and collaborative when making decisions Payment Approach Fixed price Evaluation Weighting Technical competence 45% Cultural fit 15% Price 40% Questions from Suppliers 1. Do you have a budget range in mind for this work? At this stage we would like to engage with the market in order to understand the range available. 2. Some of the dates seem to conflict (for example, 8 week piece of work, however Public Beta after 4 weeks?), therefore to ensure we are completely clear, please can you state what is expected to be delivered (outputs) and by when? The length of the contract is for eight weeks. In the first month suppliers will be expected to develop an alpha (MVP) which we will present to a large group of senior stakeholders on the 6th April. Following this suppliers will be expected to iterate the product based on feedback so a stable product is delivered at the end of the two months. 3. You have indicated that the current stage is Discovery. As you have a proof of concept already we are unclear whether you have done the Discovery and/or whether you are looking for someone to work with you from Discovery through to Beta? We have conducted some discovery activity, including reviewing existing work and user research with select group of users. Following development of the proof of concept we have shown the tool across government and received feedback that would be incorporated into the development of the tool. We are looking for a supplier to take the proof of concept through to an alpha (MVP) which we will present to large group of senior stakeholders on 6th April. Suppliers will then be expected to iterate the product based on feedback so a stable product is delivered at the end of the two months. 4. What is the extent of the user research already taken place? Prior to the proof of concept a user needs analysis was conducted with a small set of users. Following the development of the proof of concept we have shown the tool across government and received feedback that would be incorporated into the development of the tool. 5. Is the Transformation Peer Group committed to a bespoke build approach, or would they be open to procuring an existing solution should it meet the users needs? We are not committed to a bespoke build approach and would welcome proposals from existing solutions. However in our initial research no solution met all of our needs. 6. Has the tech stack for this product been defined and what technologies does it have to integrate / have APIs to pull the data from? No technology stack has been defined and we would be looking for suppliers to recommend a solution. We would like to be able to integrate with departmental project management systems, but no engagement has happened identify how this could be done.