Hi everyone,
As an associate Jira product owner, I have been working with my team for a year now. We are eager to establish Jira as the system of record for our requirements. Our primary goal is to ensure that Jira serves as the central source of truth for all our requirements.
To achieve this, we recognize the need to accurately capture the timeline of when each requirement is added to the application, as well as any instances when a requirement is replaced, written over, or superseded. This accurate timeline will help us maintain a clear understanding of the history and evolution of our requirements.
Furthermore, it is essential for us to have the capability to trace the linkage of each requirement to the code repository. This ability will enable us to establish and maintain proper requirements traceability and strengthen the connection between our requirements and the associated code changes.
By implementing these features in Jira, we aim to enhance our requirement management process and ensure that Jira becomes the go-to system of record for all our requirements.
Are there any teams out there with similar use case? how is this achievable?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.