IBM Engineering Workflow Management Reviews

BM Engineering Workflow Management (formerly RTC) offers powerful end-to-end lifecycle management. It shines in large-scale, regulated environments where traceability, process enforcement, and integration with systems like DOORS and Rhapsody are crucial. The process templates and role-based access controls are highly customizable, and the Jazz platform enables strong collaboration between devs, testers, and analysts.

The UI feels outdated compared to modern Agile tools like Jira. Performance can lag when handling large repositories, especially on web clients. Setup and onboarding require expertise, and there's a steep learning curve for teams not familiar with Jazz architecture.

We're using EWM to manage development across multiple teams in a highly regulated industry. It helps ensure compliance through enforced workflows, audit trails, and tight integration with requirements and test management tools. This has significantly improved traceability and reduced audit risk.

IBM suite holds all the software development tools from source code to testing, requirements, and data warehouse reports and BI

Since it's all combined and managed, you can have enterprise components of the above list, and they work bi-directionally with each other - so you can force attaching a task to a code that is related to the same user, and it is on the current sprint, the data warehouse capabilities are endless like the live Excel export that you can work on the sheet data offline and get updates when you're connected.

The biggest drawback is that IBMers do not use it as their primary source control. So by not promoting it, the popularity declined dramatically, and developers moved to open source code versioning and cloud options where their code resides outside the vendor's premise (e.g., China). So the gist is IBM doesn't promote its product, and so the popularity declines.

The source control plugin supports only Eclipse and Visual Studio clients, making it hard for other IDEs to blend in.

This tools set, including the other integrated tools, provide the best platform for scaling agile teams for complex systems with stringent compliance requirements.

It can be confusing for new users as to which tool they are in, or need to be in, sometimes,

Developing large software and systems engineering applications

I like how customizable the tool is. It allows teams and users to really configure the tool for their specific needs. The tool is also very tightly integrated with many other IBM tools.

One of the things with the extreme customizability is that when the tool is integrated to the other tools, the more customized it is, it tends to break certain aspects of the tool. Either that or, the configuration is not easily defined to make it work.

We current use it in IT for workflow management and task assignment. We also use it for agile planning in conjunction with our customers (engineers) to define their needs.

Source control - ease of use and flexibility

It's a little flaky requiring computer reboot.

Version control and compilation of documents.

IBM Engineering Workflow Management helps my company map requirements to products. We develop these product to help with knowledge on our sensors. The best thing I like about Engineering Workflow is the traceability it provides on development cycle.

I had a long learning curve with the product.

Shorting the development cycle benefits the lower cost of product delivery.

.ability to manage work items and provide dashboards

does not support portfolio planning, the planning functionality needs to be more robust like a mpp

traceability, planning, reporting

The ability to integrate with other systems while allowing controlling access and permissions to content plus changes. The OSLC and REST API are extensive enough the extend the system to meet regulatory requirements efficiently

Lack of consistency across interfaces and intuitiveness of the interface leads user to the conclusion the system is too complex thus costly to develop products in. Configuration needs to be careful to focus consistency across work items and rest of the system.

Defense and Aerospace DO-178, ARP 4754, and DO254 development. The ability to capture and manage change of artefacts is beneficial and crucial to the development.

The face to face with the IBM professionals.

The information regarding the standard publication releases.

Configuration Management of 1980s tech, developed in the 90s and sustained for 30 years.

easy to use. easy to configure. nice subscription and notification. nice workflow control

DNG and RQM need to be more consistent with RTC,. RTC itself is great. Things like CSV import and export. Things like review.