HM Courts and Tribunal Service (HMCTS)

HM Court and Tribunal Service - Hands-On Technical Lead (Reform Programme) RFM-TD-002

Incomplete applications

Incomplete applications

Completed applications

Completed applications
25 SME, 8 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Thursday 2 June 2016
Deadline for asking questions Thursday 9 June 2016 at 11:59pm GMT
Closing date for applications Thursday 16 June 2016 at 11:59pm GMT


Opportunity attribute name Opportunity attribute value
Specialist role Technical Architect
Summary of the work Hands-On Technical architect (developing designs and building code) required for HMCTS Digital Transformation project supporting the Civil Justice Reform Plan.
Latest start date 04/07/2016
Expected contract length Up to 2 years
Location London
Organisation the work is for HM Courts and Tribunal Service (HMCTS)
Maximum day rate £770

About the work

About the work
Opportunity attribute name Opportunity attribute value
Early market engagement None
Who the specialist will work with HMCTS have a "rainbow" team of specialists for the initial discovery and later phases. This includes user researchers, business analysts, solution architects, delivery managers, service managers and business representatives (product owners/managers). Specialists will be expected to fit with existing teams and pick up work already completed quickly
What the specialist will work on Technical Lead for HMCTS Digital transformation projects to support and produce:
An end to end digital service for users enabling them to start, progress, and receive decisions for cases online
A service that can flex the way it works according to user needs and simpler for users to understand rather than complex paper based process;
A service where users can see what is happening in the process and are clear about next steps
An efficient service for decision making from other third parties which allows evidence sharing
Digital solutions that can be used across other HMCTS services.

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place 102 Petty France, London, SW1H 9AJ (the 'Base location', although some UK Travel may be expected)
Working arrangements The teams is still in the forming stage. The specialist will 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 alligned to scrum methodology).
For any work performed at a location different to that of the Base location 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 Disclosure Scotland

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions Any expenses shall be submitted in line with Ministry of Justice standard Travel and Subsistence policy.

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Experience of leading technical and developer teams with examples of successful design and delivery of working services within government
  • Technical expertise in front end development (e.g. HTML 5, CSS 3, SASS, Javascript)
  • Technical expertise in back end development (e.g. SQL Database, Java 8, Node.JS, Java Message Service (JMS) and Apache ActiveMQ)
  • Technical expertise in integration technology (API's, protocols and standards)
  • Technical expertise in testing tools and methodology (TDD and Capybara / Selenium, JUnit or TestNG)
  • General technical knowledge: Use of open-source libraries, Use of Object Relational Mapping, e.g. Hibernate, Knowledge of Dependency Injection and Experience building RESTful services
  • Choosing Technlogy - Experience in the design of and construction of information architectures that will enable well integrated transactional, collaborative and analytical systems
  • In depth experience of designing and implementing enterprise solutions in an Agile environment with specific reference to meeting the Government Service Design Manual and/or Government digital projects
  • Proven track record and ability in leading/mentoring technical staff
  • Sound understanding of software development life cycle models and familarisation of software version control tools (specifically GIT).
Nice-to-have skills and experience
  • Experience of delivering phases of government digital services in a minimum of 3 different project environments
  • Experience of BDD (Behaviour-driven development) and TDD (Test-driven development)
  • Experience of using virtualisation for developing, e.g. Vagrant to build dev VMs
  • Experience of designing and developing microservices
  • Experience of migration between different cloud environment (e.g Skyscape to Azure)
  • Experience of handover work / live services to buyer and/or supplier teams

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many specialists to evaluate 5
Cultural fit criteria
  • Demonstration of agile culture and values
  • Demonstration of working as a team to deliver high quality products
  • Be visible to staff and stakeholders and regularly undertake activities to engage and build trust with people involved in area of work
  • Demonstrate responsibility (e.g. act like a leader, serve your team, provide solutions to problems, engage in external/internal environments, seek the best for the organisation beyond your team)
  • Able to work under own direction and set own short term targets as required
Assessment methods
  • Work history
  • Reference
  • Interview
  • Scenario or test
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. The expected contract length stated is up to 2 years. What will be the length of the initial term? When we have selected the right specialist we will work with them to develop the first statement of works (SOW). The first SOW will be for a 3 months duration. Other SOWs will then be developed for the remainder of the 2 year term subject to the performance of the specialist.
2. For the avoidance of doubt, please state how many candidates a supplier may submit at the initial stage. There is no limit on the number of candidates a supplier may submit however only a maximum of 5 will be shortlisted from all submissions received.

Please note this is one of two requirements published on here for a technical lead.

Briefing session on Friday
The briefing session on Friday 10th June will take place at 14:00 for approximately one (1) hour.
4. I would be grateful for details of where the briefing session will take place and how we can register as we are interested in attending. The date and time of the session is published under question 3.

Suppliers do not have to register their attendance. They should dial in to the teleconference using the number and code that is published in the requirements.
5. IMPORTANT UPDATE - Briefing session The briefing will take place at 14:00 by teleconference for approximately one hour. Details were published with the requirements as follows: Dial in details: 0800 917 1956 (Mobile access - 0203 463 9739), Participant PIN 29004640#.
6. IMPORTANT UPDATE: Bid Submission Candidates will be shortlisted by no later than cop on 20/06/2016. Shortlisted candidates will be required to submit evidence of their skills and experience, work history and references by 12 noon on 22/06/2016. Interviews are scheduled for w/c 27/06/2016.
7. Do we still need Disclosure Scotland if a specialist has a higher level of clearance? Yes. This is mandatory. Suppliers are advised to use the following site to apply for Disclosure Scotland.
8. Is there data migration to do? There are legacy applications with information stored on paper case files. This information may need transitioned into any new system that replaces the process. Alternatively we may choose a double running cut over between existing process and the new digital services
9. What technology is the HMCTS Common Platform Programme (CPP) built upon and where is HMCTS in this process? The CPP takes existing case management systems and digitalises the process. It is focused on the criminal side of MOJ/HMCTS as our programme has a Civil, Family and Tribunals (CFT) focus. It is for citizens facing the justice system. No decision has been taken on whether to use technology built for the CPP, although of course we will be re-using what is appropriate.
10. How much work has taken place on User Research? A UX Function (Researchers, UX Designer and Content Designers) is in place in each team as a full time resource. To dates sessions have taken place F2F, by telephone interview and shadowing support units. Procurements are also ongoing through DOS for User Participants and Labs. As the current teams are in discovery, there are focusing on user research at present.
11. Is the Authority specifically looking for the areas of expertise listed under the essential criteria for front and back end developers? For back end technologies we are specifically looking for a Java focus and the front end technologies Node and HTML based.
12. What platform are the programme using for hosting? The Authority are currently using Skyscape and are moving to Azure.
13. Is the Authority looking for a mix of front end and back end expertise or a specialist with good expertise in architecture? The former. The Authority are looking for a specialist with experience in working on high transactional systems which is a benefit. A hands-on full stack lead. Knowledge of how to scale up is also important.
14. Is the Authority moving towards DevOps? Yes. We are currently using it and have an agreed SLDC process.
15. The criteria around experience in working with Government in 3 different project environments is restrictive. We will review this for future procurements.
16. Front-end and Back-end - Is this an all encompassing role? The Authority would expect the Technical Architect to have knowledge of both but they may be an expert in one or the other.
17. How valuable is knowledge of the business? This is not essential. We are looking for a skill set and we will educate the specialist on business knowledge.
18. Will these services be going through A GDS panel of Alpha, Beta assessments? Yes