Hackney Re-Platforming Weeknotes : week ending 2020-01-10

Weeknotes are a way for us to keep people informed about progress on the project. Given the technical nature of the re-platforming work we will use them to explain technical choices that we are making, including the benefit and impact of these choices. 

Project goals

  • Enable housing officers to use MaT offline when there is poor mobile coverage
  • Enable Hackney to decommission Outsystems, saving £80,000 per year
  • Enable Hackney to support, develop and deploy future improvements to MaT more quickly, at lower cost

Sprint goals:

The goals for Sprint 5 are to:

  1. Replatform all of the Tenancy and Household Check and Homecheck frontend (including save and return)
  2. Do testing of offline functionality within the team
  3. Have all APIs in place and integrated with the frontend (including image persisting and S3)
  4. Connect the React frontend to Outsystems
  5. Get in a position to where we can release Tenancy and Household Check and Homecheck to a group of Housing Officers for further user testing with users by 3rd Feb

Good things

Building processes is now quick and easy. Emma has been able to make good progress in a short space of time, having only really started this week. Chris even managed to build 14 steps in a single day, which is great. This bodes well for Hackney’s ability to build more processes in future. 

Decisions we’ve taken to deprioritise certain tasks has really helped the team. Before Christmas we decided to postpone both the Service Assessment and the cautionary contact development work. This has helped us keep focus.   

We have 2 more API endpoints in place – Create (POST) and Update (PUT). This means that we can start plumbing the front end in, and ensure that the processes work offline. 

More Hackney colleagues have started to join the team. Emma, Tuomo, Bukky and Anna are getting increasingly involved. A successful handover means making sure that the wider Hackney team understands and can maintain the updated service, so this is good news.

Decisions

Approach for going live. Based on Gill’s guidance we decided that the best approach will be to release the updated service to a small group of housing officers throughout February, to thoroughly test offline working ‘in the field’. This should get us into a position where the updated service can be released to the wider team in March. This will be led by Hackney colleagues, rather than dxw.   

We have decided not to replatform the Introductory Tenancy Visit process during this final sprint. Given how quickly processes can be assembled, this is something that can be picked up by Hackney once we finish this phase of the project. We are discussing with Emma how we can potentially use this as an opportunity to test our documentation and make improvements to the forthcoming front end playbook.     

Difficulties

There is a lot to build and to test in this final sprint. We would have liked to test the offline functionality much earlier, but this hasn’t been possible. We’re making this a priority early in the sprint. 

We often come up against blockers or issues that we haven’t spotted far enough ahead. Although we have spent time this week thinking about the “known unknowns” that might cause us problems, we’ve often been hit by things we didn’t anticipate. Given the small amount of time we have left we need to minimise disruption to get everything done. 

We still have some UX/technical decisions to make in the final sprint. We need to make sure that things like post-visit actions and manager review are set up properly. These aren’t big tasks, but we do need to resolve them early on.  

Acknowledgements

Thanks to everyone who worked on the project this week – Bukky, Chris, David, F, Gill, Liudvikas, Mirela, Richard and Tuomo.  

What’s next

We are now in the final sprint of the project. Over the next week we will be:

  • Rattling through the remaining Tenancy and Household Check steps
  • Making sure that Manager Review is set up properly
  • Connecting the React processes to Outsystems
  • Clarifying the user journey for post visit actions

The following people will be working on the project:

  • Ana
  • Bukky
  • Chris
  • David 
  • Gill
  • Liudvikas
  • Lorraine
  • Mirela 
  • Richard
  • Tuomo

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.