Best Approach for managing a Story When Multiple Teams are involved

[Vikrant Yadav]

Hi Agile Expert and Scrum Master,

In our current org,R&D team is using a single Story which move across different team like Design, QA, Dev, UAT and due to this workflow is very complex,because issue is moving in different team so different workflow status like Design in Progress, QA in Progress etc..

Kindly help me with the best approach, how to handle tasks or work for each teams. 
I am not sure how they are estimating the issue and managing in board. 

[Nikola Perisic]

Hello @Vikrant Yadav 

Are you using Teams where you can create teams such as Design, QA, Dev and more. You can distinguish the tickets based on Teams with quick filters and based on that you can easily switch between the tickets for different teams. You cannot assign tickets to Teams, only to individual members of the team.

You can check the estimation technique that they are using if you are a board administrator by going to Board settings -> Layout -> Estimation, or you can check one of the work items. If story points field is populated, they are using story points. If the part of original estimate is being prefilled they are using original time estimate. If both, that is not a good sign.

[Vikrant Yadav]

Hi @Nikola Perisic  Thanks for your response!

I am not using Teams. 

Teams are creating a single story and the Same Story is moving across all the teams like Design >> Development >> QA >> UAT .. 

In the single Story there are multiple Story point field like QA Story point, Dev Story Point and Design Story points. Estimating using these Story poins

Is it a correct method( Single Story method ) of tracking task for each Teams? 

What is the best approach ? 

[Nikola Perisic]

Hi @Vikrant Yadav 

Story points are usually given by developers, not the designers and the QAs. If this is the case, then this is a bad practice which will cause arguments between these teams. Personally, I never heard that QAs and designers are defining the story points. This is something that developers do in Scrum.

[Vikrant Yadav]

@Nikola Perisic  That's why I am asking, what is correct process of managing tasks ?

[Nikola Perisic]

@Vikrant Yadav 

I would say:

• Only use Story Points standard field - no additional fields
• Each of these teams are having different tasks based on their roles - create new boards for each team
• Create quick filters that would be suitable for each team and enable them on each board
• Make sure there a transition between the statuses, there needs to be a process of moving issues from one status to the another