The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We want to create a roadmap for feature development with Portfolio. Our feature workflow is split into two phases/stages which have been set up in Portfolio:
Stage 1: Discovery (Skills: Design, UX)
Stage 2: Implementation (Skills: UI, Engineering)
The resources within the feature teams have the necessary skills assigned in the team view.
What Portfolio does, and I don't understand why, is splitting up the stages: a part of the first stage (Discovery) is scheduled for the first sprint, then a part of the second stage (Implementation) in the next sprint, followed by another work package for stage 1 and stage 2 in later sprints. (see image: stage 1 is red, stage 2 is blue).
Is there a way to enforce that stage 1 is completed before the next stage is being scheduled?
Thank you,
Mark
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events