Customer Projects with PBIs assigned/worked to multiple teams (having their own project)

Emilio Gómez July 6, 2021

We manage our customers' projects by creating a Kanban project in Jira Software. There we create a backlog of PBIs (Epics, tasks, subtasks, bugs, etc.) that need to be done for the project. In addition, we use advanced roadmaps to properly manage our customer portfolio/program/projects

Then we assign inside the PBI the value for "Team" field (provided in Jira Advanced roadmaps) so that each team can see in their backlog (each team has its own project) their own PBIs plus the ones coming from our customers' projects.

Considering that some teams work in Scrum and others in Kanban, the issue we've found is that the issue field "Sprint" is blocked as it can only be used for SCRUM projects. This may enforce us to migrate our customers' project from KANBAN to SCRUM which makes no sense as the customer project doesn't have sprints at all (the sprints are in some teams' projects).

 

Any suggestion on how to face this situation as well as other possible approaches to having customer projects and team projects (fulfilling customers projects) at the same time?

Example:

Project: Customer X

  • Task X-1: Team a
  • Task X-2: Team b
  • Task X-3: Team c
  • ...

Project: Customer Y

  • Task Y-1: Team a
  • Task Y-2: Team b
  • Task Y-3: Team c
  • ...

Project: "Team a"

  • Task X-1 (Customer x)
  • Task TA-1 (Team a)
  • Task Y-1

etc.

 

 

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events