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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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