4 ms·
JIRA had R4J plug-in that is pretty good if using jira doesn’t upset you. I’ve used it and it works nicely. You get traceability “for free”. There’s additional
by rubidium 5y ago
JIRA had R4J plug-in that is pretty good if using jira doesn’t upset you. I’ve used it and it works nicely. You get traceability “for free”. There’s additional plugins to enable testing so you can do full requirement to test in JIRA (along with work breakdown if you like that sort of thing). I like JIRA for this because you can put all the conversation about each one in the comments. Gives extra color to the reasoning.
JAMA is a great tool I demoed but couldn’t get the org to buy.
Doors is crap.
I recommend word/ excel if you have <60 requirements. If you have more than a tool like above helps, esp if you need to have traceability to testing.
- sam_bristow 5y agoI've used JAMA at 2 companies so far. It's a bit of a mixed bag. There are parts of it that are great, and parts that are an absolute nightmare. In a lot of ways JAMA is like Jira - your experience is hugely shaped by how well it's been set up for you at the start.
- requirementyogi 5y agoHave you tried our plugin, Requirement Yogi (on the Confluence side), and if you have, can you share how you would position it on the market, especially compared to R4J for example?
- ijustlovemath 5y agoWhat were the major pain points for you guys? I have a med device startup, and JAMA's automatic document import, traceability matrix, document versioning, and general scriptability put it FAR ahead of similar offerings like Greenlight Guru. We don't have it deployed though due to cost, so I'm curious to know the major problems people have with it.
- ware_am_i 5y agoHey, I’ve done dozens of similar implementations within Med device companies. Happy to chat -> chris@medlaunchnow.com