2021/2: Q4 | Review#6 (2022-03-15 to 2022-03-29)

(the reason we include these is to be open and transparent about when our apps have been compromised, in order to confirm that we’re constantly iterating to improve performance, resilience and security of our Apps.)

We highlighted that we recently had an external review of how we work within the TIS team. From that review, a number of recommendations were put forward for how we can alter things going forward. The whole team is actively working towards implementing these recommendations. As we are a team that at its core believes in transparency and openness, we decided to give you a flavour of what we have been working on:

• We've created and published a Team charter. And we’ve completed initial work on adhering to the team Charter - a soft/supportive approach of using regular team health-checks against the Charter values: Empathy, Unity, Transparency and Collaboration.

• We're reviewing all our meetings and events with a view to rationalising them in the near future

• We're embarking on team training in User-Centred Design: Online, 15hrs over 5 days | On-site at one of our offices, 1 day. Some of the team attended the online GDS UCD training, others are booked to attend in Feb and Mar.

• Progressed work on standardising Job Descriptions / Job Summaries. We’ve identified the need for two roles we don’t currently have in the team: User Researcher and Performance Analyst.

• Debating sensible ways of splitting the team’s work up by Services and Products.

• Started the review of Stakeholder mapping.

• Had an end of Quarter Review and looked forward to Q4.

• Agreed we need to reach out to gain more context for what we do in TIS, within the wider HEE and NHS. And we’ve started having these sessions (one from Jon Howes on PGMDE and another on Digital First). If anyone reading this would like to volunteer to do a session, please let us know!

• Started the process of agreeing standard team events (TIS team meetings, stakeholder sessions etc), and central comms (Teams, Sharepoint, mailboxes, etc), so that communicating within the team is more efficient and communicating with us will be, too.

We really do welcome any feedback you have for us - whether it be negative or positive, or whether it be a suggestion of something we could try/incorporate in a future Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our Reviews themselves! Your contributions to this survey are entirely anonymous, should you wish to include anything others might perceive as controversial. We welcome any and all feedback, as long as it is constructive!