Question for Ken or CST - > Cross-functional teams
Hi All,
I saw related topic already - https://www.scrum.org/Forums/aft/1863#10015 and a lot of other discussions witting another resources.
Will be appreciate for the answer from a certified Scrum trainer. Ideally it's interesting to know what exactly Ken thinks about this :)
"Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity."
Does it mean that in team SHOULD be at least one cross-functional member?
Thank you very much!
Scrum never say that the member should be cross-functional. It is the team that must be cross-functional.
Cross-functional team is not the same as cross-functional member. Does that make any sense?
Posted By Joshua Partogi on 23 May 2016 12:24 AM
Scrum never say that the member should be cross-functional. It is the team that must be cross-functional.
Cross-functional team is not the same as cross-functional member. Does that make any sense?
I see this get misinterpreted everywhere!
The key thing here is whether the "team' still considers itself cross-functional when one of their team members is unavailable for any reason (vacation, ill, leave company, etc).
The team can consider itself truly cross-functional if they have the expertise to complete work despite the absence of a technical or business expert on the team. If this is not the case, it is a vulnerability that the team needs to work on to mitigate (i.e. - cross-training, knowledge transfer, pair programming).
=> "truck factor" or "bus factor" ;-)
Think of teams as being cross-functional and of individuals as being cross-skilled. You need the former in order to create an increment without impediment, while there are potential efficiencies to be gained from the latter.
But it is more that just the "bus factor" that drives the need for cross functional teams.
The variability of complex work can mean an unevenness of work. You don't know everything about the what to do, or how to do it until you start actually implementing. Even when you try your best to create an evenness of work, one sprint may be dominated by database work, the next by work in the front end, the next by work in the service layer. In the first sprint most of the team pitches in on the unexpected database work, the next most of the team works on the unexpected front end work, the next most of the team works on the unexpected service layer work. That is why you want a cross functional team, in which its members are cross trained. For each sprint most of the team member will work on that one thing that often unexpectedly dominates.