One of the rules of the Scrum states the team should self organize and be in control of the technical part of the project. It is rather easy when Product Owners are delivering tasks which every member of the team is capable of dealing with. But there are some cases when it became more complicated, for example:
- When it comes to deciding on architecture of the project it is noticeable that one of the team members is much more experienced, so democracy in decision making in such area is maybe not the best idea. (or such team member is brought to the project especially because of previous problems with architecture)
- Some products are designed for specialized group of people. Product Owners have the knowledge about functionalities they want to introduce and how such features should look like, but each task needs also a legal advice on it's subject. Probably legal advisors should be introduced to the team.
I could bring more examples if needed but you get the image...
So my question is: "How does specialization fit into Scrum?"
and "How to introduce work of specialists into tasks taken by Scrum team?"
My thinking is:
When I throw task at the team they should be capable of doing it. If they do not have all the knowledge, technical skills or competences needed then such task should remain out. Introducing specialist to the team only in order to handle such tasks would probably create botle necks and is rather a fake solution to the problem.
So how to fit them properly into the team?