Re-engineering Hackney Content: Show and Tell 16/05/19

See how happy everyone is?

Thanks to all who came to our Show and Tell this week. Our big news is we:

  • moved to WordPress API
  • launched five pages to live for Libraries
  • started to design the nagivation
  • added HotJar to gather feedback
  • started pulling together metrics

Dive into the details in our slides.

Extending Repairs Hub to RCC agents – Show & Tell 14/05/2019

The Repairs Hub (RCC) team has been working together in the Unboxed office on Fridays, which has made it easier for everyone to focus on user stories and making progress on key development tasks. Our work last week focussed on:

  • Integrating Keyfax, a response management software
  • Raising a repair under the RCC agent’s name
  • Integrating contractors’ diaries
  • Talking to the Neighbourhood Contact Centre team to understand if we could reuse some of their work to manage contact information.

We also had our show & tell on Tuesday 14th May, where we talked about all of the above and demoed some of the new features.

Weeknotes: Network redesign and implementation for webfirst project WC: 13/05

Where we are
We entered our sprint 6 – which is our last sprint of this information gathering and learning phase.

Last sprint: Sprint 5
Sprint 5: 30/04/19 – 14/05/19, our goal was to complete the setting up of all the exercises and activities that we had planned for our testing, learning and information gathering. So we ensured that the final parts of the test lab for testing new devices was up and running and the user surveys were all sent out to our users in in our test sites and begin to chase users to ensure we collate as much of the response as possible.

This Sprint: Sprint 6
This is our agreed and official last sprint of the learning, discovery and information gathering phase. The ultimate goal is complete all tests – network devices testing in the lab and in the user network; user experience and site analysis in preparation to enter our design and exploratory phase.

Looking ahead
The team is excited and enthusiastic about entering the next phase. a lot of learning has happened over the last 6 sprints, and we are keen to begin to interpret all the data that we have collated and start turning them into tangible, meaningful network design. We are bursting with the potential possibilities that we’ll uncover and and how we might make sense of all of them to satisfy our user needs and high level design.

What have we learned
Liked: We have enjoyed prompt responses from our various potential suppliers. All our potential suppliers seem to be enjoying working with us in an agile way.
Learned: We have learned that collaboration and knowledge sharing is indeed awesome! We have enjoyed collaborating in a multi-disciplinary team in achieving technical and non-technical tasks specifically around delivering and setting up network switches for testing in our lab and on the network.
Lacked: Our communication to the world outside our team hasn’t been as good as we would have like. So we’ll ensure that we are working with our product owner to ensure that we are telling the wider ICT and the organisation about the things that we are doing.

Everyone has been amazing. so special thanks to +Henry Lewis +Isaiah Oketola +Chidi Oko +Shafiq Ahmed +Gillian Newman +Mal Morris and +Lindsay Rex

Star of the sprint, will be shared between +Isaiah Oketola, +Chidi Oko and +Shafiq Ahmed for all the hard work including working out of hours to get our test sites surveyed and device testing all set up! You guys are really awesome!!!

Verification Hub: Weeknotes 15/05/19

We’ve been working this week on the spec for the development required from Farthest Gate to bring the Verification Hub in to the parking permit verification process in Liberator. In the first instance, it’ll be (after testing in the test environment) put in front of the existing verification steps including the current Citizen Index. This means we can watch how the VH performs and tweak our matching rules without creating any unnecessary extra effort for either residents or parking staff. We’re still not sure when Farthest Gate will be able to prioritise the work so we may have to consider pausing the project until we get the work scheduled in.

Matthew Keyworth and Tom Clark have managed to successfully connect and authenticate the API to the new ClearCore 5 web service but are still working through the search, possibly because some field names have changed between version 4 and 5.

Steve Farr continues to work to automate and clean up Housing Benefits and housing tenant data to bring it into the VH hub. Our testing has shown we’re already hitting around 57% verification based on Council Tax alone and we’re confident that the inclusion of these data sets will push that up considerably.

Creating a Job Description Register – weeknotes

Good afternoon all,

We ran two User Journey mapping sessions:

HR Business Partners: We created a persona ”Gloria” who is a HR Business Partner,  wants all the documents to be available for review and fairly evaluate the Job Description to grade it.  We created a User Journey Map of the Job evaluation process. There are 4 main steps within this process: ‘Receipt of Job Description and Questionnaire’, ‘Review the documents’, ‘Evaluating the Job Description’ and ‘Implementing the decision’. We captured what each Business Partner was doing, thinking and saying/feeling.

Business Managers: We created a persona ”Mohammad Hussain” who is a Business Manager, wants to easily create a Job Description with guidance given by the HR Business Partners, so that he can get the grade for the Job Description. They want to make sure that the finalised version is stored into an agreed location. There are 5 steps within the process of creating a Job Description: ‘Identifying the need’, ‘Scoping out the role’, ‘Creating a Job Description’, ‘Job Evaluation process’ and ‘Finalising the Job Description’.

From the sessions’ outcomes, we came up with the User Needs (as below). We presented them to the Business Managers and HR Business Partners and ran User Needs Prioritisation Workshop. The prioritised User Needs are highlighted in ‘Yellow’.

Business Managers User Needs:

‘Having building support’  

‘Gathering a business case’

’Managing my time’

‘Getting Sign off’

‘Create a role that’s fit for purpose’

‘Support from others’

‘Process’

‘Consistency in JD Storage’

‘Finding out the result of Job Evaluation’

‘Job Evaluation’

‘Organisation Structure’

‘Job Families’

‘Where do I find the Job Description template’

HR Business Partners User Needs:

‘Understanding context’

‘Understanding the actual changes being proposed’

‘Process’

‘Resources’

‘Managing expectations (the outprocess)’

‘Do I have enough info/is there sufficient info to progress?’

‘Transparency in outcome’

Where is the current JD?

‘Understanding the actual changes being proposed’

‘Managing my time’

‘Ensuring fairness’

‘Have a clear Job Evaluation Process’

‘Scoring methods’

‘Organisation structure’

‘Questionnaire’

‘Storing, versioning and linking Job Description with Job Evaluation’

‘Communicating the outcome of Job Evaluation’

Next week, we will let you know about how we have created User Stories based on these prioritised User Needs. We will also discuss how we used MoSCoW to prioritise the User Stories. Thank you for reading.