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
Community Members
Community Events
Community Groups

Solution to track Engineering velocity, as well as separate requirements validation process?

I am working on a highly regulated project. After the normal Engineering Scrum process that includes QA, there is a separate team providing requirements validation and this sometimes does not take place until several sprints after the initial Engineering work is completed.

We would like to keep it simple and make use of the same Issues to track both processes, but maintain the velocity tracking capability of the original sprint. Can cards be later moved from Done on a scrum board, to a new status (like ready for validation) on a different Board (likely a Kanban), without affecting velocity metrics?

Any issues found in Validation would result in Bugs sent back to Engineering, and the original User Stories would remain in Validation until resolved.

Is this a feasible strategy, or is there an easier or better way to do this?



Log in or Sign up to comment

Community Events

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

Events near you