“How well is your delivery team doing?” That seems like a straightforward question for an Agile team, but it is more complicated that it might sound at first. Do we know what it means to “do well” or is it one of those things that is different to everyone?
The book Executable Specifications with Scrum by Mario Cardinal starts with a strong statement: “This book aims to solve the recurring challenge encountered by many software development teams: They do not build the right software.” This is an ambitious goal, especially when you want to achieve it in a little bit more than 100 pages.
Do you have a nagging feeling that your Scrum team may not be investing in building the right thing? Do your products have features that are rarely or never used? Does it take your organization the full investment of building and launching a product to validate an idea?
After many years of working with Agile and being a witness to its results, we found the main mistakes (the dark side) that usually come up when implementing this methodology. Take a look at some of the reasons why Scrum fails within the software development projects.
There is often a vacuum between the company vision and the final outcome of software development projects, causing late validation and low value. This vacuum is present in pretty much all companies, caused by a wrong and ill-conceived product delivery approach.