IBM Engineering Lifecycle Management (ELM)

What differentiates IBM Engineering Lifecycle Management (ELM) from other similar products?

We appreciate how flexible the tool is. It enables individuals and groups to modify the device to suit their requirements. The tool also includes several other interconnected IBM technologies that regulate information access and rights while facilitating updates and system integration. The OSLC and REST API can effectively extend the system and adhere to regulatory requirements.

What is your favorite aspect of this product?

The business uses IBM Engineering Workflow Management to link needs to products. We make these products to aid in the understanding of our sensors. Engineering Workflow's ability to provide development cycle traceability is one of its best features. Excellent subscriptions and notifications are simple to set up. Efficient control of the workflow. With the other linked technologies, this toolkit offers the most effective framework for the scalability of agile teams for complex systems with strict compliance requirements

What do you dislike most about this product?

The RTC navigation model is challenging to comprehend for novice users. The inconsistent UI occasionally makes things more confusing and might be more user-friendly. This confusion is cleared up after the user has used RTC for a few months. But it does take some time. A manager or project manager cannot use RTC to oversee the job responsibilities of team members centrally.

What recommendations would you give to someone considering this product?

I liked how simple it was to use. The user-friendly interface improved accessibility for Scrum development. It was much simpler to keep track of everything because the IDE could use the Personal Work View and the task tracking capability. Furthermore, receiving ten free licenses upfront was beneficial because we only had a tiny development team.

What differentiates IBM Engineering Lifecycle Management (ELM) from other similar products?

It fully implements kanban agile and provides a variety of dashboards. It is user-friendly because it integrates with test and requirement management tools. RTC is a more trustworthy solution since Java APIs are easily accessible for extension development. Once created, the needs discovered are easy to manage, monitor, and analyze.

What is your favorite aspect of this product?

The dashboards and GUI produced by the IBM RTC Tool are simple to understand for senior management when considering the range of extended versions they may view. Widgets are great for condensing information. Lowered management risk - Due to continual system integration, you know the precise volume of functionality created thus far.

What do you dislike most about this product?

The program needs some time to adjust. Integration with extra tools serves no purpose. Lacks portfolio planning functionality; as a result, a more complex planning element, comparable to an MPP, is required. Information regarding the publications' combined releases. The user interface could be improved. The dashboards can be improved, and a specific drill-down method needs to be valued.

What recommendations would you give to someone considering this product?

RTC allows team members to own their work, estimations, and other activities fully. This ownership removes the need to update a PM on your progress, have the PM update the plan with your tasks, and notify the team, which adds time and reduces the chance of misunderstanding. It was our idea. If you have any problems, the personnel will be able to help.