How to Avoid Role Confusion on Scrum Teams
There are only three official roles in Scrum, but there’s widespread confusion about the roles and what each one is responsible for.
The Agile Product Owner role on a Scrum Team is THE key to success. Check out this blog collection covering the skills and traits necessary to succeed.
There are only three official roles in Scrum, but there’s widespread confusion about the roles and what each one is responsible for.
Negative feelings and emotions are often the root cause of fearing failure, but sometimes it’s all right (and even beneficial) to fail.
In this subseries’s third and last blog, I tackle the final five ways that Product Owners should not behave. Watch out for these behaviors.
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.
The Product Owner is the most crucial member of a Scrum Team, but there are some problematic personality traits & behaviors to watch out for.
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.
There are many ways requirements can go wrong in Agile. In Part 2 of 4, I tackle five more requirements anti-patterns so you can avoid them.
The problem of Agile requirements going wrong is endemic; this is the first 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.