Imagine that there is a user story-1.
There is a UI team A and Backend team B.
User story-1 has a total of six tasks (3 in UI and the other 3 in the backend)
How will I make sure that the same story collaborated between A and B. dependent tasks and velocity of the story, etc.?
This goes against what Scrum / Kanban suggest i.e. a team should be able to do all the required work, which is why you're up against this issue. Ideally you should be combining the teams or have each team made up of some UI and some backend people.
Assuming that you're not going to change the teams, are all stories like that with some UI and some backend subtasks? You can add a component or label to each subtask which differentiates which team it belongs to, then add a swimlane for each team or quick filters for each team.
Essentially I think you'll find that the teams are effectively working as one team, otherwise you're not going to achieve your goals.
Yes, I agree with the theory of Scrum/ Kanban. I have learned it that way. But, Unfortunately, we follow a different way of doing things.
I learned, form your comments that there is no direct implied scheme in JIRA for doing things in our way. It's fine.
Thanks for answering my question.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events