This week’s summary:
The Newly Awarded contract
Made Tech has won the tendering bid to extend the MVP for Manage Arrears. This week, we met to discuss the objectives, resourcing and planned our Inception workshop which will be taking place on the 9th September.
Over the past few months, we have been preparing the backlog ahead of the newly contracted team joining. During Made Tech’s first week with us in September, we will be bringing them up-to-date with backlog and projects development.
User Testing feedback (Case Details page)
We summarised last week’s user feedback. The testing re-highlighted the users’ passion, “As an income collection caseworker, I need to see the Payment history and Arrears Actions diary on the same page so I can assess and understand what is going on with a case at a glance and initiate the appropriate action.” The users all listed their preference in order which we will share with the developer in a couple of weeks. They all had very similar preferences.
This week we discovered that GOV.UK Notify invoice by Organisation rather than by service area. I’ve started looking into if they will be changing this in the long term and how/if other Councils recharge individual service areas.
Show and Tells
Manage Arrears show and tells, will recommencing from 11th Sept 2019 and will continue fortnightly through to December with updates on the project’s progress.
1. Inception workshop 9/9/19
2. Show and Tell 11/9/19
This week we welcomed +Lia Tarar to our team, by inviting her along to our RAG (Red, Amber and Green) rating and priority scoring workshop. Lia is a Junior Developer, with Ruby skills and is a lovely addition to the team.
The outcome of the RAG rating and priority scoring workshop was interesting. The aim of the session was to show the product owner and the rents team how the different aspects of the scoring fitted with the RAG and the message flow. We found that our Product Owner would like Red cases to reflect top priorities P1s. Amber cases to reflect P2s. And the Green cases to remain as they are which is to reflect lower arrears cases which will generally be handled through automation. The outcome was interesting because this approach simplifies the existing rules for Red and Amber cases in the system.
This week, we also user-tested, the improved case details layout designs with the Income Collection team. Testers generally shared the same comments. Based on their feedback we have a clear idea of how features can be adjusted to increase the usability of the system. We plan to amalgamate the preferences into one design which will be shared with our UX/UI consultants and the developers joining in September.
Next week we will be:
- Collating the User testing, case details layout designs feedback.
- Updating the message flow based on the workshop feedback and preparing the automation stories in the backlog.
- Continuing to find solutions to the Hackney API/ Hackney action diary bug.
This week has been a positive and productive week, for Manage Arrears. We have;
*Shortlisted Digitalmarket place bidders, and reviewed their proposals for Phase three. The outcome will be published shortly.
*+Trish Hadden shared some positive feedback relating to service charge arrears. Last month the team saw a huge reduction, approximately by 10%, in their arrears which is a result of their arrears letters being sent. Contributing factors from our project include;
- The improved content redesign of the letters
- The improved accuracy which comes from the bulk sending feature providing the ability to provide and send accurate and timely information.
*Many thanks to +Cate McLaurin for assisting with discussions around the Letter before action (LBA) and Ministry of Justice (MOJ) conversations. The Letter before action is a 14 paged letter sent to Lessee has part of the Service Charge escalation policy. We are investigating the possibility of an alternative solution to enclosing paper forms. Which will determine how these letters will be handled e.g. via Gov Notify.
*Also many thanks to +Carolina Gaspari for providing +Elaine Geeves and I with advice and guidance on UI and UX design. We learnt a lot. Particularly relating to simple tips about making use of lines and space and grouping text. We have since adjusted the layout of our wireframes to reflect the advice. Our Product owner was shown the example of these and he is in full support of us user testing these with his team next week.
Next week we will be:
- User testing case details layout designs with the Income Collection team
- Working to resolve the Hackney API/ Hackney action diary bug.
- Continuing to finalise LBA stories.
This week +Elaine Geeves and I aligned the new Manage Arrears prioritisation scoring adjustments up with the Manage Arrears Message Flow which will be used to automate communications and the RAG which categorises the cases. We will be sharing this with the wider income collection team shortly, to ensure everyone has a shared understanding of how the three fit together. Many thanks to +Elaine Geeves we needed this!
The important cases with high priorities will be correctly positioned and no cases will fall through the gaps. The good thing that came out of this exercise was that no major changes are required to make the three elements work together.
We also shortlisted the Digital marketplace applicants for Phase 3’s business case this week and last week we said thanked and goodbye to +Guy Whitfield, the Senior Delivery Manager on our project.
As mentioned in the previous week notes, the business case for Phase 3 includes a few key workstreams. Our focus for next week will be finalising the finer details in the two areas below:
1. Letter Before Action
2. Case Details Layout
Letter Before Action (Leasehold Services Team’s arrears letter)
Amending the ‘Letter before action’ and adding it into the system will benefit both the Lessees and caseworkers. We will be meeting with Team leads to discuss options and agree its format for the next phase.
Case Details Layout
We will be working on prototypes to capture the layout improvements in the backlog with the aim to obtain feedback from the users in the following week. The outcomes of both will be attached to existing cards in our backlog helping to ensure they are clear and stories are ready for the new team for Phase 3 join.
Project: Property Licencing Software Metastreet
The property licencing software, Metastreet, has been in place for almost one year now. It is providing Agents and Landlords with a way to complete online property licencing applications and a way for back-office staff process these.
Recently, we have experienced a few challenges with progressing some of our development features/bugs and there have been a few deployments concerns. To address these Metastreet has agreed to provide release notes for each deployment and assured us that they are reviewing and testing their coding before releases.
To help ensure our bugs/features are being prioritised correctly, over the past few weeks, we have been working with the PSH team to review and update our Metastreet’s roadmap. This week +Guy Whitfield ran a well-received workshop with the PSH team which mapped the process before Metastreet was introduced, and the new existing process post- Metastreet. It encouraged the team to see the differences and shared their Likes, Lacked, Learnings and Longings.
It highlighted, that although the Metastreet software enables applicants to apply and pay for a private sector licence and for the team to issue licences, there are a number of workarounds that officers are doing to make the system’s workflow work well for them. These gaps will feed into the roadmap which we plan to follow-up with the Metastreet providers.
In addition to the above we now have a local government Metastreet user group. The first official meeting is on 5th August 2019 and involves Islington, Waltham Forest, Haringey and Slough. The aim is to share and identify common challenges to help build a better service.
Next week, Metastreet are due to release a new major enhancement will allow officers to issue invoices and refunds. It will make the reconciliation process a lot more easier for the team as Metastreet’s report should match Stripe’s output.