How do you deal with product owner who assigns user stories/ tasks to the individual team members?
As part of the Scrum Master’s role, one of the responsibilities is to support and guide the product owner. It is very important that the role of Scrum understands its role and works accordingly. It is the Scrum Master’s job to make the product owner aware of the importance of self-organization when the product owner assigns user stories / tasks.
The Scrum team is self-organizing, so a partial definition of self-organization can be found in the Scrum Guide. Self-organizing teams decide how to perform their work, rather than being guided by others outside the team. Self-management is one of the greatest motivations for people engaged in creative and problem-solving work. Assigning tasks to people is an implicit claim that product owners know better than teams. This not only conveys the wrong idea, but also demoralizes the team while violating Scrum’s values and agile principles-“Point 5. Give them the environment and support to get them done.” Need and trust them. “And” Point 11. The best architecture, requirements, and design come from a self-organizing team. “
Therefore, the product owner assigns work and the Scrum Master intervenes and need to help the Product owners understand the true purpose of working with the Scrum framework and are discouraged from continuing this practice.
