Blog / Agile Principles

What if the stakeholder can't work in an agile way?

Many projects do operate in a non-agile way. What happens to them? Most fail.

If we agree that software development is unpredictable, and we agree that this means we need to deal with stakeholders in a different way, what do we say to stakeholder who refuse to work in an agile way?

Well, countless projects do operate this way. What happens to them?

Well, the vast majority of them (estimates range from 50 to 80%) fail in one way or another:

  • They run over schedule
  • They run over budget
  • They are full of bugs
  • They get cancelled before they’re completed
  • They are released, but with a very limited scope
  • They are released, but fail to meet the needs of the intended user
Share this

Related Content

So do you expect me to write a blank check?

If we don't know when a software project will be done, how do we know if it's worth the investment?

Ask 10 people, get 15 answers

Ask 10 people what "Agile" or "DevOps" means, and you'll get 15 answers. The terms have essentially become meaningless.

My preferred "Agile framework" for a new team

Work closely with the users of the software, and establish tight feedback loops. No framework necessary.