Whilst there is often a technical implementation of the agile principles for software teams, at the core of each lies a choice and a behavioural change.

For example, as well as choosing to use automated testing to ensure the intended quality, teams can choose to talk to customers more frequently to see how their product is used in practice.

They can choose to focus on fewer items of work to improve overall speed, and choose to hold themselves accountable for that.

They can choose to try and continually improve, and leaders can choose (or not) to allow their teams the autonomy and empowerment to do so.

Nearly all of the hundreds of ‘agile’ techniques that software teams have used to change their ways of working for the better are transferable.

Tech teams will often implement a technical solution because their material requires it, but the underlying principle always has an equivalent for other domains.

These principles have been used in hospitality, marketing, finance, education, policing and even wedding planning.

This is Agile Beyond Tech.