ClearHub attended the recent Government ICT 2.0 event in London alongside Atlassian, where openness and teamwork were key themes of the day. This post takes a look at how the public sector uses technology to empower teams, and how the Criminal Justice System in particular is benefiting from Atlassian Jira and Confluence Data Center.
Many of the challenges faced by government and public sector organisations are unique. These organisations deal with highly sensitive information at a scale far beyond the majority of private businesses; this alone brings a series of challenges around security and data protection.
Like any organisation, though, government bodies are made up of teams of people. It’s not only important that the technology and tools being used are secure – they also need to empower those teams to work together, as in any business.
The value of people – both internal teams and external users – was apparent throughout the talks at Government ICT 2.0. Paul Brewer, Director for Digital & Resources at Adur & Worthing Councils, stressed this in his talk on digital transformation in local governments, where he identified design, people and technology as the three main pillars of digital transformation.
“Flexible technology and common capabilities are necessary to build end to end digital solutions. Team capabilities and human-centred design are key to a successful digital transformation, and new technology forms the foundation.”
– Paul Brewer, Director for Digital & Resources at Adur & Worthing Councils
Technology for teams
Your choice of IT is what facilitates digital delivery.
This was Paul Brewer’s message throughout his talk, and nowhere was this more clearly demonstrated than by the work of the Criminal Justice System. Mark Giles, Digital Operations Manager, and Carl Storey, PMO Planner, gave a presentation at Government ICT 2.0 on how HM Courts & Tribunals Service and Crown Prosecution Service are working together to establish the Criminal Justice System Common Platform:
To create a single (“common”) digital platform across the Criminal Justice System (CJS) based on user needs, unifying and transforming the criminal process.
Criminal Justice System Common Platform: The challenges
The planning and management of the development and delivery of a solution like this is not without challenges. These challenges broadly fit into those three pillars as outlined earlier by Paul Brewer.
People
The Common Platform is being built for a wide range of users, including those within government and the civil service, legal professionals, and members of the public.
This is why creating a “common” platform, whilst a challenge, was so important, to bring all these different areas together.
As Mark Giles said in his talk, “Tools are only productive if the policies, processes and people using them are effective as well.”
Tech and design
The challenge for the Criminal Justice System wasn’t just around choosing the right software for the planning and development of this platform. This was, of course, an important starting point – the legacy tools they had been using weren’t collaborative or flexible enough to meet the new requirements.
The other challenge was around the correct configuration and deployment of software. Not only did they need to guarantee high availability, but they needed to be able to guarantee the security of data and be able to meet regulatory requirements, and it needed to be designed with users first
The case for digital business change
At the beginning of this joint venture, HMCTS and CPS were using tools like Word, Excel, email, and shared drives. This would often mean it was difficult to achieve a good level of visibility over work, particularly with two departments now working together. These tools were often high maintenance, difficult to access, and information often ended up out of date. It meant that to create the reports that senior management required, it was a time consuming and very manual process.
It was time for a newer, more agile solution – one that would empower change across business teams, not just in IT.
Atlassian Jira and Confluence: A single source of truth
In adopting Atlassian Jira Software and Confluence to manage the development of the Common Platform, the Criminal Justice System was able to provide one single source of truth thanks to the close integrations between the two.
Confluence, for example, aids daily phone calls between teams, acting as a hub for relevant information. Participants in disparate teams can access this page, and it brings together links, discussion points, related Jira tickets.
Jira tickets, meanwhile, act as a way of tracking not just tasks, but assets, risks, actions, dependencies, and even the people on different programs.
By moving work to Jira and Confluence and taking advantage of the close integration between the two tools, the Criminal Justice System was able to achieve a much higher level of visibility. This, combined with the flexibility of these tools, helped considerably in efforts to break down the silos between teams and aid collaboration.
Migrating from Atlassian Cloud to Atlassian Data Center
Atlassian Data Center
The Criminal Justice System knew from this first stage of the project that Jira and Confluence were the right tools – but what about the setup?
When considering this, the Criminal Justice System elected to migrate from Atlassian Cloud to an Atlassian Data Center deployment for a number of reasons.
Data storage and privacy – government directive to host data within the EU
Increased functionality – Atlassian Data Center offers more functionality than Cloud software
Resilience – Atlassian Data Center offers high availability and zero downtime upgrades
The migration from Atlassian Cloud to Data Center was a large scale project for the Criminal Justice System, so they worked with Clearvision to design and implement the project as smoothly as possible.
As an Atlassian Platinum Solution Partner, Clearvision’s consultants are experts in digital migration. Our teams are more than familiar with the requirements and regulations of government IT, as one of the first Atlassian Partners to be listed on the G-Cloud digital marketplace. We were able to work closely with the Criminal Justice System to understand not only how they currently use Jira and Confluence, but how they need the software to perform moving forward.
“Clearvision’s onsite presence, technical skills and calmness proved invaluable for a quick migration with minimal disruption.”
– Mark Giles, Digital Operations Manager, HMCTS
The migration was a success:
Users logged off at 4pm on Friday and back on at 8am on Monday
Opportunity to move to Azure hosting and review Atlassian apps with Clearvision
Confirmation testing took place on the Sunday evening, leading the most issues being resolved
Delivery continued with many users unaware any maintenance had taken place!
Post-migration timeline
Six problems by 15th June (largely due to firewall settings)
Just two problems by 30th June
0 problems at the end of July
The results
Thanks to having the right tools, policies, processes and people in place, the Criminal Justice System has seen a number of tangible benefits.
Single source of truth
Easy to configure, change and improve
User friendly
Identifies bottlenecks
Encourages collaboration
Drives quality
That combination of the right people, processes and tools was invaluable.
We know that the management, development and delivery of any digital solution is complex. When it comes to government ICT, this is more true than ever.
The Criminal Justice System was able to achieve the above results by leveraging the help of Clearvision’s consultants. As the longest-accredited Atlassian Solution Partner on G-Cloud, Clearvision has been delivering specialist services to the public sector through the G-Cloud framework since 2013.
Browse our offerings on G-Cloud or get in touch to discuss how we can help your teams with a successful digital transformation.
ClearHub 2024 © All rights reserved | Privacy Policy | Trust Center | Modern Slavery Statement | Cookie Overview
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_BHWFTMS5QE | 2 years | This cookie is installed by Google Analytics. |
_gat_UA-91023414-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
TawkConnectionTime | session | Tawk.to, a live chat functionality, sets this cookie. For improved service, this cookie helps remember users so that previous chats can be linked together. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
_hjSession_1670766 | 30 minutes | No description |
_hjSessionUser_1670766 | 1 year | No description |
_referrer | 1 year | No description available. |
_utmz_cf7 | 1 year | No description available. |
AnalyticsSyncHistory | 1 month | No description |
li_gc | 2 years | No description |
popForm | 1 day | No description |
twk_idm_key | session | No description |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |