Best Approach for managing a Story When Multiple Teams are involved

Question

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 · Answer

@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

Vikrant Yadav · Answer

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

Nikola Perisic · Answer

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.