Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,199
Community Members
 
Community Events
184
Community Groups

Jira "Business-Based" Projects interacting with Jira "Functional-Based" Projects

The setup:

  • Jira Project: Gazelle (A Scrum project running in 2-week sprints)
  • Jira Project: Software (A “Functional Group” Scrum project running in 2-week sprints, but with issues that span across many “business projects”, Gazelle being one of them)
  • Jira Project: Hardware (A “Functional Group” Scrum project running in 2-week sprints, but with issues that span across many “business projects”, Gazelle being one of them)
  • Jira Project: Mechanical (A “Functional Group” Kanban project, but with issues that span across many “business projects”, Gazelle being one of them)

 

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.

My thoughts:

  • Gazelle uses Jira Components such as “SW_Functional_Team”, “HW_Functional_Team”, “ME_Functional_Team”.
  • Gazelle uses FixVersions for the stake in the ground for touch point deliverables along the way to the end, e.g. customer milestones, functional prototypes, or testing results. These are shown on the Advanced Roadmaps Plan instead of using MS Project.
  • The Gazelle Product Owner plays a big part in the prioritizing of the Gazelle backlog, but also participating with other POs in prioritizing the backlog for the functional groups with the functional leaders. This helps shield the engineer from the battle of what is the most important business project.

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?

1 comment

Any thoughts here would be greatly appreciated. Many companies I feel come across this dilemma. 

Comment

Log in or Sign up to comment