Scrum Team characteristic
Hello All, Scrum team are cross-functional and self-organizing. From Dev Team perspective I can relate this quality with the work they do. Can someone explain this characteristic with reference to Product Owner and Scrum Master's work ?
The Product Owner's and Scrum Master's skills and focus are not the same as the Development Team's. So, for example, by adding the skills to identify market demands (Product Owner) and skills in helping teams be more effective and efficient through self-organization (Scrum Master) you have added two cross-functional skills to the Scrum Team.
Another way to look at this is that each role in the Scrum Team has a different focus and purpose. By having all 3 roles working together you are creating a cross-functional, self-organizing team.
Cross-functional means more than front-end/back-end/full stack or Java and Python.
Scrum team are cross-functional and self-organizing. From Dev Team perspective I can relate this quality with the work they do. Can someone explain this characteristic with reference to Product Owner and Scrum Master's work ?
Perhaps this quality can be illustrated by its absence, which raises certain challenges. Scrum Masters and Product Owners are generally assigned to Scrum Teams by the "higher ups". The team itself will often have little influence on this, and will not be fully empowered to inspect and adapt the implementation of roles.
Team members cannot then fully self-organize to improve their cross-functionality under changing conditions, at least with regard to the structural concern of who fulfils the role of Scrum Master or Product Owner. Stability in these matters is important, but membership should not be immutable or beyond the team's remit to improve.
Another point of view is about who decide who will do "this stuff" for the whole Scrum Team.
Some "stuff" (user interviews; refinement ; facilitation...) can required skills not only in the hand of the Product Owner ; the Dev Team or the Scrum Master like explain by Daniel.
Because of the spread in skills and because of any time constraint and any motivation, the whole Scrum Team can decide who will facilitate the next event (not only the Scrum Master) ; or go and talk with actual users next week (not only the PO) ; "write" the PBI related to this new customer segment (not only the PO)...