When your Agile Requirements go Wrong, Part 4
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
The Scrum Master is a servant leader to a Scrum Team, who teaches, coaches, and advocates for agile within an organization.
In the fourth and final blog in this series on what happens when Agile requirements go wrong, I tackle the final four anti-patterns.
The problem of Agile requirements going wrong is endemic; this is the third of a four-part series on what can go wrong, and how to fix it.
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.
What happens if you have an uncommitted Product Owners? When a Product Owner isn’t interested, available, or engaged, you are in for trouble.
Product Owners are inherently leaders. To succeed, Product Owners must navigate every level of an organization, from the Help Desk to the CEO.
Agile teams are fully cross-functional so they can create a done increment each sprint. But what does that mean? Explore the official roles.
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.
So, can you add items to the Sprint Backlog during the Sprint? The Scrum Guide states that you can, but you may not want to do it. Learn why.
Can the Scrum Master be a Developer on a Scrum Team, too? Join me in exploring why (or why not) a Scrum Master could have these dual roles.
Sprint 0 is a hot topic amongst debated by Agile practitioners. So, should you have a Sprint 0? Check out these arguments for and against it.