Skip to main content

Supporting distinct skilled team members

Last post 06:32 pm February 7, 2021 by Ian Mitchell
1 reply
05:23 pm February 7, 2021

Situation - 

Team members consisting of Data scientists , Front end developers & Dev Ops. Take it as a group of I shaped people in a scrum team. Of course T shaped team members would have been ideal. But with this team its difficult as the skills are little more diverse at least with a presence of data scientists. Moreover its not easy for other members to learn it (in order to support) plus personal motivation in learning new distinct skill is another point here. During refinements team forecasts the work / size the PBIs & usually sizing is done by the members who can accomplish the work (eg: FD unable to estimate or size for DS & vice versa). But at the end there is a product goal and all these skills are needed to create the integrated increment. Each sprint team works to create increments in line with product goal. These increments can be integrated or can be non integrated ones depending upon the Goal. 

Now problem with this cross functional team is that they are not able to converge until the work needs integration. Therefore, the work is executed in parallel by particular skilled members (silos). Dependency is high in this case and with no influence or support within members generally there are spillovers. We are thinking on the lines of early integration of work or introducing CI/CD. But are we looking at the one side of the coin only ? Is there something else we can also try ?

If you been in similar situation , what you & your team did ? Any success/failure stories or insights , suggestions are welcome. :-) 


06:32 pm February 7, 2021

But are we looking at the one side of the coin only ? 

Yes, but automation is usually the lowest hanging fruit, tends to be cheap, and is likely to increase predictability as well as introducing efficiencies. Unless you have reason to believe you will just end up doing the wrong thing quicker, there is usually little sense in delaying automation.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.