Select Page


Build the design to meet the ultimate goal

Identify the ultimate goal

The ultimate goal is the thing that is most important to the customer. It’s the reason we’re making the thing in the first place, and the way we know what success looks like.

The Digital Services Architect is responsible for defining the ultimate goal with the customer/product owner. They will do this before any work begins, with the Business Analyst for support.  

Find out what your ultimate goal is as early as you can. Then ask yourself continuously, is our work helping the ultimate goal?

The delivery section of the playbook has its own ultimate goal –  to share our practices and proposed delivery game ‘plays.’ Doing this will mean that we provide a consistent approach to our customers and a repeatable process to get our own team to the finish line.

Agile methodologies

We find that compared to waterfall development, agile projects are far more likely to deliver on time, budget, and having met our customer’s need.

We use this iterative, fast-paced style of software development to reduce the risk of failure.

We want to get working software into users’ hands as early as possible to give the design and development team’s opportunities to adjust based on real user feedback.

We’ve tried these ways of working and found that using most of the practices most of the time improves the quality of our work and happiness of our team.

Be consistent, not uniform

One size does not fit all and never will.

We’ll always iterate on this section, because we’ll always explore better ways to get things done. But now, when we’ve found one, it’ll be recorded here. And once it is, it’ll be the way we do things until we find something better, and write it down.

Agile tools

Agile planning

Agile methods

Run a retro

Version control

After delivery

How the live phase works

Measuring and reporting

Retiring a service