The following are best practices for Agile ALM:

You can build an Agile Dashboard by combining the agile wiki plugins with the Table plugin. In fact, for each newly created Codebeamer project there will be a default Wiki page created with the name Agile Dashboard. This clearly illustrates the idea, and can be edited or copied for further customization.

Information radiators are publicly visible displays that show the status of the current iteration or the overall project.

They can be as simple, as a large LCD TV with a periodically refreshing dashboard on it. The dashboard should display statistics about the currently running sprints, a Burn Down Chart per team, the status of the last CI build, number of the recently created and solved work items and so on. The content should rely on the key performance metrics of your company.

To implement this with Codebeamer X, you should consider:

For more information see: concept of information radiators by Alistair Cockburn.

WIP limits (Work in Progress limits) mean a simple, but efficient way of preventing bottlenecks in the software development pipeline.

Limiting WIP means setting up minimum and maximum values for each column in your cardboard. For example, having less than 2 cards in the ToDo column means that you will soon run out of work to do, thus should be flagged. In the other end, having more than 5 cards in the To Verify column means that the QA team is overloaded, and suggests that your team should reallocate resources to testing to remove the bottleneck.

WIP limits can vary between columns, and should match the capacity of your team. The cardboard enables you get to the right WIP limit as you get better at it.

Disadvantages of not having WIP limits