Skip to main content

How To Handle Development Team Members That Are Only Needed for Very Specific Tasks and Sprints

Last post 07:34 am June 15, 2023 by Pierre Pienaar
5 replies
01:12 pm June 13, 2023

Hi,

My scrum team will rely on developers with very specific development skills in future sprints for 1-2 sprints in total. For the rest of the work, the regular development team holds all the necessary skills. The development team is not entirely cross-functional. However, I do not think that it makes sense to fully integate the developers with the specific skills from the beginning.

How would you handle this situation? More specifically:

- Would you include the specific developers in the scrum-ceremonies? And if yes, then from which point on and until when?

- What else needs to be considered in this case?

Thanks!


02:35 pm June 13, 2023

My opinion is that if that anyone contributing to the valuable increment is a Developer on the Scrum Team even if it is a short duration. And the Scrum Team participates in all of the Scrum events. Remember that the Sprint itself is an event and they will be participating in that event, so why would they not participate in all of the events? And if they did not participate in all the events, how would their work be transparent to the others? 

I would also suggest to the Developers that someone pairs with those that have specific skills in order to expand the knowledge of the core team. This could help in the future if the work done by the visitors needs to be modified. 


05:05 pm June 13, 2023

Anyone whose industry is needed to help craft a Done Increment is technically a Developer. It doesn't matter if it is required for one or two Sprints or for one or two minutes. Their work is needed, and if they don't share the Developers' commitment, we can expect problems.


09:18 am June 14, 2023

To handle developers with specific skills needed for 1-2 sprints:

  1. Identify the tasks and sprints requiring those skills.
  2. Plan ahead and inform the developers in advance.
  3. Include them in Scrum ceremonies for transparency.
  4. Encourage knowledge sharing between team members.
  5. Define clear roles and responsibilities.
  6. Consider skill diversification for the regular team.
  7. Continuously evaluate and improve the team's composition.

12:29 pm June 14, 2023

I think it would be good to discuss with the Scrum Team how they see those additional developers' participation.

Also, it would be good to discuss with the current developers the possibilities of absorbing the missing skills into the Scrum Team for the purpose of the long-term solution


07:34 am June 15, 2023

Similar to other comments. When the specialised developers join, then I believe they should be full members of the team even if only for a couple of  sprints. The team should be given the capability to self-organisation, or at the very least be part of the discussion.


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.