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.
Failure is negative if you don’t learn anything from it. In agile, the goal is to fail early, fast, and cheaply – that way you don’t waste time or money.
Technical Debt is often neglected, but it’s like building a house of cards – eventually, something will give, and it will all collapse.
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
I can’t tell you how many times I have seen Scrum go wrong. If you want the perfect recipe for screwing up Scrum, you’re in the right place.
A company’s culture is like its personality or its soul – it’s an intangible set of unwritten norms and rules that guide how people behave.
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.
Negative feelings and emotions are often the root cause of fearing failure, but sometimes it’s all right (and even beneficial) to fail.
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.
Some people can jump right into the Product Owner role, but for most, training provides an essential foundation to do the job successfully.
It’s a fact: The Product Owner is indeed a member of the Scrum Team. But when the PO doesn’t act like a team member, you’re in for trouble.
Having a vision aligned to the strategy of our product is like having a north star to guide you. Without one, you will probably fail.