IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.
N/A
monday dev
Score 8.5 out of 10
N/A
monday dev is a product to plan, track, and ship software while staying connected to the business, featuring AI capabilities that allow it to analyze bugs as they are submitted, summarize product documents, and automatically assign tasks.
The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.
I find Monday helpful for lead management. It's great because details like phone, email, and addresses are specific columns from which we can grab data and pull it into other areas. It's great to see who is assigned what and to know what the next steps are for your leads. We use a different scheduling tool with our team, as that calendar view isn't as robust.
I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
I give a ten for monday dev's usability because it was a really smooth transition coming from Jira to monday dev. All team members also felt that way. When managing projects, the quality and various options I am able to customize views and columns for each task is really a dealbreaker. Approved.
It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
It is at least as good as these tools, in many ways, it is better because it is easier to use and setup. It doesn't require a full-time admin like these tools do. It does lack some of the detailed reporting and such that these offer, but the product is still young and growing. These are much more well-developed tools
It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
Comprehensive reports and dashboards provide better visibility.
Although the initial operational cost is usually somewhat high, it is really worth considering in an environment with more than 10 employees working together.
In project costing (web development) it is quite acceptable and falls within the scope of the final product quote.
I don't have exact numbers or percentages (because I'm not in charge of that section) but I can say that it falls within a good to acceptable ROI range.
