AuditBoard vs. codeBeamer ALM vs. Rally Software

Auditboard is especially useful for SOX control testing. It is very convenient having all our information on a single platform. It is easy to communicate PBC requests to clients, store control testing working papers for review, communicate deficiencies and build dashboards to provide visual statistics. Situations where it might not be useful are for organizations that are smaller in size where the templates don't fit well with their internal audit/controls program. There is a significant amount of testing required before using the platform, and adapting working papers to fit in well with AuditBoard

Incentivized

In my opinion codeBeamer is well suited for any activity where detailed tracking is needed with teams involved. It can be less suited for small projects which do not last long, or are not continuous, etc

Rally Software is well suited for large Agile or scrum teams who do sprints and it helps managing sprints and backlogs. It is well suited for organizations who want visibility into work being done and progress. Suitable for tracking is user stories, defects and release planning. Works well with CI CD too. It would not be suitable for small teams or startups. For teams that don't use agile. Teams who want lightweight tools like Jira. Companies with a limited budget.

Incentivized

• AuditBoard allows real-time collaboration between control and business owners and auditors.
• AuditBoard has a lot of fantastic training sessions and office hours to help users make the most of the product.
• AuditBoard has great customer service personnel to answer questions and troubleshoot any issues.

Incentivized

• Tracing of requirements.
• Tracking of development.
• Tracking of QA.
• Tracking of bugs.
• Tracking of releases.
• Wiki.
• Users and teams.
• Works for teams scattered across the globe.
• Testing and coverage for releases.
• Integration with SVN.

• There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
• Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
• Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
• Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
• Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
• It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
• CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
• The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
• CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
• Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.

• We used to perform our Risk Control Analysis (RCA) for each audit's planning in an Excel spreadsheet. Once we purchased the Risk Oversight module, AuditBoard helped us convert the RCA to a system function rather than a spreadsheet. At first, we lost some of the functionality the spreadsheet provided, but AuditBoard did continue to help us build and work towards a solution more similar to what we previously had. Though happy with it, it's still not perfect. As one example, I'd like to be able to link actual Ops Audit work steps that cover the risk and controls being outlined in the RCA, rather than just adding a comment to state which steps cover them. More of a preference, I suppose.
• I also had demoed their beta Resources and Scheduling module, but it didn't have enough functionality at the time to work for how we put the quarterly Internal Audit schedule together (using Excel). One thing I recall was that you couldn't pull in SOX controls or non-chargeable work (such as education or administration) to auditor's schedules; it was meant to schedule the Ops Audits only. It is possible they have already fixed or improved this; I just haven't seen the updated version.

Incentivized

• Search.
• Metric calculation.
• Would be nice that cB is a source of truth, i.e., that say SVN commit is done only from cB; know this is difficult to achieve.

• User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
• The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.

Incentivized

• To keep connecting my people, platform, and process for faster, smarter, better results.
• Making the right contribution to the community. Use Agile and Lean processes to manage the work of your team.
• Once you have tasted the positive result with Rally Software, you don't want to give up and come back to the old school of development pain any more.

Incentivized

Sometimes info in codeBeamer can be lost, in principle, if not well organized by the user, info can never be found, or can be forgotten about, etc

Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available

Don’t recall ever being unavailable.

The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.

Excellent support professionally. Also, thanks for giving me for free access to SaaS cB for my hobbyist project.

I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.

Incentivized

It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.

They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.

I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial

Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page

Incentivized

I remember there were a lot of sync issues when I used the internally developed software, but that's probably because a few people were working on the same project at the same time. I have not come across this issue in AuditBoard

Incentivized

codeBeamer is by far better.

Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.

Incentivized

• Hard to quantify. It was cheaper than the tool we had and we were able to get rid of standalone tool for surveys. overall, just better user experience for all.

Incentivized

• Customer tracking.
• Process tracking.
• Workflow framework.
• Can be overhead.

• it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
• with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
• too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise
• Kanban board support is lacking

Incentivized