Post on 07-Apr-2020
transcript
13th November 2019
Monitoring affordable homes alphaShow and tell Sprint 3
Our team this sprint
Daria Kwiatkowska
Service designer
Jack Ricketts
Product owner
James Darling
Developer
Alex Yedigaroff
Transformation
manager
Gaz Aston
Lead Designer
Adam Duell
User researcher
● Alpha overview● What we have done● What’s next● Questions
Today
How might we get clear, accurate and live data on affordable housing?
...in order to track the properties through their entire lifespan, to increase the provision of homes for Southwark residents
Alphato build and test a minimum viable product for monitoring affordable homes
● 2 Oct - 16 Oct● 17 Oct - 30 Oct● 31 Oct - 13 Nov● 14 Nov - 27 Nov● 28 Nov - 11 Dec
5 sprints
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5
Goals
Set-up the project, communicate our aims and test our existing concepts
-Develop interfaces for internal users
-begin collection of historical data
-map the necessary process changes
-Develop interfaces for external users
-test approaches to reporting and visualising data
-Develop change history for pre and post completion
-import historical stock and test processes for new stock
-Test the end to end MVP
-agree procedure and date for launching service
Outputs
● Governance set up● Tech stack set up● Comms plan● User research plan● Testing feedback● Plan for obtaining
historical data● High-level user
journeys
● Interfaces for entering details at planning stage
● RP engaged● Service blueprint
showing process changes
● Interfaces for external users to enter address information
● User needs and requirements for reporting and internal data needs
● A service that can report on the accurate position of existing stock
● Processes agreed for new developments
● Service
● Service assessment● An MVP service for
new developments● Recommendations
for next steps, including using external sources for monitoring change
Note: Sprint goals and outputs to be refined and agreed during sprint planning
Sprint 3 goals- Develop interfaces for external users- Test approaches to reporting and
visualising- Develop change history for pre and post
completion
Design review
Core service aims
1. What affordable homes have been agreed?
2. Have developers delivered what was agreed?3. What happened to the affordable homes after they
were delivered?4. Can we monitor all affordable housing?
We cannot do 4 without doing 3 first...
However, we do think we can provide a live service that answers each question in order
Current level of refinement
1. What affordable homes have been agreed?
2. Have developers delivered what was agreed?
3. What happened to the affordable homes after they were delivered?
4. Can we monitor all affordable housing?
Makes all this possible in the future:
● Verifying tenancies and ownership● Tracking landlords● Monitoring and enforcement of airbnb rentals● Non-affordable housing
Usability testing
Testing data entry
1. Enter real data into the system
2. Understand how long it takes3. Identify any usability issues4. Feed into the development cycle
Development work
Coding in the open
https://github.com/dxw/affordable-housing-monitoring
Open Source contributions!
● Developer response form● Dwelling Reference ID
Alpha prototype
Registered providers
Understanding the data
● Sample data from Peabody
● Dummy data to illustrate data fields from their systems
● To understand how housing enters and exits the cycle
What’s next
Research priorities for next sprint
● Explore multi-phase developments and offsite provisioning with the
Strategic Applications Team
● Ongoing work with Peabody to assess audit capability and data entry
● Affordable homes secured outside of S106
● Information for S106 officers
● Evaluate the proposed process with Street Naming and Numbering,
and potentially Building Control
Development priorities for next sprint
● Develop connecting multiple legal agreements to one development
● Tenures/products
● Search
● Changelog microcopy
● Add real user accounts
● Statuses and flows
Thank you!
Questions?