Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

distributing the roles between development team in scrum

Last post 06:01 pm December 20, 2021 by rick midlton
5 replies
09:48 pm December 17, 2021

Good evening
Suppose that we have a project where there are two systems, legacy system that was made by Team A, and a new system that's done by team B and is intent to replace the legacy one..
the legacy system has many web service that were made by team A.
There is a Business analyst in Team B to gather the requirements; and there are some developers to develop the New System.
Both of Team A and Team B are at the same place.
my Question is:
if there's a WEB SERVICE in the legacy system; and one developer of Team B needs to understand its logic and steps; does that developer has the right to ask the Business Analyst to go the the Developer of Team A and ask him about the logic of that web service whereas both developers are at the same place?
why doesn't that Developer B go to the Developer A that 5 meters away and ask him whatever he wants?!!


05:27 pm December 18, 2021

There is no such role as BA in scrum.  Scrum only has three accountabilities, the SM, PO & Developers. 

The Developers consist of many cross-functional members, and are the ones who are committed to creating any aspect of a usable Increment each Sprint. 

There is absolutely nothing stopping a developer from one team talking to a Developer from another team, as this type of dependency would be mentioned either during Sprint Planning or at least during a Daily Scrum once the relevant PBI had started to be worked on. 

Now, if the organisation prevents Scrum teams from talking to each other, then this should be treated as an impediment which would cause the SM to become involved if the Developers could not resolve it themselves. 

Why do you think a BA has authority over a Developer? 

Also, if the teams are smaller enough, they could work as one team instead, as even though Team B will be creating a modern version of the product that will eventually replace the legacy one, having both teams work together will ensure that Team B will know how the legacy system works as this may help them when creating the new one. 

 


06:23 pm December 18, 2021

There is absolutely nothing stopping a developer from one team talking to a Developer from another team

 That's right; but the developer thinks this is from the job of BA to talk to Team A developers to get the BUSINESS RULES of the web services; then explain these rules to him again!
the problem (as I think) is that Team A developer thinks that any thing regarding the business rules must be done via BA!; I think that the rule of BA in general should be with the end users, and any thing regarding the code should be via the developers


08:34 pm December 18, 2021

if there's a WEB SERVICE in the legacy system; and one developer of Team B needs to understand its logic and steps; does that developer has the right to ask the Business Analyst to go the the Developer of Team A and ask him about the logic of that web service whereas both developers are at the same place?

Of course he has the right to ask. The other team member also has the right to say no and to point out he is 5 metres away and could ask himself.

Perhaps it would be best for team members to consider the responsibility they have to collaborate well, and to make best use of the networking potential afforded by a small team size.


10:33 pm December 18, 2021

The other team member also has the right to say no and to point out he is 5 metres away and could ask himself.

That's what happened :)

many thanks for support 


02:00 pm December 20, 2021

Thanks for this information! Really interesting.