IBM Engineering Workflow Management Reviews

In terms of data, when I started in 2018, the database for IBM ELM was around 200 to 300 weeks. Now, in 2023, it's grown to 15 terabytes. 

The main use cases include RTP, API, and PI planning, sprint planning, data planning, defect fix tracking, and other related activities.

We have a custom process specific to our organization, which we internally developed. Each project has related V&V requirements and RQM testing projects. These projects are version-controlled and GRC-enabled, creating a complex GRC hierarchy and structure.

I essentially use IBM Engineering Workflow Management under agile methodologies for the development of stories, use case stories, and test cases with end-to-end traceability.

The tool provides traceability and reporting, which are important for compliance and measuring progress. The reporting part for management is probably the most significant. It provides more efficiencies for our scrum team, ensures everyone is on the same page, and offers leadership insight into progress.

I use the solution mainly as a task tracker, capturing workflows of different functional groups and creating different reports and metrics for them.

The most valuable features of the solution are highly customizable reports and visibility for all the higher management.

It is used for source control, defect tracking, and project management.

It was an all-in-one solution for source code, integrated source control, defect tracking, and project planning. Useful for getting started with all the needed tools for software development in 2010.

I really value the links from stories/defects to code via the tasks and change sets.

• We’ve used it to drive our move to DevOps primarily because the CI tools were pre-built by another team.
• The strong links between work-item tickets and change-sets have enabled simple reporting of changes to software.
• This adds business value by reducing time-to-market.

We use Workflow to manage all our agile project management; all our development is managed through this solution whether it's the stories, the hydration, the tasks, the defects. I'm the vice president of the company and we are customers of Workflow. 

Overall, Workflow allows us to manage our stories, sprints, hydration and releases. It's good for that. 

We are customers of IBM and I'm the manager of digital engineering.

There is a value in certain things like traceability, from high level requirements to low level requirements, to a test case, to a test plan, to a work item, to a change request, which is very essential to have for any OEM trying to not just create data, but also enable tracing. All those things are valuable. It's helpful that the traceability reporting is inbuilt and includes all your requirements, management and test management. There are also  certain integrations with code repositories, to a level where you can trace back and see who actually tested it, whether it was a pass or fail, the length of the test and steps behind it. Anyone coming in will automatically know that something has changed.

We are mainly using it for project planning, resource engagement, load distribution, and work allocation. Work distribution among team members and accountability for completion with a clearer picture. This represents the outcome clearly, along with measures to be taken, if any.

It has improved our organization up to an extent, but it certainly has a lot of areas for improvement related to resource management. Teams need clearer pictures of resource availability in charts and dashboards along with plans. Additionally, the non-availability of a "contributor list" both in plan views and JRS restricts the usability which would have played a greater role for our teams.