So, you think you’re agile? It always surprises us the number of companies that claim they’re ‘agile’ when the facts suggest otherwise. They claim to be agile without fully realising the benefits they would achieve by this. It’s not even clear if their implementation of agile understood. Agile (or more importantly a lean agile mindset) enables you to assess your operational and development value streams for your organisation and implement a lean operating model which enables you to better deliver value to your customers - at the pace and of the quality they demand.

Identifying areas where your organisation’s implementation of agile is not delivering value can be difficult, however, there are common behaviours and symptoms that can be observed that highlight that you may not be quite as agile as you thought you were.


Testing operates in a separate team from analysis and development

You still have silo thinking

When moving to an agile way of working, the mindset of the team must be on delivering the best product for your customers. This is a change in approach for your people, where their objectives will previously have been based on their role - Analysts analyse, Developers develop and Testers test.

Now the objective is delivering the product the TEAM are responsible for, using everyone’s skillset at all stages throughout the development of your product. Shared responsibility and ownership of the product, as a team, is key to delivering frequent, quality releases. Your product team should be made up of all the key skillsets that ensure the focus is on delivering quality products for your customer.

Pressure to meet delivery dates compromises the quality of your product?

You are not working close enough with your customer

As the technology footprint and usage of your product increases, the ability to accept and adapt to change is essential.

Implementing the right agile framework in your organisation ensures change is embedded in everything your organisation does. The team’s focus on customer value means your product is likely to go through many iterations before it fully meets your customer requirements.

Frequent and regular system demos with your customer (or proxy), and absorbing their feedback means that your product is refined to ensure that the course can be changed quickly to ensure the released product is aligned with customer expectation.

As team’s focus on customer outcomes, so must your organisation’s leadership. This demands a mindset from the top of the company that understands that fixed delivery dates must be replaced by putting trust in your teams to deliver the right product for your customer.

Difficult to predict and measure progress?

Difficult to predict and measure progress? – You’re not using the power of data generated from your team

Whilst agile devolves decision making and ownership to your teams wherever possible, it doesn’t necessarily provide you with visibility of progress at a all levels where you need it.

This is often obvious when, despite your teams claim to be agile, your sprints still contain ‘mini-waterfall’ processes which only identify product issues through testing late in the sprint.

Through the correct implementation of lean and agile processes, in combination with appropriate platforms and tooling, your teams will be better equipped to have a consistent real-time view of your progress status. In addition to this, an understanding of estimation using story points and program increment planning, enables your wider organisation to see where features will be delivered and better plan for releases.

At the team level as testing is embedded through all stages of the process, you will have access to a real-time view of your product build quality. This provides faster feedback to your team on the quality of the product and issues can be addressed quickly to ensure sprint commitments can be met.

Releases are large and require significant manual support

You’ve not planned well enough for it!

Whilst the thought of releasing a new product may be a big deal, the process to release it shouldn’t be. When time has not been invested in identifying and implementing a clear path to live, releases can become delayed by issues due to differences in configuration, environments, data etc. The gains made within your agile team to accelerate release of your product are lost navigating the issues you uncover in your release process.

Repeatable and automated release and environment management process will better support your delivery pipeline. The ability to utilise live-like environments and deploy your product consistently reduces any significant overhead spent on test data and environment issues.

In combination with automated checking and exploratory testing, your agile team can build, deploy and test faster. An automated deployment process ensures the steps and checks conducted to deploy to test are followed all the way to production meaning your team can focus on verifying the product with confidence that the release process is sound.


Often organisations implement agile as a layer over their existing operating model, ‘cherry picking’ elements of agile to minimise disruption, and do not achieve the value and efficiencies agile and lean thinking can bring. By ensuring your people, process and technology is in place that TRULY enables your teams to deliver value quickly and consistently, you’ll then realise the benefits that being agile can bring.