How to dig out of Technical Debt
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
My clients ask: “How do we deal with Production Support issues in Agile when our Scrum Team supports both the product and its development?”
Ideally, your Scrum Team includes full-time people with the right cross-functional skills; but if you have part-timers, you’ll have problems.
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
There are many problems and struggles that can occur between Product Owners and their stakeholders. Thankfully, most of them are avoidable.
In Agile, defects can be handled in different ways – so what should you do when you discover a bug? Find out how to handle defects in Agile.