Microsoft Excel is a spreadsheet application available as part of Microsoft 365 (Office 365), or standalone, in cloud-based and on-premise editions.
$6.99
per month
OpenText ALM/Quality Center
Score 9.1 out of 10
N/A
OpenText™ ALM/Quality Center, formerly from Micro Focus, serves as the single pane of glass for software quality management. It helps users to govern application lifecycle management activities and implement rigorous, auditable lifecycle processes.
I don't really know another program as powerful as Excel. I've used Google Doc programs but do not feel they come close. So far, anytime I've needed a table of some sort for data, whether it's budget oriented or information off a survey, the best system has been Excel. We do web audits on occasion and we create an Excel worksheet featuring every URL of the pages we're auditing, notes, data about the content, information about files attached to the page and other information to help us determine what pages need updating, deleting or otherwise. We also use Excel primarily to export our Google Analytics to in order for us to create reports for clients that need to see specific information about their traffic.
For an organisation that has completely adopted SAFe structure including naming terminology, it is less appropriate and apart from that. It can suit any organisation out there, and it can solve all your problems one way or another by customising it. It is a robust and highly scalable solution to support all the business needs. It improves a lot of productivity and visibility.
It is very good at embedded formulas and tying cells to one another
It allows me to compare deals terms on a side-by-side basis and talk my clients through it easily.
It is very helpful as well in terms of allowing me to filter/sort results in many different ways depending on what specific information I am most interested in prioritizing.
If you have a mix of automation & manual test suites, HPALM is the best tool to manage that. It definitely integrates very well with HP automation tools like HP Unified Functional Testing and HP LoadRunner. Automated Suites can be executed, reports can be maintained automatically. It also classifies which test suites are manual & which are automated & managers can see the progress happening in moving from manual to automated suites. In HPA ALM all the functional test suites, performance test suites, security suites can be defined, managed & tracked in one place.
It is a wonderful tool for test management. Whether you want to create test cases, or import it, from execution to snapshot capturing, it supports all activities very well. The linking of defects to test runs is excellent. Any changes in mandatory fields or status of the defect triggers an e-mail and sent automatically to the user that the defect is assigned to.
It also supports devops implementation by interacting with development tool sets such as Jenkins & GIT. It also bring in team collaboration by supporting collaboration tools like Slack and Hubot.
This tool can integrate to any environment, any source control management tool bringing in changes and creates that trace-ability and links between source control changes to requirements to tests across the sdlc life-cycle.
Excel offers collaboration features that allow multiple users to work on the same spreadsheet, but managing changes made by different users can be challenging. Excel could improve its features by offering more granular control, better tracking of changes, and more robust conflict resolution tools.
Itcan be a barrier to productivity when importing and exporting data from other applications or file formats. To improve its features, it should offer better support for standard file formats and more robust error handling and reporting tools.
Excel can be challenging for finance students and working professionals, but it can be improved by offering more robust tutorials, better documentation, and more user communities and support forums.
The requirements module is not as user friendly as other applications, such as Blue Bird. Managing requirements is usually done in another tool. However, having the requirements in ALM is important to ensure traceability to tests and defects.
Reporting across multiple ALM repositories is not supported within the tool. Only graphs are included within ALM functionality. Due to size considerations, one or two projects is not a good solution. Alternatively, we have started leveraging the template functionality within ALM and are integrating with a third party reporting tool to work around this issue.
NET (not Octane) requires a package for deployment to machines without administrative rights. Every time there is a change, a new package must be created, which increases the time to deploy. It also forces us to wait until multiple patches have been provided before updating production.
Excel remains the industry standard for spreadsheets and has maintained simple and straight-forward formula writing methods. Although there is a learning curve to do more complex calculations, there are countless help sites and videos on the Internet for almost any need.
I'm giving it a 7 because it is my go to. But the fact other prefer Google Sheets when working with a team does get irritating. I've used the online version of Microsoft Excel that other teams can get into and it still seems behind Google Sheets. It's a little clanky and slow? If that's even a term.
Because it lets me track the test cases with detailed scenarios and is clearly separated in folders. Also the defect filter helps me filter only the ones that have been assigned to a particular area of interest. The availability of reports lets me see the essentials fields which I might be missing the data on and helps me to work on these instead of having to go through everything.
It is a great tool, however, it got this rating because there is a lot of learning that takes a lot longer than other tools. There are no mobile versions of ALM even with just a project summary view. I believe ALM is well capable of integration with other analytics tools that can help business solutions prediction based on current and past project data. This is Data held in ALM but with no other use apart from human reading and project progress. ALM looks like a steady platform that I believe can handle more dynamic functionality. You could add an internal communication platform that is not a third party. Limit that communication tool to specific project members.
Out of Microsoft Excel, Microsoft Power BI, IBM SPSS, and Google Sheets, Microsoft Excel is by far the most common tool used for anything data-related across organizations. Accordingly, our organization has also implemented Microsoft Excel as a first-step tool. We recently adopted Microsoft Power BI (the free version), and use it occasionally (mostly for creating dashboards), but it is less commonly understood by stakeholders across our organization and by our clients. Accordingly, Microsoft Excel is more user-friendly and because of its popularity, we can easily look up how to do things in the program online. Google Sheets is a comparable alternative to Microsoft Excel, but because it's cloud-based and we have sensitive data that needs to be protected, we chose against using this software. Finally, a few users (including myself) have access to and utilize IBM's SPSS. For my role, it's a helpful tool to do more rigorous analyses. However, because of its cost and limited functionality as a simple spreadsheet, we only use it for more complex analyses.
We have other tools in our organization like Atlassian JIRA and Microsoft Team Foundation Server, which are very capable tools but very narrow in their approach and feature set and does not come even close to the some of the core capabilities of HP ALM. HP ALM is the "System of Record" in our organization. It gives visibility for an artifact throughout the delivery chain, which cut downs unnecessary bottlenecks and noise during releases.
Each user can use it to whatever level of expertise they have. It remains the same so users can contribute to another's work regardless of whether they have more or less expertise