How to manage requirements in Jira Cloud

[@thewiklunds9942]

This video needs more love. Really nice!

[@vasupodagatla393]

informative content

[@FIshyfaceify]

Hey! Thanks for the video. Would you trace these requirements to user stories and their acceptance criteria? Or is this a different process.

[@agile-innovations]

Great question. Yes, I like to link requirements to the user stories (or other relevant backlog items) that created or updated them. It's good practice to update your requirement specification as part of the 'work' of implementing a user story (backlog item). Part of that update is linking the new or updated requirements to the backlog item that impacted them. Here's another video I posted that might do a better job explaining this: kzbin.info/www/bejne/oHW9qmqwebd8hMU

[@matsl.178]

Good video! One question: where do your stakeholders write general requirements (before a product owner or a business analyst work on them). Do you have a separate board / issue tool for this?

[@agile-innovations]

Good question! Yes, there are lots of options for this. One option is to maintain a separate project/board for stakeholder requests. This is nice because you can implement separate workflows for vetting requests or even turn on Jira's voting feature for stakeholders to vote on each other's requests. Another option is to manage incoming requests in another tool. If your company already has a ticketing system, it might make sense to manage requests there. And I think the new Jira Product Discovery (JPD) tool could be useful for this, too. Sorry, this is a difficult question to answer without more context about your situation. But it seems you already have the right idea. 🙂