Comprehensive Software Reviews to make better IT decisions
Don’t Let a Tool Vendor’s Research Spook You
Tool vendors love to promote research as part of the product marketing campaigns. While there can be valuable insights in their reports, a tool alone will not fix a broken practice.
Jama Software recently published a report written by engineering.com that declared:
“Despite the increasing complexity, only 15% of respondents relied on a dedicated requirements management system. This was either causally linked or a likely factor in the following reported negative outcomes:
- Production outcome failures (83%)
- Reprimands by a regulatory agency (62%)
- A minority reporting they feel they effectively manage requirements (34%)”
Whenever you find a report like this on a software vendor’s site but not on the author’s it smells like research for hire. In this case though, these are not surprising results. IAG’s landmark 2009 study on requirements management maturity clearly identified that requirements management maturity was more important than your delivery method to project outcomes.
Apart from its age, the IAG report also suffers from one fatal flaw when it comes to selling software. They found that, “Forcing analysts to use a tool enforces a set of practices and standards on the organization that can be productive. In cases where the implementing organization uses the tool as a catalyst to also improve other areas of requirements capability, the activity can be seen as highly productive – and significantly impactful.”
The requirement that their customers need to do more than buy and implement the tool is a barrier to the sales cycle. As a purchaser, you need to make a significant investment in your business analysis practices and practitioners in order to get the benefits from tools such as Jama as well. This is not to say you shouldn’t invest in a tool, just be prepared to invest in the practice development and training required to build a better business analyst.
Want to Know More?
- Info-Tech’s Transition to Product Delivery, Build a Product Roadmap, and Build a Strong Approach to Business Requirements Gathering have the information and exercises to help you define the practices you need to complement a product or requirements management tool implementation.
- Explore Seven Reasons You Need a Data-Driven Approach to Application Lifecycle Management.
- Are you a Jama user? We would like to hear your feedback on your experience with the tool on SoftwareReviews!
Blueprint Software integrates financial services regulatory requirements into its core platform for easier traceability.
ALM Works Structure for Jira enables Atlassian customers to track and manage projects at scale.
Build out your collaboration tool chain to include diagram and design capabilities. An image is worth a thousand words in a requirements document.
Too many teams are “doing Agile” and mistakenly think that interactions over comprehensive documents means no more requirements. That may be true in a world of “Badgile,” but not when Agile is executed properly.
ServiceNow’s New York release extends the visibility, transparency, and collaboration capabilities today’s Agile and DevOps teams need.
Intake and backlog management are two of the top reasons for failed product and feature delivery. Skop.es brings the analytical and management practices to visualize, quantify, and verify and validate the delivery of the right requirements.
Application portfolio management (APM) is typically characterized as a subset of application lifecycle management (ALM). However, we see this capability included more often in enterprise architecture tools than in ALM software.
Atlassian’s Jira remains a popular collaboration tool for teams looking to improve work coordination. However, it requires third-party add-ons and integrations to support end-to-end artifact traceability and product delivery. Zephyr fills Jira’s test management capability gap.
The immense sprawl of products and product versions across the organization complicates manual inventory collection practices. Automated discovery and inventory tools help alleviate this challenge, but they do not negate the importance of end user and stakeholder collaboration and application capability mapping.