Forget About Features, Prioritize Key Results

How will your software development landscape change with this simple shift?

Prompted and edited by the Author

What if I told you that a federal agency in the US attempted to contract software development using the waterfall methodology and failed, would you be surprised? Probably not, right? But it didn’t just fail; they even lost a lawsuit against the contractor who delivered exactly what was requested. But here’s the twist: learning from their mistake, they switched to Agile. So, they created a new contract, renewed monthly to review deliverables. Years later, they still ended up with something they didn’t need. And failed again. Surprising? Maybe a bit. So, how did they fail despite continuous reviews? That’s what I aim to explore in this article.

And here lies the problem.

How is it possible to review deliverables every month, not to mention practicing Agile, and after a few years, realize what you have is not what you wanted?

Breaking down Scrum.

Let’s start with something simple and well-known. Without a doubt, Scrum is the most widespread and applied Agile framework in software development.

Scrum is a framework designed to facilitate team collaboration. It breaks down the development…