Sr. Project Scheduler at a government with 10,001+ employees
Real User
Top 20
2024-12-26T18:53:00Z
Dec 26, 2024
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.
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.
Vice President Delivery - Enterprise Solutions and Infrastructure Services at a financial services firm with 10,001+ employees
Real User
2021-11-18T03:58:14Z
Nov 18, 2021
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.
Learn what your peers think about IBM Engineering Workflow Management. Get advice and tips from experienced pros sharing their opinions. Updated: July 2025.
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.
IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of...
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.
It is used for source control, defect tracking, and project management.
I use the solution mainly as a task tracker, capturing workflows of different functional groups and creating different reports and metrics for them.
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.
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.
We are customers of IBM and I'm the manager of digital engineering.
We primarily use the solution to help us implement Scrum.
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.
Execution of the Agile software development methodology.