Try our new research platform with insights from 80,000+ expert users
it_user631638 - PeerSpot reviewer
Senior Technical System Analyst at a financial services firm with 10,001+ employees
Vendor
The most valuable features for me as a developer are Iteration Planning and Iteration Tracking

What is most valuable?

The most valuable features for me as a developer are Iteration Planning and Iteration Tracking.

  • Iteration Planning is very helpful for the team during planning sessions. It shows the exact picture of where we are and what is coming.
  • Iteration Tracking is a very useful dashboard that shows the status of the stories and details what they are about.

How has it helped my organization?

This is the only tool our team is using for tracking and monitoring agile projects (features, stories, tasks and use cases). It’s stable, easy to navigate and fast. It’s not overwhelming with details and fields, but provides necessary placeholders to keep all the information needed for the project and have a picture where we are and what is coming.

What needs improvement?

I would say use cases is an area with room for improvement. I found it a bit cumbersome and not so easy to grasp a global picture. Some teams prefer to track use cases through the HPE QC tool, keeping the rest in CA Agile Central.

For how long have I used the solution?

We are using CA Agile Central since the beginning of 2016.

Buyer's Guide
Rally Software
March 2025
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.

What do I think about the stability of the solution?

We had a lot of stability issues; however, all of them were solved during Summer/Fall 2016. Recently, it’s been stable and provides the necessary functionality.

What do I think about the scalability of the solution?

We did not encounter any issues with scalability.

How are customer service and support?

I haven’t dealt with technical support.

Which solution did I use previously and why did I switch?

I am not aware of any previous solutions.

How was the initial setup?

The setup was done for us already.

Which other solutions did I evaluate?

I wasn’t the one to decide which solution to adopt. However, I like CA Agile Central as the choice of our management.

What other advice do I have?

Go for it. It’s a nice tool to use.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
it_user797955 - PeerSpot reviewer
Director of Delivery at Physicians Mutual Insurance
Video Review
Real User
We can work better and at a higher quality, than we were able to before
Pros and Cons
  • "The transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing."
  • "We can work better and at a higher quality, than we were able to before."
  • "I think there needs to be some simplification. The team-level side can be challenging and complicated."

How has it helped my organization?

It has improved our ability to focus on less work, but do that work better and at a higher quality, than we were able to before. 

What is most valuable?

The main value that we get out of Agile Central is the transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing. 

What needs improvement?

We have been talking about improvements in the quality section of Agile Central. The quality section does allow you to do test cases and test sets, and all these things, but it does not integrate very well with the portfolio and feature side, which causes some challenges. 

What do I think about the stability of the solution?

We have not had any issues. 

What do I think about the scalability of the solution?

We have had no scaling issues with Agile Central. We have worked anywhere from a couple of teams up to about 15 to 20 teams on Agile Central.

How is customer service and technical support?

Technical support is very good, considering we have very rarely had to use it. The product has been very stable for us. We have not had a lot of technical support issues even to reach out and ask about.

How was the initial setup?

The upgrades are very simple and straightforward. They generally get pushed out, and you choose whether or not you want to accept that upgrade early, or whether you are going to wait for the general release. 

As far as the initial setup, it can be challenging. There are a lot of options. There is a lot of configuration. There are a lot of decisions that you have to make on how you want Agile Central to work for your company. Those decisions can impact your flexibility in the future. With the initial setup, there is some thought that really needs to go into how you want to do it.

What other advice do I have?

I would give it probably in the seven to eight range. In order to improve beyond that, I think there would need to be some simplification. The team-level side can be challenging and complicated. However, its ability to scale to portfolio and executive-level solutions really drives it up to that seven to eight score. It is something that I don't think there is a lot of other projects out there that allow you to take that from a team to an executive-level view.

Most important criteria when selecting a vendor: First and foremost, we are buying a product, but we are buying also the people and support. Probably the best thing we have had with Agile Central is not only the tool, but the people that support that tool, and the relationships we have been able to build there in order for us to further our Agile journey.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Rally Software
March 2025
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.
it_user779193 - PeerSpot reviewer
Project Manager
Real User
Data visibility means I know the status of a release, though the Project Picker is not flexible enough
Pros and Cons
  • "If teams are tracking correctly and entering their information correctly, it's really easy to see where you're at, within your release, and whether you're on track or not."
  • "It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
  • "I would like for workspace admins to be able to hide projects in the Project Picker and not lose any historical data; make them invisible to certain users, visible to certain users, depending on permission sets. That would be lovely."
  • "I'd like the ability to customize reports without having to incur Professional Services, or having to write my own code GitHub and then implement that as a custom report. That's untenable. It's not sustainable."

What is our primary use case?

We use it to track all of our work. We also manage our portfolio in it.

It works. It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history.

How has it helped my organization?

There's familiarity. The teams have been using it for a while. Leadership is comfortable with it. That's huge. And from a price point, it's a cost effective solution for our needs.

What is most valuable?

Visibility of the data. If teams are tracking correctly and entering their information correctly, it's really easy to see where you're at, within your release, and whether you're on track or not. For our business model, we can't get everything out of the box, but we're a unique business so I understand that, but we know how to massage the reports to get what we need out of it. And so far it's done the best job for us.

What needs improvement?

I would like for workspace admins to be able to hide projects in the Project Picker and not lose any historical data; make them invisible to certain users, visible to certain users, depending on permission sets. That would be lovely. 

I'd like the ability to customize reports without having to incur Professional Services, or having to write my own code GitHub and then implement that as a custom report. That's untenable. It's not sustainable.

What do I think about the stability of the solution?

I think it's relatively stable. I've had very few instances where I've had an issue. I think CA is really good about communicating outages. Any troubles we've incurred generally haven't been on CA's side, it has been teams or functional managers not assessing impacts to anything they have in process that could be related to the outage that was communicated.

What do I think about the scalability of the solution?

Scalability works well for us.

How is customer service and technical support?

I've had pretty good responses with them. If I need help or we run into something that we believe may be a defect, I just open a ticket on the support site and I usually get resolution really quickly. 

There was one issue that we had where I was going to be out of town, and I'm the point of contact for our company, so I had to leave a person in the gap to get it to "done." And within a business day it was resolved. I was really happy with that because I was a little concerned.

What other advice do I have?

When selecting a vendor the most important criteria are:

  • It's got to work.
  • It's got to be stable. 
  • Cost, to be honest, is a huge factor. It's top three. It needs to be reasonable and affordable. I need to be able to make a business case and sell it to leadership, give them a reason why it's going to work better than what is currently in place. 
  • We need reliable support.

I rate it a seven out of 10. I don't rate it higher because of the things I said I needed more autonomy in being able to change. And while I have really good results and feedback from CA Support, I wish that Accounts were as responsive to my needs as the Support side is. And I get that we're probably a small fish in their pond of Accounts, but we still need help getting our work done.

If I were to advise a colleague looking into similar solutions I would say it's a good tool. I'd want to talk to them more about what it is they're trying to accomplish to find out whether this is the best fit or if they want to use something a little different. Agile Central will cover a lot of needs for you, but maybe it's too much for what you need. So I would want to dig down deeper into their requirements to make sure it's the best fit.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user592689 - PeerSpot reviewer
Software Engineering Manager at a tech company with 10,001+ employees
Real User
With the portfolio management feature, we understand our capacity and visually understand all the various initiatives in-flight.

What is most valuable?

  • Portfolio management

How has it helped my organization?

It is designed 100% for agile, so if you run an agile/scrum organization, it will work for you. With the portfolio management feature we were able to understand our capacity for the first time and visually understand all the various initiatives in-flight. We could provide very clear dashboards to senior execs to be able to choose which projects we did and if they were on schedule.

What needs improvement?

Its greatest "feature" is also its limitation. Nothing is locked down or mandatory, with no complicated permissions, so it's very easy to get up and running quickly. They could have more controls around user types and what they require permissions to do.

What was my experience with deployment of the solution?

There were no issues with deployment, stability or scalability because it's cloud based. It only went down a few times, which is very inconvenient when you run your entire team on it. But I guess this is the same for any system, cloud or self-hosted.

How are customer service and technical support?

Technical support is 6/10. There weren't too many problems, so I didn't have to use them much. However, if support issues were specific to your data, they couldn't really help easily. They had to get permission to duplicate the database and then work on that, which in a large organization required quite a few approvals.

Which solution did I use previously and why did I switch?

I have used JIRA in the past. This is not originally agile-based and requires more setting up to get it right for you.

How was the initial setup?

The initial setup was simple as it only does agile.

What about the implementation team?

An in-house team implemented it. The adoption wasn't the hard part. It was the overall agile transformation that required the effort, which was a culture/process thing.

What was our ROI?

I don't know about ROI but we couldn't work without it.

What other advice do I have?

You have to adopt agile and be true to agile. This is an agile product, too. If you don't want to plan in sprint and build teams around the agile process, then it's probably not the tool for you.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user591864 - PeerSpot reviewer
IT Systems Analysis Consultant at a healthcare company with 1,001-5,000 employees
Vendor
Tabs in user stories allow you to jump to another tab without leaving the story. Stories can be moved between different sprints and backlogs.

What is most valuable?

The features I view as most beneficial are:

  • The ability to search at different levels and views
  • Having tabs in an opened user story so that one can jump to a tab and check the details without leaving the user story
  • Being able to sort on any element in the column headers
  • Being able to add new elements to a page type
  • Being able to move user stories to different sprints or backlogs easily
  • Being able to add content or select a different drop down and have it saved automatically while still working on a user story
  • Being able to get to help-rich tool pages and videos
  • Having a community for this tool
  • Having a dashboard that can be customized to a user
  • Being able to write program code to generate a unique report
  • Being able to click on maintenance wheel thumbnails to do such things as delete a particular attachment
  • Having tool level tabs to select a different view page in the drop-down
  • Being able to “split” a user story for tasks that have not been completed

That is just a starter list.

How has it helped my organization?

When there are disparate locations in cross-area teams, it is difficult to locate all of the documentation that one needs.

Having the CA Agile Central tool allows for there to be one place that contains all the information on teams and sprint by having features to add and update notes, attachments, and data element values to user stories and tasks.

This encourages team members to make updates as a way for others to learn the challenges and developments that are occurring during sprints and to communicate statuses on where we are now regarding tasks that are in-progress or completed.

What needs improvement?

I think that the product use of the user-story-split feature that creates child user stories can be abused by users for being so easy to do. It will require one to drill down to the grandchild, or great-grandchild, etc., to see the progression or what happened before now.

Also, it will look messy when seeing a list of nested user stories. Using this feature, a waterfall view is being promoted. Instead, having predecessors and successors as part of the split will allow us to track this “legacy” user story better, which should have been created as smaller user stories to begin with.

In a sense, completion of a user story in a sprint would have been reinforced by not seeing parent and children. Predecessor user stories would not contain unfinished tasks.

For how long have I used the solution?

I have been using CA Agile Central for one year.

What do I think about the stability of the solution?

We haven’t had any stability issues, but at times there are IE browser stalls for those who use IE in meeting presentations. I, for one, use Firefox as my browser, so I do not experience issues.

What do I think about the scalability of the solution?

I have not had scalability issues at all.

How are customer service and technical support?

I have not had a chance to work with technical support yet.

Which solution did I use previously and why did I switch?

I have not used a different tool, because we did not have one.

How was the initial setup?

Setup was done on my behalf, so I cannot comment.

What other advice do I have?

I think that there is a trial period for this tool, so I would say to try it. However, some training is needed first.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
it_user558177 - PeerSpot reviewer
IT Manager at a transportation company with 1,001-5,000 employees
Real User
The burn up and burn down chart helps me show the progress of my team to the business.

What is most valuable?

For me, it is the burn up and burn down chart, so I can measure progress easily. It shows me the progress of the team and it helps me show the progress to my business.

How has it helped my organization?

The charts that this tool has make it transparent. Also, the information is there for everybody to share and it supports Agile methodology. This tool makes it easier. These are the features that are valuable to us. Our team’s Agile maturity level is close to expertise.

What needs improvement?

I would like to see it more well connected with the PPM tool. We have Planview. It does connect to it but I would like it to connect more robustly. They just introduced a new milestone feature of the product. I would like it to be more user-friendly.

What do I think about the stability of the solution?

Stability of the product is good.

What do I think about the scalability of the solution?

We have over a thousand employees using it and it is extremely scalable.

How are customer service and technical support?

I personally haven't used technical support. We have a PPT tool support group which has used it. So, if we have any issues, we report to our PPT support group and they reach out to CA technical support.

Which solution did I use previously and why did I switch?

When we moved to Agile, we were just using standard scrambled writings on the wall. We knew with the scale of our organization, we needed something to suit our needs and so we decided to invest in this product. It did meet our needs, especially in terms of scalability as we knew that there were going to be so many licenses we would need. We needed a more robust organization.

In addition, we needed someone who was flexible to work with us. At that time, it was Rally and they were very flexible to work with us. The most important criteria for choosing this vendor was their willingness to work with us, features, scalability and cost; also it needed to fit our organization culture.

Which other solutions did I evaluate?

I did not choose this tool personally, it was an enterprise decision.

I believe they looked at JIRA as well and they picked CA Agile Central.

What other advice do I have?

Go for it but make sure you learn the tool and understand it. Hopefully, you have a product expert.

I would like the milestone features to be more seamless and user-friendly.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user558051 - PeerSpot reviewer
Enterprise / Team Agile Coach at RBC
Vendor
The Portfolio allows us to drive our requirements along with planning at an enterprise level. Kanban features need to mature.

What is most valuable?

The Portfolio is the most valuable feature that I found, because it allows us to drive our requirements along with planning at an enterprise level. That helps a lot. Along with this, there are other valuable features, such as Timebox. It provides proper cadences based on the Timebox that we work with. Those are the two features I find most valuable.

How has it helped my organization?

Agile Central is an enterprise tool, so it allows our teams to work together. Individual teams don’t work in a silo. Agile Central allows us to drive all the metrics at an enterprise level. We can then discover what needs to improve at the enterprise level, instead of looking at it on the team level. We are using it for our Agile project delivery.

What needs improvement?

As I've mentioned elsewhere, Kanban needs to mature a little more. The product itself is focused more on the scrum, but they need to go forward. Also, they did a pretty good job on the scaling side, but they could improve.

What do I think about the stability of the solution?

Stability is pretty good. It's improved from the past. Ten years ago, I was using this product. As a product, it got better over time.

What do I think about the scalability of the solution?

Scalability, is good, but needs some improvements on some other aspects of the framework, such as Portfolio Kanban. It requires a little bit of work, but we can make it happen. It’s the best tool.

How are customer service and technical support?

We have ASP service with CA Agile Central. It is kind of technical support, but it is personalized support that we could get for the company.

Which solution did I use previously and why did I switch?

Our business has been using Agile Central for five years, but I have been using it for almost 10 years. I see the evolution of the features that have come along, as well as the product overall, making this an option that allows me to take it to the next level.

The most important criteria when selecting a vendor are the sustainability of the product, their reputation in the market, and pricing.

How was the initial setup?

I have been part of Agile Central since the get go. Initial setup is straightforward. It is software as a service, so it is very easy for us to set it up; the project and initiative.

What other advice do I have?

The tool is amazing. If you want organized, overall delivery at the enterprise level, this tool allows you to do it for sure.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user558054 - PeerSpot reviewer
Senior Agilest at SolutionsATI Consulting
Consultant
With big room planning, we can get it all laid out, understand what the dependencies are, where the interlocks sit, and which sprints can be optimized.

What is most valuable?

It allows me to do large team planning operations, where I can do "big room planning" and have all of my Agile teams in one session. We can get through all of our planning through the use of the software. With big room planning, we can get it all laid out, understand what the dependencies are, where the interlocks sit, and which sprints can be optimized. The portfolio tracker tool is phenomenal. It gives us the opportunity to look at our features holistically across the entire landscape of the solution, where they fall within a continuous delivery (CD) release when you're looking at a DevOps model. It allows us to apply those features to the DevOps model. I can take that and apply it across all of my teams, look at it when we can pinpoint exactly when that feature is going to be delivered holistically. This is a huge value to our client, who is Cisco.

We can have high predictability, which is what Agile tries to do. We can have low cost of ownership, dealing with “just-in-time” delivery for the monthly releases, because we release on a monthly cycle. We can look at this information and say when those features are going to become available. The portfolio tracker is huge, a phenomenal piece of the add-on functionality that's been wonderful.

I also like the use of apps, and the ability to use the customized HTML capability of the apps. We're working with the consultants to design a custom look and feel for specific types of reports that we need. It's very open architected, so we can take advantage and utilize the software as we choose to use it, and have a really good experience with it.

There's some room for growth. There's some more functionality we'd probably like to see in it, but at this point, it's been a stalwart product for us.

How has it helped my organization?

It's optimized how our organization runs. We can look across multiple teams, using Scaled Agile Framework Methodology (SAFE), so that we can look at various release trains, and how that then flows up to the overall program budget. Each train has its own unique budget line. I can look holistically across all the trains and have it flow up to the program office’s budget. I can track personnel within the software. We can do all of the quality functionality and spread that across multiple tracks. In this way, one track is not going to be heavily burdened by taking on the quality function.

The big value add is not only the ability to do Agile, but scaled Agile as well, utilizing the budget functionalities. It’s really top notch in that regard, with the ability to work with the personnel function of the software. It gives us another holistic view of the overall functionality and operations that we have providing a value add to our customer, Cisco.

What needs improvement?

The main area to improve is performance. If they can get that performance improved, they'd be golden. They really need more in the DevOps modeling, and the use of Kanban. Their Kanban area is fairly weak. That's probably the one area of the tool that, outside of performance, really needs improvement. If they could add more robust Kanban functionality, then they would have the best of both worlds. You would have a DevOps capability, Scrum capability, and Test Driven Development (TDD) within the tool.

That would also help from the quality perspective. When you're dealing with your DevOps team, especially when you're trying to do releases on a monthly basis, they need to be tied into deadlines and be able to track through a Kanban mode. They need to know about the workflows, the work in progress, and how it moves through the workflow. That would probably be one of the main areas I would tell them to put some energy into the Kanban side of the tool. If they did that, then they would have pretty much the complete solution. They are losing a lot of business to Trello.

There are performance issues that nag the product. I would like them to build out a more robust Kanban workflow methodology system. Then, I would open up the APIs more. I would allow for third-party solutions to be able to plug in easier. There's a little bit of work that they'd need to do.

There's a couple areas where that they can make significant improvements, and I'm sure they're working on it.

What do I think about the stability of the solution?

Stability is very good. The solution rarely goes down. When it does go down, we make a couple of phone calls and we get a really clear estimate of when it'll be back up. We get e-mail alerts when things aren't going too well. The biggest issue that the product needs is to improve is performance.

Ever since the Agile Central package (formerly Rally) came out, performance has always been an issue. It lags behind, at times, especially when generating large reports. That's probably the number one area for improvement. They know that. I'm telling them nothing haven't heard before. If they can get performance at a much better level, I think the product would be really well received for other companies, who tend to shy away from it from a performance perspective.

One of its main competitors, AgileCraft, is a high performing product. It's got really good performance. They really need to be competitive with some of the other products on the market. I have used it extensively. It's a great product. Its premier focus is being a safe solution, where Rally tends to be a Swiss Army Knife. It's more for all encompassing type of Agile work. Whether you're doing SAFE, standard Scrum, Test Driven Development (TDD), Feature Driven Development (FDD), these are all areas for which Rally can be utilized. That's what makes it a very multiverse tool and allows you to work holistically across an organization, where AgileCraft has a very specific, narrow focus.

What do I think about the scalability of the solution?

Scalability is very good. No problem there. It will scale as you need it to. That's not a problem.

How is customer service and technical support?

I personally haven't used technical support. My interaction has been through our consultant. We have a dedicated team of consultants with whom we work. If we ever run into an issue, we usually just pick up the phone, call our consultant, and explain what's going on. We do have support through a Cisco support group. They're extremely responsive. When we run into a problem, they usually solve it within about an hour or so.

Which other solutions did I evaluate?

Vendors who were on our shortlist were JIRA (Atlassian) and AgileCraft. At the end of the day, we chose Agile Central, mainly for its robust capabilities and the ability to talk to other database systems. For example, I can bring in all those JIRA defects or issues, into the CA central product, because of the open API architecture. Using the SOAP API codebase, I can then have one of their consultants write me a custom hook that allows me to bring in all the data from those other databases. The other two solutions didn't have that open-ended modular framework that allowed me to pull in information from older systems, whether it's coming out of Excel spreadsheets, or older systems, like JIRA. That's one of the big things that we look at.

What other advice do I have?

When making a decision to switch products, I consult others on tool choice based on the number of departments they have. I went in as the Agile coach to Cisco and recommended that they move to this solution. One team I was working with used JIRA. It's an option that Cisco allows some of their departments to use. I got them out of JIRA into Rally, mainly because JIRA is older technology, and it's too lightweight for a major corporation such as Cisco.

This tool allows you to talk to the rest of Cisco. If you've got one group running one solution and you've got another group running another solution, they can't speak to each other. They can't share data. They can't assign issues to each other. By moving one off one platform and moving them onto Rally, or to Agile Central, we can now holistically start to work across organizations, and see each other's problems.

The only other big issue is their workspaces need to talk to each other. That's another area for improvement that would be good. There are a few areas they had to work on, but cross-workspace communication is the main one. If they could solve that problem, that would be amazing. I would be so happy. Even in my own group for which I'm providing consulting services, we have multiple workspaces and we can't talk to each other. That can get a little crazy. We have to create this third solution that we all feed into. Obviously, nobody pays attention to it, because everybody is so focused on their own lane.

In terms of selecting a vendor, I look for the responsiveness to quality concerns. Whenever you've got an issue, the timeliness that they'll come back to you to resolve those technical issues is important. I also look at whether or not they have consulting services themselves for customization work The other part of it is just overall “solutioning”. I want to know if they have a complete suite of products, or if it is just a standalone, a one-off. If it is, then I have to go bring in three or four other additional products to augment the single product. Then you've got multiple bids and you're talking across multiple vendors, and that can be a headache. I just want to do one-stop shopping.

That's what CA provides holistically across the entire platform. They're going to give me everything that I need. Another factor is with one vendor, you work on better pricing structures and a better deal. Whether it's in service, or getting a discount on other products, you can weave all that in as an opportunity going to one vendor.

My advice to other is take a test drive. They have a sampling system that you can demo. They'll give you a space to put your product in and try to go through the whole workflow process. Make sure you go through the whole workflow process. Really see and understand exactly the functionality that the solution has to offer. A lot of people stop at the very top level, the one-inch level. Go underneath the wave and dig down into the solution. There's a lot of great opportunity there.

One of the neatest opportunities, because of its HTML capability with its apps, is the ability to embed a lot of my Smartsheets right into the solution. I can take team rosters and embed them. I can track monthly performance reports and a number of different functionalities that are available to me via the Smartsheet. I can update my Smartsheet, and it'll automatically be reflected in Rally. That is huge in the CA Central product. That's significant for me.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
agileninja - PeerSpot reviewer
agileninjaAgile Coach at a tech consulting company with 11-50 employees
Consultant

Awesome information.
I'd like to point out that 3rd party integration tools (like opshub.com) also makes it possible for us to integrate Rally/Agile Central with other tools in our ecosystem. This makes it very easy for my clients to go for a frictionless adoption.

See all 2 comments
Buyer's Guide
Download our free Rally Software Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Rally Software Report and get advice and tips from experienced pros sharing their opinions.