What do you use today instead of Perforce ALM (https://www.perforce.com/products/helix-alm) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Perforce ALM better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Misty Walterneutral

Right now, I'm using Google Sheets for requirements, a basic test tool for execution, and Jira for defects. It's a lot of manual work to tie everything together, especially for audit evidence. Perforce ALM seems like it could automate that traceability, which would be a significant improvement. The main concern would be how well it integrates with our existing Jira setup and the learning curve for my team. I'm not seeing pricing details on this page, so it's hard to estimate, but I'd be looking for something in the range of $50-$75 per user per month if it delivers on its promises.

Simulated interest: 60/100

Edmund Hoegerneutral

Currently, we rely on a mix of Azure DevOps for tracking, Confluence for documentation, and email for test status. The primary challenge is the manual reconciliation required across these systems, which consumes significant time. Perforce ALM could be better if it genuinely streamlines this process, offering true end-to-end traceability without adding more administrative overhead. However, if it's just another tool to juggle, it would be worse. The biggest draw would be a unified system that eliminates manual data consolidation. Pricing isn't detailed on the page, so I can't estimate a maximum monthly payment. I'd need to understand the pricing structure and see a clear demonstration of time savings.

Simulated interest: 40/100

Annika Demutneutral

Currently, I manage requirements in IBM DOORS Next, track work in Jira, and store release evidence in shared folders. These tools, while functional, require manual effort to ensure complete traceability, especially for customer sign-off. Perforce ALM's promise of centralized management and automated traceability across requirements, test cases, and issues sounds appealing, particularly the ISO 26262 certification for our automotive work. However, the integration with our existing DOORS Next setup is unclear. If it streamlines evidence collection for sign-off and reduces manual linking, it could be valuable. My maximum acceptable price would be $100 per month, given my focus on cost-effectiveness and long-term value.

Simulated interest: 60/100

Amaresh Duttaneutral

Right now, we manage our requirements, test notes, and defect logs using Excel spreadsheets and email threads. It's a bit of a manual process, and I'm often the one pulling everything together for client updates. While it gets the job done, it's definitely time-consuming and I worry about missing details or not having a clear audit trail. Perforce ALM looks like it could automate a lot of that, especially the traceability matrix which would be a huge time-saver. The biggest thing keeping me on my current system is the lack of a dedicated budget for new tools; we're saving for a house, so any new expense needs to be carefully considered. I'd be willing to pay around $30 per month if it significantly improved our efficiency and reduced the risk of errors.

Simulated interest: 40/100

Nick Hamillneutral

Right now, we're using Linear and Notion to manage our feature specs, QA sign-offs, and bugs. It's a bit of a manual reconciliation process each release cycle, pulling together product notes, compliance feedback, and support tickets. Perforce ALM's promise of centralized management and automated traceability is appealing, especially for compliance. However, I'd need to see how it integrates with our current Linear workflow and if it adds significant overhead. The biggest hurdle is the budget; as a small startup, every dollar counts. I'd be willing to pay up to $100 per month, but that's pushing it given our runway constraints.

Simulated interest: 30/100

Franklin Effertzneutral

At present, we manage requirements and test links in Jama Connect, and use Jira for issue tracking. My primary concern is the manual effort spent aligning evidence between these systems, especially for regulatory compliance. Perforce ALM promises end-to-end traceability, which sounds promising for reducing that burden. However, I'd need to see how well it integrates with our current tools and if it truly simplifies the evidence alignment process before committing. The pricing isn't clearly stated on the page, so I can't estimate a monthly cost, but I'm generally budget-conscious for our team's tools.

Simulated interest: 40/100

Jalou Hartmanpositive

Right now, I'm using spreadsheets for acceptance criteria and GitHub Issues for bugs, then manually compiling all the release evidence. It's quite time-consuming and definitely prone to errors. Perforce ALM sounds like it could streamline things significantly, especially the traceability aspect, which would be a huge win for our customer pilots and supplier reviews. The idea of having requirements, test cases, and issues all linked automatically is very appealing. What I'm unclear about is the pricing model; it mentions USD per month subscription, but there are no specific figures on the page. Given my current budget constraints and the manual nature of my work, I'd be willing to consider paying around $50-$75 per month if it truly saved me the hours I currently spend on manual compilation and reduced errors.

Simulated interest: 75/100

Soline Francoisneutral

Currently, I manage requirements traceability, verification records, and change requests primarily within Polarion. I also use spreadsheets and manual methods for certain aspects. Perforce ALM seems promising for centralizing these activities and providing end-to-end traceability, which is a significant challenge given the volume of data. The ISO 26262 certification is also a notable benefit. However, I'm concerned about the potential learning curve and integration with our existing processes. I would need to see how it handles our specific supplier interactions before considering a commitment. I would be willing to pay up to $50 per month, based on the subscription pricing model mentioned.

Simulated interest: 40/100

Lai Joshineutral

Right now, we're managing our projects using the free tier of Jira, supplemented with Google Sheets and shared docs. It's functional, but honestly, it feels a bit like juggling chainsaws sometimes, especially with client feedback loops. Perforce ALM sounds like it could really streamline things, particularly the automated traceability it mentions. That would be a huge improvement over our current manual processes for tracking issues and test status. What I'm unclear about is the pricing structure – it mentions USD per month subscription, but no specific figures are given. If it's anything like the enterprise tools I've seen before, it might be out of our budget. I'd be willing to consider paying up to $50 per month, but only if it truly solves our current pain points and doesn't introduce new complexity.

Simulated interest: 50/100

John Manteneutral

Currently, my team and I rely on DOORS for requirements management and Word templates for test procedures and defect evidence. This is a manual process, requiring significant cross-referencing. Perforce ALM appears to offer integrated traceability and automated workflows, which would be a considerable improvement, especially for our compliance reviews. The key concern for me would be the integration with our existing systems and the learning curve for my team. We value stability and proven processes, so any new tool must demonstrate clear benefits and robust support. I would need to see a detailed cost breakdown before committing. For now, I am not willing to pay for this product.

Simulated interest: 30/100