Defining outcomes as a product team

How defining outcomes can help a product team collaboratively discover, identify, collate and rank what they should do and enable them to perform effectively and happily to ensure outputs are tied to those outcomes.

Documentation should meet outcomes too

How do we go beyond seeing documentation as a burden and ensure that it is maintainable, reliable and valuable? Documentation is necessary to explain how something complicated works and defines a critical process to ensure a successful software release.

Connecting loved ones: building the NHS Book a virtual visit service in 48 hours

The simple digital service enables ward staff to book in calls which we hope will reduce the burden on staff having to do this manually and reduce the number of calls to wards from loved ones. From the loved ones perspective they receive an SMS stating when their virtual visit is booked for and receive a unique link to join the call when the ward is ready.

9 Benefits of Test Driven Development

Test Driven Development is the practice of writing a test for a piece of required functionality, before writing any implementation code. This test should fail when first run, and then, you write the code to get it to pass. It doesn’t have to be the most perfect code, just so long as the test passes. Once it does, you can then safely refactor your code.