IBM Engineering Lifecycle Management

IBM Rational DOORS is already succeeded by different IBM toolset for the task that proved to perform highly profitable.

Not all parts are under development. It might run out of date sooner or later by design.

IBM Rational DOORS has most installation in truncated format so it is in need of full fledged installation for development at the customer.

Cannot really answer as I was a user as an employee.

Ability to generate document straight from DOORS is a big plus.

Ability to track all changes is a big plus when doing multiple iterations or updates to requirements.

Need wider use of DOORS by all stakeholders.

Manage complex projects in one single integrated solution.

Reporting through IBM Rational Team Concert enables us to make the best business decisions.

Collaboration of teams on projects in one place.

Time saving due to being a centralized tool for all the project functions.

Great with customization according to the users need.

Breadth of integration features and aspects.

Time and development management software.

Quality and accurate data analytics production.

Effective on easy reporting and access control management is nice.

Price

Better Management of Testing Artifacts

Helped us enforce Testing Process

Helped us in keeping track of Test Execution Results for each Build

Wastes time to get access, connect.

Many other tools are faster and easier to use.

RTC helps automate incident management workflow which improves our work efficiency. With the integration with Geneos and GSD, we can one click create RTC incident tickets from Geneos with most of the information copied from Geneos automatically and then link the details to GSD for privilege account management if needed.

RTC provides a holistic view on ad hoc production activities. We use RTC for production management. Whoever needs to get access to production due to non-planned activities (planned change is managed in GSD) has to raise an incident ticket or service request ticket in RTC so as to get production privilege accounts.

RTC is also being used to review and approve the usage of privilege account which help us to meet audit requirements. For example, if a user made some database change using privilege account under incident number xxx, an entry will be added in RTC and sent to account owner or production support manager to review and approve.

Having this software available was mandatory, but allowed us to win a bid for a project that has led to other work.

We have gained major experience and recognition due to our use of this software.

If you can setup DOORS to your project, you will experience lower costs.

Also, less rework in the project, which means lower times to achieve your milestones.

Finally, the cost of setting up a related project is considerably lower, and the estimates obtained in the process are much more precise.

Expensive in comparison to other tools like JIRA

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.

License cost is on higher side.

The application teams were not able to provide a specific team to be able to work completely on the tool because most of the artifacts and documents were produced by the business division that creates sub-standard documents that are easy to import.

The approach to defining standard artifacts and ability to store them in a central repository was well understood but the way DNG works was considered really too complicated and not user-friendly.

It has given us a way to manage a project, consisting of a large team of members.

The reports and queries are an easy way to look at tasks assigned to a particular member or team.

It provides for a way to generate development burn-down charts and defects ratio.

It has although, created an overhead on development teams to enter data into the RTC system in order to get the benefits of the above.

Allows managing large number of dev stream and products.

Better organization of requirements

Effective assignment of priorities

When estimating the size of stories and tasks become predictable, it facilitates sprint planning.

There is a very positive ROI when a disciplined, mature development team use use the software.

Worked as project manager and used this tool as part of client process. For my current client I am using JIRA.

Increased efficiency

Better reporting

Better visibility

Increased employee efficiency is definitely a point to be considered when all the employees are resolving the change requests in a timely manner.