Beta – Sprint 10 Show and Share

How are we at the end of sprint 10 already!? As usual, we have made some good progress over the past couple of weeks and achieved our sprint objective.

Work completed in this sprint:

  • Built MVP remaining pages 
    • Identify repair – Lighting (Bathroom)
    • Identify repair – Shower (Bathroom)
    • Identify repair – Toilet (Bathroom)
    • Identify repair – Electrical (outside)
    • Identify repair – Garage (Outside)
    • Identify repair – Electrical (outside)
  • Reworked MVP pages to align with prototype v4
  • MVP testing & feedback (core team)
  • Set up monitoring & alerting
  • Presented to DLUHC – Continuous funding application panel
  • Preparation for next phase, working with Newark and Sherwood
  • Fixed bugs 🐛

MVP work

All the branches of our repair identification are now complete, with over 120 possible journeys leading to 63 different schedule of rate codes, covering our most commonly reported non-emergency repairs.

The MVP now accurately reflects the prototype, and also includes new iterations based on our last round of user testing.

Funding application

We had our interview, following the submission of our application, to continue funding with DLUCH. We felt the presentation was well received and are now awaiting the decision, so please cross your fingers with us, so that we might get the opportunity to carry on this great piece of work.

Our key objectives if we receive the funding are to:

  • Create API layer to integrate with housing management systems. This offers the potential to remove any manual steps for staff, and could also enrich the user experience by identifying the property tenure, utilising any flags that may require paired attendance or highlighting where a property may still be under guarantee.
  • Allow the option to amend or cancel a repair – importantly without requiring a login
  • Provide the ability to log communal repairs
  • Offer valid repair options to leaseholders

With this functionality, the options for reuse by other councils is increased. This would allow for greater adoption potential with the ability to log these repair types, in addition to the functionality already available.

Monitoring and alerting

The developers have added the ability for the system to report issues detected across the API’s used and potential server issues. These notifications will ensure that we can closely monitor and resolve any issues detected.

This could be something simple such as an invalid API call based on user input, to something more sever, such as a wide impacting server issue.

Show and Share

Why not check out our show and share and catch-up on the full detail.