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?
What happens when a Product Owner doesn’t have control or even visibility into the product’s budget? No one will know if it’s successful.
In blog two of three, I cover five more ways a Product Owner on a Scrum Team should not behave. Watch out for these behaviors or traits.
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
If your Product Owner used to be a developer or has a technical background rather than business experience, you may run into a few issues.
There are many problems and struggles that can occur between Product Owners and their stakeholders. Thankfully, most of them are avoidable.