Basically, unites the whole process of software development, from conception of the idea to realization, to QA, to release, to bug fixing, etc.

codeBeamer ALM is extremely customisable; it covers all aspects of ALM; requirements, software architecture, computer programming, software testing, software maintenance, changes, continuous integration, project management, and release management; allows multiple teams, geographically dislocated, to seemingly work on the same project; tracks every single activity in the process; has a good potential for writing good Wiki pages; has placeholder for technical documentation; practically every tracker type item has comments, attachment, description, etc.; well established links between trackers, downstream references; customisable automation, say you can generate downstream task when system requirements change to a state; completely configurable state diagrams, etc.; excellent testing framework, test cases, test sets, test runs, etc.

As with every system, the value of it depends on how much you put into it; but IMHO codeBeamer ALM has a very high potential to give you exactly what you need from an ALM tool; say there is integration with SVN, etc.; there is a danger of overcomplicating, but that is the price of very flexible customisation; if you design your process well, you should be OK, etc.

Very flexible and powerful platform that can be adapted in a variety of ways to align to your process and practices for managing your application lifecycle. Expect to invest time and effort to configure the platform to meet your needs and expect significant return on your investment. Over a 6 month window we rolled out codeBeamer capabilities for: 1) Requirements Management 2) Risk Management 3) Architecture and Design Management 4) Test Management 5) Defect Management 6) Scrum Team Rituals (Sprints, Stories, Tasks, ...) codeBeamer is now our single digital system of record for the full Application Lifecycle.

It can be challenging to debug why a user is unable to execute a task given the intersection of 1) license constraints 2) project permissions 3) tracker permissions 4) field permissions

We are working with codeBeamer to fullfill the requirements from Automotive Spice and for this usecase the tool is very good for. Also we are working for medical products and with codeBeamer it is very simple to change the workflows from automotive projects to medical projects.

The easy way to create a traceability from the requirements to the tests.

The user management is not so easy to handle with

Before I joined the codeBeamer world, I worked with other ALM tools. It was really a hard time, lots of things didn't come together or were poor in performance. I remember my first steps in codeBeamer. It was like an epiphany - suddenly everything makes sense and it's really that easy to accomplish. Actually the tool supports you in collaboration and structured workflow.

Simply: it works! Seriously. I worked with other ALM tools. Either the tools didn't cover (understand) the ALM universe, or the tools were glued together resulting in diminished functionality or even failure. Supected links. Traceability browser. Test coverage. Those tools work perfectly in codeBeamer.

Sometimes it's difficult to handle WYSIWYG. Implementation is done with a third party tool (Froala) and codeBeamer is bound to its limitations and drawbacks. Usually I get my ideas realized within the HTML editor, but sometimes you have to struggle a little.

Good agile development features including Kanban board and Scrum process artefacts Easy management of integrated SCM repositories (Git, SVN) Good handling of project templates to specify and provide organisation specific development process templates REST API for a flexible integration of CodeBeamer with other tools Improved dashboard functionalities for project and user dashboards

It would be great to get more out-of-the-box integrations with other popular parts of a development toolchain like: Slack, IntelliJ