Jonathan Waldheim: March 01, 2021
It has been a while since we blogged about our work on the Recommended Summary Plan for Emergency Care and Treatment (ReSPECT). That’s because we’ve been working hard to re-platform the system on to a new infrastructure, while also simultaneously upgrading to version 3.0 of ReSPECT, released by Resuscitation Council UK in September 2020.
Now that we are well on our way to releasing in NHS Forth Valley, this week we are doing a series of blogs and videos about this work.
These won’t be long reads, just a bitesized view of what we’ve been up to!
ReSPECT week: what to expect
Today (Monday) we will be talking about roadmaps, tomorrow (Tuesday) it’s a video question and answer session all about the user groups we need to work with next. On Thursday, our Interface and Interaction Designer, Laurel will give us a whirlwind tour of how we used a Design Sprint to tackle the problem of drafting forms digitally. Friday, we will have a look at the new User Interface!
What is a roadmap?
As part of our continued development of the digital ReSPECT, we have to think about what we are going to do next, why it is worth doing and how we are going to approach it.
One of the best ways to do this is to create a Roadmap. The Government Digital Service describe a Roadmap as: “A plan that shows how a product or service is likely to develop over time. Roadmaps need to be easy to understand, and simple to adjust when priorities change - as often happens with agile ways of working.”
It is often less the map, plan or visual and more the discussion which it yields that can enable the most progress. With that in mind, we’ve put together a roadmap to help have that conversation.
What's on our roadmap?
This is the roadmap we use to plan our future work internally.
Based on the needs of our users in NHS Forth Valley and our commission from the Scottish Government, it sets out the next pieces of work in sequence and is broken down to a level where our engineering team can plan for the quarter.
It is focused on the product, the ‘thing’ we are making. It isn’t a project plan because it doesn’t have set dates and we can react to demands, resequencing items when necessary.
We use a tool called Miro for this Roadmap, an interactive whiteboard which I encourage you to have a look at and leave comments on it here.
Think about what features you might want the application to do in the future, or even ask questions about items already on there!
Categories of roadmap items
Items are segmented in to five categories: Explore, Design, Technical Design/Discovery, Technical delivery, Rollout.
Items can float between these ‘swimlanes’ and as you’ll see, items are often closely linked together. Here’s a rough description of what these mean to us:
Looking at this Roadmap, you’ll probably be keen to find out what we’re planning for after March. We’ll talk about that in the coming days, so keep reading….