You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My company is moving towards more agile development but we still have some waterfall type methods too. We are using Jira software standard cloud version.
We have several groups (teams) that collect ideas (stories) and then prioritize them, assign them to a BA to research and gather high-level requirements. This process is over some time period (not a sprint).
Once they are done if the story needs development it goes through the typical Jira process of development for our dev team(s).
My question is: How to organize the work to best track it, track the team's progress for the Discovery phase then continue that issue onto the Development phase to monitor and track the delivery team's efforts.
How do others do this? What options might we use?
Would the discovery teams have their own Jira project (kanban) and once that phase is done the story is moved to another team for the delivery phase using (Scrum)? Is that moving the story from one project to another or is there a way to duplicate the story and add it to a backlog for a delivery team?
As I said, there are multiple teams that do Discovery work that ultimately feeds into a delivery teams backlog for development.