JIRA has traditionally been used as a bug/issue tracking tool, but has anyone used it for Requirements Management and especially Traceability throughout the lifecycle? I am thinking of extending the use of JIRA to capture requirements as well (with the use of the new EPIC and STORY issue types - though our project is a hybrid and not truly Agile), then convert to Development & Configuration tasks, Testing, Releases etc. We may have Word, Excel as detailed requirements docs as attachments in JIRA, but I am envisioning having the one-liner requirements as individual entries in JIRA. Any insight into this type of approach would be appreciated. Thank you! Saving Changes...
Anyone use JIRA for Requirements Traceability? Saving Changes...
John ReilingSeeking new opportunities | AcroVision Business Systems, Inc.Mendham, Nj, United States
Yes, I am on a project where this is being done. Usage varies across scrum teams, but developers are regularly using the whole suite of Atlassian tools, which includes JIRA. Our thought is similar to yours - use the hierarchy of EPIC and STORY, and maybe even extend it down to task. The tool looks to be geared to support this. We are looking to possibly create some custom fields to trace upward to higher level reqts or capabilities. Saving Changes...
Thanks John. Since I first posted my questions, we were able to make progress on the process design. We are also planning to go with additional fields, as well as some workflow customizations Saving Changes...
Kelly McDowellBusiness Analyst| ASGNaples, Fl, United States
Have you had much luck with this approach now that's been in place a few months? Our company has been using Microsoft Project but are looking to transition to JIRA Saving Changes...
I setup the requirements in JIRA, but the project was put on hold. We did not begin executing on the solution, so I don't have any practical lessons from that. If you have questions on the setup, I can try to answer. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I have not yet incorporated into our process yet as we are looking into using TFS as our ALM. No need to ramp up on a new tool to simply change.
Good Luck Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Our company is also looking at using Jira for agile projects. I look forward to reading about people's experience. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
We currently do utilize Jira for our agile work. It works very well for that. Easy to use, ability to @mention team members, flexibility, and built in reporting. Also capable of saving and sharing filters, bulk actions, and exporting. Saving Changes...
We recently used JIRA on an Agile project. We had User Stories as Story items which had Acceptance criteria. Tasks and defects were linked to the User Stories. We also had an electronic scrum board in JIRA. You may also want to review Confluence. Saving Changes...
