HM Courts and Tribunal Service (HMCTS)
HMCTS - Performance Enhancement Team - PET (sustaining team) Development Capabilities.
9 Incomplete applications
8 SME, 1 large
5 Completed applications
4 SME, 1 large
Important dates
- Published
- Thursday 11 May 2017
- Deadline for asking questions
- Thursday 18 May 2017 at 11:59pm GMT
- Closing date for applications
- Thursday 25 May 2017 at 11:59pm GMT
Overview
- Summary of the work
- HMCTS is undergoing an extensive Digital transformation for which Agile Technical Specialists are required. The Sustaining team deliver a mixture of systems analysis, technical investigation, live service evaluation, enhancement sizing, implementation planning, technical issue resolution, management of service outages, and supporting resolution of information requests
- Latest start date
- Monday 10 July 2017
- Expected contract length
- Up to 2 years. 1st SOW for 3 months, subsequent SOWs dependent on Agile phase duration
- Location
- London
- Organisation the work is for
- HM Courts and Tribunal Service (HMCTS)
- Budget range
-
The maximum rate MOJ are prepared to pay is:
- Business Analyst £700
- Python Developer £650
- Ruby Developer £650
The total Supplier charge will be evaluated as per evaluation crieria %.
About the work
- Why the work is being done
- HMCTS is undergoing an extensive reform transformation enabled by a technology work stream. The Technology work stream spans several programmes within the change portfolio - delivering the service transformation, the supporting platform and the enabling new services, all needed to deliver the benefits. Current HMCTS services are typically supported by high-volume, paper based processes. The Change Portfolio's main technology objective is to develop efficient, proportionate and accessible digital services delivering access to justice via appropriate modern channels. These digital services are being developed within a coherent architecture which maximises reuse across the services.
- Problem to be solved
-
Current HMCTS services are typically supported by high-volume, paper based processes which are expensive, subject to frequent delay and often unclear to persons without legal training leading to a high number of support calls. The CFT Programme is designed to develop efficient, proportionate and accessible digital services delivering access to justice via appropriate modern channels.
The Reform Sustaining Team provide the Beta live services for the new systems. A team is required, comprising of up to, four (4) Ruby developers, three (3) Python developers and two (2) Business Analysts - Who the users are and what they need to do
-
As a User of the Courts system I require the ability to have a digital justice system that is coherent, flexible, efficient, proportionate and accessible. I require the system to be in plain English and I do not wish to be confused by legal jargon.
As an employee of the Courts system I require the digital justice system to be efficient, easily managed and to assist me in my daily duties
As a member of the legal judiciary I require the digital justice system to reflect the legal requirements and all elements of the Statute to remain in extant - Early market engagement
- Any work that’s already been done
-
The wider programme has undertaken extensive planning and mobilisation as part of the 6 year transformation roadmap. The projects are staggered across the length of the programme so all are currently at different stages of their life-cycle.
Works have commenced within the Sustaining team to establish the support process, however continuous improvement and refinement is needed. The team deliver a mixture of systems analysis, technical investigation, live service evaluation, enhancement sizing, implementation planning, technical issue resolution, management of service outages, and supporting resolution of information requests - Existing team
- The existing team is a blend of internal staff and external contractors/consultants from a range of suppliers. The Reform Sustaining Team includes several Python and Ruby developers and Business Analysis roles. The team also consists of Service and Project Management, a Solution Architect and a Delivery Manager.
- Current phase
- Not applicable
Work setup
- Address where the work will take place
-
102 Petty France, London, SW1H 9AJ (the 'Base location', although some UK Travel may be expected)
The authority may consider suppliers hosting project teams at their own premises. Any benefits offered by suppliers in this scenario should be reflected in the value for money section of the written proposal. - Working arrangements
-
The suppliers team will initially be required to work onsite at the base location working a five (5) day week.
The Service is being delivered against the GDS Service Manual (e.g. agile delivery aligned to scrum methodology).
For any work performed at a location different to that of the Base location (or the supplier's own premises) and London (outside of the M25), all reasonable travel and expenses costs shall be met in accordance with the rates set out in the MoJ travel and subsistence policy. All expenses will require prior approval from HMCTS before being reimbursed. - Security clearance
- Baseline Personnel Security Check (BPSS) which must be dated within three months of the start date. See https://www.gov.uk/government/publications/government-baseline-personnel-security-standard for further guidance.
Additional information
- Additional terms and conditions
- All expenses shall adhere to the Ministry of Justice standard Travel and Subsistence policy. Expenses to Base Location of works will not be paid, nor expenses within London M25 location
Skills and experience
Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.
- Essential skills and experience
-
- Capable of deploying 3 Ruby, 2 Python and Business Analysts on 15th July; with 3 years minimum experience, with the ability to fulfil the remaining requirement within 6 months(2%)
- Experience of interfacing with technical and business teams to deliver enhancements across multiple applications; working with non-technical stakeholders to evaluate technical needs, building rapport / strong working relationships(2%)
- Experience of working with technical and business teams to deliver Agile Beta service support across multiple applications / digital services.; building a strong working relationships and prioritising incident resolutions(2%)
- Capable of demonstrating capability expertise, minimum of 3+ years commercial experience with Ruby on Rails, working on large-scale projects or supporting significantly sized services(2%)
- Capable of demonstrating capability expertise, minimum of 3+ years commercial experience with Python Django, working on large-scale projects or supporting significantly sized services(2%)
- Capable of demonstrating capability expertise, minimum of 3+ years commercial experience with one or more of the following tools; libraries: Github, Jenkins, Salt Stack, Fabric, Jenkins and Docker(2%)
- Capable of demonstrating capability expertise, minimum of 3+ years experience working in agile multidisciplinary teams meeting user needs based on a prioritised backlog(2%)
- Experience of continuous Integration, distributed version control workflow, automated testing (approach to quality), reducing and avoiding technical debt, ability to describe a complex technical situation to a less technical person(2%)
- Experience of working in an Agile digital change project, preferably following the Digital By Default Service Standard: user-first approach, accessible solutions, responsive 'mobile-first' web apps, continuous improvement (backlogs, sprints, retrospectives)(2%)
- Demonstrable experience of documenting business process models (as-is and to-be), documenting business needs and associated KPIs, and clarifying business rules(2%)
- Demonstrable experience of where story maps and sprint plans have been delivered for multi-skilled teams including design and development tasks(2%)
- Describe your experience in defining sprint tasks and user stories that have well defined acceptance criteria and sizing(2%)
- Define how you measure success in MVP and future states, defining how you have balanced the demand for iterations with new functionality and supported prioritisation of change(2%)
- Nice-to-have skills and experience
-
- Experience of using microservices and containerisation to deliver solutions that meet business process needs(1%)
- Evidence of supporting the development of the Service vision and its interpretation into a delivery roadmap(1%)
- Demonstrate team ways of working that support scaled agile delivery with collaboration across multiple teams within a transformation programme(1%)
- Evidence of analysing and documenting service data and metrics(1%)
How suppliers will be evaluated
- How many suppliers to evaluate
- 5
- Proposal criteria
-
- Proposed Team members, minimum 3 years experience in multidisciplined teams delivering Ruby on Rails, and/or Python Django, and/or Github, Jenkins, Salt Stack, Fabric, Jenkins and Docker(5%)
- Provide named individuals and cv's for initial team; three (2) Ruby Developers, two (2) Python developers and one (1) demonstrating experience of working in agile multi-vendor teams(5%)
- Describe how will you ensure that HMCTS is supplied with high quality and appropriately skilled team specialists, whilst minimising HMCTS's effort in screening th eproposed team members(4%)
- Describe your approach to adding, replacing and rotating new team members, within a 2 week notice period, to the existing team without reducing the teams velocity(2%)
- Provide three referenceable client focussed case studies where your company have provided the desired service capability; please identify the proposed team member(s) that were part of the delivery team(9%)
- Describe how you intend to measure and manage quality and speed of delivery within the team to ensure continuous improvement(2%)
- Propose your approach for enabling digital teams, delivering capability and ensuring that knowledge transfer is conducted during handover of project outputs to the HMCTS BAU maintenance team(4%)
- Give examples of KPIs and SLAs that you would be prepared to commit to for this contract, including ability to provide high calibre substitutes/replacements within 2 weeks(2%)
- Explain the Value Proposition; value for Money, how the proposal will optimise costs, and generate savings. Demonstrate how discounts will be linked to volume and duration(5%)
- Cultural fit criteria
-
- Explain the approach for working with multi-vendor teams across multiple projects at different locations(3%)
- Explain how you will ensure collaboration at all levels of the project and programme delivery between users, team members, and management. Give examples of where you have taken this approach(2%)
- Payment approach
- Time and materials
- Assessment methods
-
- Written proposal
- Case study
- Work history
- Reference
- Presentation
- Evaluation weighting
-
Technical competence
70%Cultural fit
5%Price
25%
Questions asked by suppliers
No questions have been answered yet