Putting patterns to work

Posted by Gareth Evans . Nov 30.23

We’ve published a new case study that shows how we’ve used patterns to implement a flow-optimised ‘Delivery Ecosystem’ for a fintech client.

Patterns are critical to our work. They’re solutions to typical challenges we observe across our clients – challenges that are common to specific sectors, business domains and technology functions. More importantly, they’re also the improvement actions we need to take to solve these challenges.

Over the years, we’ve learnt how to combine patterns to work in balance in a delivery ecosystem. Patterns can be applied to improve technology, tooling, technical practices, team topologies, architecture, ways of working and specialist skills – all with the goal of accelerating the flow of value to your customers.

We know, however, that using patterns in a point solution won’t work if they prove suboptimal for the system as whole. Which is why, in almost all our engagements today, we act right across a value stream and use patterns which work synergistically to transform outcomes from concept to cash.

We’ve developed our thinking on this and have been putting it into practice for well over a year now. We call it a ‘Reference Ecosystem Implementation’.

Software Delivery Ecosystems comprise social networks that rely on skills, technology and processes to work in balance to accelerate the flow of value to customers through software products. Value flows through – and relies on – interconnections between human and technical elements.

We start by building a ‘reference’ ecosystem for a client based on a flow-optimised set of patterns encompassing architectural style, technologies, tools and practices. The ecosystem is also designed to ensure teams are able to innovate with fast feedback to create an optimal learning experience.

Over time, the ecosystem forms the basis for new teams and value streams to accelerate value to customers and help meet business objectives.

There’s no ‘templated’ solution here. Crucially, the first phase of any engagement is always experimentation. Experiments identified in the discovery process will be undertaken to gain confidence that proposed tools, patterns and practices will work together as expected to form the delivery ecosystem that works uniquely for the business – one that will be relevant, adaptable, long-lived and constantly evolving.

We prove the value of this work through positive changes in Flow Metrics and how those changes help meet business OKRs.

We’ve also found that as we help clients scale delivery ecosystems across other business domains and the teams that work in them, people engagement improves dramatically.

Our new case study has much more on our approach to implementing Delivery Ecosystems and the outcomes we’ve achieved for a fintech client. If you want to hear more about what we can achieve for you, don’t hesitate to drop me a line.

Gareth Evans

Gareth Evans

Co-founder of HYPR, our chief engineer and solutions expert and one of the first fully-certified SAFe® Programme Consultant Trainers (SPCT). Above all, Gareth is a fantastic technology mentor to our team.

More Ideas

our thoughts

Open for business. In Australia

Posted by Justin Tomlinson . Nov 27.23

After working across the Tasman to develop a nearshoring model, we’re delighted to announce HYPR’s formal entry into the Australian market.

> Read