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.
There are only three official roles in Scrum, but there’s widespread confusion about the roles and what each one is responsible for.
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.
I have worked with good and bad Agile Product Owners, and I found some sure signs that a Product Owner is doomed to fail. Learn what they are.
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.
Let me begin this blog with the fact that the updated 2020 Scrum Guide changed the term “self-organizing” to “self-managed”. I think this was a very appropriate change because that is what Scrum Teams truly do. They don’t just decide how to work together, they also direct their own work without anyone else telling them …
If you are new to agile or Scrum, then you might want to better understand what a Product Owner is and what s/he is responsible for.