In this scenario I have a fictional business project called “Gazelle”. Gazelle has a cast in stone deliverable of a product to be delivered on a specific date a few years down the road. It also has touch point deliverables along the way to the end, e.g., customer milestones, functional prototypes, or testing results.
Gazelle has a team of some dedicated SW, HW, and Mech engineers, but much of the work comes from functional teams as needed. E.g., a HW engineer is needed to layout a PCB that may require involvement in ½ of one sprint and is then returned to the pool to work on other projects.
I have my thoughts on this but would like to hear other expert opinions on how this is handled, particularly in the realm of automotive.
One area that I struggle with is what is the best way to handle the related tickets most efficiently without duplicating any. E.g., The Gazelle team creates a ticket in the Gazelle Jira project for the example I used above, “Layout of a PCB”. This issue must be tracked in the Gazelle Jira project as it is committed to in the sprint, but also needs to be in the backlog of the “HW_Functional_Team” Jira project. What is the opinion here of the best handling of this?
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