At Seilevel, we updated and re-published our Requirements Management (RM) Tool Study this past year, looking at over 150 tools and over 200 criteria. We did this in phases with the subset of tools making it though each phase getting smaller and smaller until we ran 21 tools through the full evaluation criteria to rank them. This tool study is a great resource if your company is looking to implement an RM tool for the first time.
But what about if your company already has an RM tool in place or has multiple that you need to decide between? The tool study report doesn’t really address how a company can look at their current tool or tools to see how they compare and if they would meet the needs of the company. You could, of course, just take the total scores and ask which one is higher or how your tool’s score ranks, but that doesn’t necessarily mean that the tool you have in place wouldn’t be “good enough” for your company’s purposes.
So, what does it mean for an RM tool to be “good enough.” Well that depends. It depends on what your requirements methodology emphasizes and what is important to ensuring you minimize the risks to your projects through the use of the tool.
Because “good enough” varies from company to company, I took our RM tool study and categorized each of the 200+ criteria into one of ten categories, or features. With these features, I then created a capabilities dashboard that shows a heat map of how each of the top 21 tools fared in the 10 features as a percentage of the total points available in that feature. With this view, you can either find or add your RM tool and see how it compares in specific categories to the other tools we evaluated to determine if the tool you have is “good enough” for your process.
The 10 features are:
- Requirements Specification and Prioritization: Can you add, edit, delete and prioritize requirements easily?
- Traceability/Dependencies: Can you create relationships between requirements and change the data model to reflect the traceability needed in your organization?
- Stakeholder Management, Review and Collaboration: Can you give feedback on requirements or initiate workflows to approve requirements?
- Change Control: Can you baseline requirements, track changes after a baseline or revert a requirements set back to a baseline?
- Visual Modeling: Can you create and edit models in the tool or link requirements to visual models?
- Import/Export and Reporting: Can you import/export to and from Word, Excel, Visio or other sources and can you report on the requirements, models or subset of either group?
- Requirements Process Support: Can you set up your own templates and object types to support a methodology with things like checklists, issues, risks or constraints?
- Task/Iteration Management: Can you track development tasks on requirements, set release or iteration dates or create agile burndown charts?
- Licensing, Support and Tool Administration: How flexible is licensing for the tool, are there adequate support materials and how difficult it is to maintain the tool?
- Scalability, Integrations and Ease of Use: How intuitive is the tool, can it scale and what integrations does it offer?
With these ten buckets, the heat map is shown below (click to expand). Typically, you would want to narrow in on a few tools or a few features. For example, if you know you have JIRA in place today, but Traceability and Dependencies are the most important feature to your organization, you would see that JIRA only received 60.4% of the total traceability and dependency points. Or if support of visual modeling and requirements process is most important to your organization, you might narrow down your list to TopTeam Analyst, Modern Requirements Tool Suite and Blueprint.
With this view, you can add one more dimension to your RM tool quest and maybe answer the question of “Is our RM tool good enough?” If the answer is yes, you have the heat map to socialize that message and if the answer is no, you can use this to help build the case for a new RM tool.