We just raised a $30M Series A: Read our story

Rally Software OverviewUNIXBusinessApplication

Rally Software is the #8 ranked solution in our list of top Enterprise Agile Planning Tools. It is most often compared to Jira: Rally Software vs Jira

What is Rally Software?

With Rally Software, you can plan, prioritize, manage, track, and continuously improve your work so that you can deliver the value that your customers need with speed, quality, and efficiency. Our enterprise-class Application Lifecycle Management (ALM) SaaS platform provides visibility into progress, roadblocks, and dependencies across multiple teams, projects, and programs. This allows you to align to your strategic goals and create better business results, and to do it all in a single system of record.

Rally Software is also known as CA Agile Central, Rally Enterprise, CA Agile Training, CA Agile Coaching, CA Agile Academy, CA Agile Management , CA ALM.

Buyer's Guide

Download the Application Lifecycle Management (ALM) Suites Buyer's Guide including reviews and more. Updated: September 2021

Rally Software Customers

Physicians Mutual, Harvard Pilgrim HealthCare, Editora Abril, Tata Communications, Level 3 Communications, Seagate, TomTom, Philips, Hiscox, Physicians Mutual, MYOB

Rally Software Video

Archived Rally Software Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
PM
Test Automation Architect at CenturyLink
Consultant
Built on web services which can be used to pull reports and metrics without SQL queries

Pros and Cons

  • "Reporting is much easier and faster than Micro Focus ALM, with CA AC built on web services... Also, the data is more granular when it comes to tasks, iterations, sprints, and releases."
  • "One problem I see is that if there is a dependent user story - for example, if my team is working on one thing and there is a dependent user story from another team - we can have a dependency created but we don't know if there is a change of status from the other team. That is something which is very important for Agile Central to look into so that if the other team makes any changes we will be notified as well."

What is our primary use case?

It's mainly about test cases and automation of data. I, as a test automation architect, collect all that data and show the metrics.

How has it helped my organization?

We were using Quality Center, Application Lifecycle Management, from Micro Focus. That is hosted on an Oracle Database, whereas Agile Central is completely built on web services. If I have to create some metrics, I can do it via simple web services. Web services can be used to pull the metrics and this is much faster. I don't have to write SQL queries to do so. It definitely saves time, perhaps something like 30 percent.

Also, if I had to track multiple teams in Quality Center, I needed to go through different containers. With this solution, I can just add all of them and see them together.

Also, the data is more granular when it comes to tasks, iterations, sprints, and releases.

What is most valuable?

Some of the services are open so that we can plug in some other tools as well. If I need to do some metrics I can use those services and a simple "get" request from them.

Reporting is much easier and faster than Micro Focus ALM, with CA AC built on web services.

What needs improvement?

One problem I see is that if there is a dependent user story - for example, if my team is working on one thing and there is a dependent user story from another team - we can have a dependency created but we don't know if there is a change of status from the other team. That is something which is very important for Agile Central to look into so that if the other team makes any changes we will be notified as well.

As of now, we get an email alert but that's not sufficient. We can overlook it. What I'm suggesting is that they have something which populates on the team level so Team One and Team Two can communicate on dependent user stories. That would be really helpful.

In addition, reports are confined to teams. For example, I have five to six teams under me, if I have to pull a report, it will be mapped to a single team. I have to pull five teams' reports and then consolidate them to see what the metrics are. I don't have an option to actually add multiple teams to one report.

Finally, it's not capable of some things such as CI/CD. Agile Central is still not there. For CI/CD you need a separate tool and a separate repository called a GitLab. Then you need to run that through a continuous integration called Jenkins. I want to see a holistic approach when you're going with DevOps. There should be just one enterprise tool which is capable of all these things. As of now, Agile Central is just a test management tool.

What do I think about the stability of the solution?

The stability is good. I haven't faced any problems up until now. It has never hung. The Quality Center tool would hang. It has some client installation components but Agile Central is all on the server side. So it is much faster.

What do I think about the scalability of the solution?

The scalability is definitely good because for a company like ours, with a huge amount of data month over month and year over year - with every release the data piles up. We are not going to delete any of the historical data. So far the scalability is good.

How are customer service and technical support?

I have not contacted technical support.

But there is a voting option available for customizations. If I need an additional field or something needs to be enabled, if more than 60 percent of users vote for it, the CA team will enable that. They have responded well to these types of requests so far.

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

We were using Quality Center, Application Lifecycle Management. The reason for the switch is a decision taken by our leadership team and I don't have any insights into it. Perhaps it was licensing cost.

If you compare Quality Center vs Agile Central, the latter is much better.

What was our ROI?

It has helped save time, especially when it comes to testing. Uploading a bulk of test cases is much faster. And if the leadership team wants to get any insight from the metrics, pulling in metrics is not so difficult. That is something which I, personally, feel is great when compared with our previous tool, Quality Center.

What other advice do I have?

This solution will be of benefit to somebody who has knowledge of and understands web services, as it is built on web services - Representational State Transfer (REST). 

In our organization, we have about 400-plus users of Agile Central. It is used by the development managers, QA managers, architects, delivery managers, and scrum masters. These are all stakeholders in it.

Across our organization, everyone, including the development team, is following the Agile methodology. We are yet to get into DevOps. Agile Central is the tool which even other departments, like testing, are using.

Overall, I would rate Agile Central as an eight out of ten because of its performance. It doesn't get a ten because of the dependency issue which they need to resolve. And, on the whole, the tool needs to have more of a holistic approach for everything, such as CI/CD and a test management tool. As of now, it is still confined to being only a test management tool.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Frederic Ferrant
Scrum Master for a Big International Bank in Belgium at a financial services firm with 5,001-10,000 employees
Real User
Streamlines workflow for many simultaneous users

Pros and Cons

  • "I was able to create epics for our budgeting concerns and it helped me link everything together."
  • "I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."

What is our primary use case?

I was previously using it as a scrum monitor for the team. It helps with billing and the IT team used it, as well. I am very satisfied with this product. 

How has it helped my organization?

CA Agile is a product that really needs more than 100 teams working on it. It works best in big organizations. It definitely streamlines workflow for many users in tandem.

What is most valuable?

The program management is one of the most valuable features in the bank I work for. I was able to create epics for our budgeting concerns and it helped me link everything together. 

What needs improvement?

I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

We are a big company. We have about 170 teams, and we find it scalable. It has been used for more than 1500 people at our company.

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

I have experience with JIRA. I find Agile has an easier UI. Furthermore, JIRA was more of an IT tool, and Agile has both IT and business capabilities.

What's my experience with pricing, setup cost, and licensing?

It is expensive and may not be worthwhile for a small company. 

What other advice do I have?

When considering a new solution, I always consider:

  • UI
  • Price
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about Broadcom, Atlassian, Microsoft and others in Application Lifecycle Management (ALM) Suites. Updated: September 2021.
542,823 professionals have used our research since 2012.
Bryan Nelson
Agile Coach at T-Mobile
Video Review
Real User
Helps with getting the alignment between strategy and execution for product teams all the way to delivery teams

Pros and Cons

  • "Having that view into features and roadmap from product to delivery teams, and where they are going, then execute on."
  • "Its ability to scale."
  • "Tech support is very responsive, helpful, and available."
  • "It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
  • "A lot of the features that we would be looking to add, I am learning may not be within Agile Central, but part of another CA tool set."

What is our primary use case?

CA Agile Central is used for the lifecycle of Initiatives, Features, and User Stories, Defects: from concept through delivery

How has it helped my organization?

  • It really helped to connect the dots between what the overall vision was down to T-Mobile. 
  • Having that view into features and roadmap from product to delivery teams, and where they are going, then execute on. 
  • Being able to have the information, helping to facilitate those conversations, and just overall delivery. It is a really powerful tool for that. 

What is most valuable?

It really helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams. 

What needs improvement?

What I have learned is that a lot of features that I am looking for, in many cases, are part of a different tool set that CA offers. Really it is more learning about which features and tool, those features would be in. A lot of the features that we would be looking to add, I am learning may not be within Agile Central, but part of another CA tool set. It is about learning which tool that would be and how to integrate it. 

It would be nice if CA had those tools as part of a package rather than having to try and find multiple tools to integrate together. Some of the additional features that we are looking at would be better roadmapping capabilities and increased robustness around permissions. More of a view into the overall lifecycle of the portfolio items, so post acceptance of a story through the pipeline. Those are some of the key things that I would like to see. 

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

For the most part, we have found that it is pretty stable. There are the occasional outages, but for the most part, it is pretty reliable. 

What do I think about the scalability of the solution?

That is one of the advantages of CA Agile Central: Its ability to scale. Other tools that we have looked at or heard of, that is one of the limitations they have. The reason why we use Agile Central is its ability to scale across teams of teams. 

How is customer service and technical support?

It is really good. In addition to tech support, we have had the agile success program supporting us. They are very responsive, helpful, and available. When we have needed tech support, they have been able to help guide us through it as well. So, really helpful. 

What other advice do I have?

I would give it about an eight and a half. The reason why it would not be higher is because some of the things we are looking for we had to get other tools to plug into. Whereas, some of the other solutions we have seen out there, it is all-in-one tool set. 

Disclosure: IT Central Station 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.
MQ
IT Consultancy Manager at OdPe Business Solutions
User
Provides visibility into how teams are meeting business objectives

Pros and Cons

  • "CA Agile Central provides visibility into how teams are meeting business objectives."
  • "CA Agile Central helps the entire organization run like one powerful team."
  • "CA Agile Central does not have a workflow tool included."

What is our primary use case?

Execution of software development.

How has it helped my organization?

  • Plans and prioritizes to quickly deliver value. 
  • CA Agile Central provides visibility into how teams are meeting business objectives.

What is most valuable?

CA Agile Central helps the entire organization run like one powerful team. With the Project and Portfolio Hierarchy, we can have deep visibility into the work our teams are doing and how it ties to our business strategy and customer value. 

What needs improvement?

CA Agile Central does not have a workflow tool included. If possible, it may be necessary for some companies that this type of feature be included.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

Now, it delivers quarterly releases and has reduced the backlog, thereby increasing feature velocity while keeping the quality high.

Disclosure: My company has a business relationship with this vendor other than being a customer:
AW
Team Leader at CU Direct
User
The solution has the built-in ability to track bugs, and story reporting helps keep the enterprise clean

What is our primary use case?

We run our team and enterprise with Agile Tool. At the team level we determined and managed capacity, created tasks, and assigned hours to the tasks.

How has it helped my organization?

Reporting capabilities were better with CA Agile than VersionOne. Both were otherwise quite good. The primary reasons we switched were that our parent company used CA Agile, and that the solution has the built-in ability to track bugs. We still used Bugzilla though.

What is most valuable?

Easy drill down and drill up, creating a very user-friendly menu. The reporting on stories with features and without parent features was quite helpful to keep the enterprise clean.

What needs improvement?

Not as user friendly as VersionOne. At first I liked VersionOne better and was very disappointed in the switch. However, after a month or so I was quite happy with CA Agile.  

For how long have I used the solution?

One to three years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user797955
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: IT Central Station 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.
it_user272523
Senior Director at a pharma/biotech company with 10,001+ employees
Video Review
Real User
Crucial for our adopting of SAFe; logs 100% of our work, nothing can go under the radar

Pros and Cons

  • "When we went into Scaled Agile Framework, we could not have done it without the use of Agile Central. It allows us to scale our Scrum teams, and it also enables us when we do our remote big room plannings."
  • "Agile Central allows us to log one hundred percent of the work we do and it allows for no hidden work, so teams can't go under the radar with what they're working on."
  • "Ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new."

    How has it helped my organization?

    When we went into Scaled Agile Framework, we could not have done it without the use of Agile Central. So for us, it allows us to scale our Scrum teams, and it also enables us when we do our remote big room plannings.

    What is most valuable?

    Agile Central allows us to log one hundred percent of the work we do and it allows for no hidden work, so teams can't go under the radar with what they're working on.

    What needs improvement?

    Let's look at the portfolio level. Let's take a look at what capabilities are needed to scale our teams and really add them to the tool.

    For how long have I used the solution?

    More than five years.

    What do I think about the stability of the solution?

    The stability of the product is pretty solid, and the tech support that we get with it is phenomenal. We don't talk to anybody because we don't need to. We use the web application for all of our support management.

    What do I think about the scalability of the solution?

    For scaling, we look for Agile Central to be the leader for the software that's going to get us to the next 4.5 Scaled Agile Framework.

    How was the initial setup?

    I'm a proud user of Rally and Agile Central for the last six years and the ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new.

    What other advice do I have?

    When we go out and look for a vendor, we're looking for a partnership. So we're not looking for a vendor, we're looking for a partner.

    On a scale of on to 10, I would give it a solid 9.9.

    Disclosure: IT Central Station 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.
    it_user779079
    Engineer Manager at a tech services company with 5,001-10,000 employees
    Real User
    My teams describe their user stories and track the progress of their projects

    Pros and Cons

    • "My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."
    • "The effect of these kind of tools drives the way you organize things. It helps you shape the way you flow."
    • "It could improve by being self-organizing: user stories, different hierarchies, and different perspectives. Not just as a single hierarchical structure, but something that can be multidimensional."

    What is our primary use case?

    I use Agile Center mostly to do two things: 

    1. To manage my requirements and I have hundreds of thousands of requirements. 
    2. My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects.

    We are a former customer before it was acquired by CA. In that time, we were using just a fraction of what was there. This year, we started having more implementation and moving into the newest version. This has allowed us to use some of the high-end features like the label hierarchy, and it is good so far.

    How has it helped my organization?

    The effect of these kind of tools drives the way you organize things. You have to adopt yourself to the kind of workflow that it comes with. It helps you shape the way you flow.

    What is most valuable?

    Right now, it is the idea of having everything in place for both information and my project in a single network. Everybody who has different kind of users take advantage of the go through from the development guys to the project managers to management staff. Everybody has such great perspective of what is going on. It is very helpful.

    What needs improvement?

    There was some evolution, and as we have this old on-premise, it does takes longer. However, this complex requirement management, having different perspectives and different ways to organize the hierarchy of things, that is something that we value. It looks like the tool is at the beginning of having this new kind of approach, and we expecting different things from it.

    It could improve by being self-organizing: user stories, different hierarchies, and different perspectives. Not just as a single hierarchical structure, but something that can be multidimensional.

    For how long have I used the solution?

    Three to five years.

    What do I think about the stability of the solution?

    The stability is pretty good. I do not have any complaints about the abilities of on-premise version.

    What do I think about the scalability of the solution?

    I do not have a bunch of users. I have not tried scaling it.

    How are customer service and technical support?

    I use more the sales consultants than the technical support. The consultants are very knowledgeable. They should be more frequently available. I would like to have more of their presence, but their technical expertise and their willingness to help me is pretty good.

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

    We were not using a previous solution.

    How was the initial setup?

    I was not involved in the initial setup.

    Which other solutions did I evaluate?

    No, I am not thinking about changing. I need to have a lot of pain to start making changes.

    What other advice do I have?

    There is an ongoing change that is happening. CA has implemented with Rally, so they are still in the early emerging process. I think the evolution and integration of the two with product solutions will come after it.

    A solution is not more than a solution. It is a tool. It does not solve your problem. It is fixed by the tool. It is important to think about the problem that you are trying to solve to work with the consultants to come up with the right solution. The tool by itself could not solve your product issues.

    Most important criteria when selecting a vendor: partnership. That is the most important thing. To be there when I need someone to be connected with the evolution of my processes when I have difficulty, both technical or on the business side. That kind of partnership is what I value the most.

    Disclosure: IT Central Station 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.
    SM
    Director Of Enterprise Architecture at Best Western
    Real User
    Furnishes visualization of what's in flight, enables us to move the cards across the board, and plan our releases

    Pros and Cons

    • "The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker."
    • "The reporting, and being able to roll that up across the verticals, was an important selling point for us."
    • "I would like to see more Kanban support. As it stands, it doesn't seem to have the features or the layouts that the teams really need to be able to execute their tasks. It almost tries to force you into more of a Scrum style."

    What is our primary use case?

    Organizing all of our Agile work load, and projects that we have in the pipeline.

    It's been good. I don't know that it's best suited for Kanban which is the Agile style that we're using. It seems a little more focused on Scrum. So having some more Kanban methodology built into the product would be nice, but it does allow us to move our stories along the board, and have a good visualization of where everything is in process. 

    How has it helped my organization?

    It probably would be mostly the visualization of what's in flight, and being able to move the cards across the board, and plan our releases based on completed work, which really is the goal of Kanban.

    What is most valuable?

    The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker.

    What needs improvement?

    I would like to see more Kanban support. As it stands, it doesn't seem to have the features or the layouts that the teams really need to be able to execute their tasks. It almost tries to force you into more of a Scrum style.

    What do I think about the stability of the solution?

    Stability is great. We rarely have problems with it.

    What do I think about the scalability of the solution?

    The scalability is fine. We don't have a huge development team, so it doesn't really need to scale that big.

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

    We were doing everything Waterfall at the time.

    Which other solutions did I evaluate?

    We were looking at two different products, CA Agile and JIRA, and it seemed like there was less customizability for CA Agile, and that was important because we didn't want to have all the teams doing different things. So the lack of customization was a selling point for us.

    Also, the reporting, and being able to roll that up across the verticals, was an important selling point for us.

    What other advice do I have?

    The most important criteria when selecting a vendor are 

    • the support that we can get
    • the ease of upgrades
    • just having software that works. 

    Even though it's not part of our core business, a lot of the supporting tools need to work for us.

    Having the right tools is important, but more important than that is actually the culture, the people, and the processes. Take a look at your culture, your people, your processes. Make sure that those are what you need them to be and then select a tool that is going to work well with those objectives in mind.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    KS
    Director Of Tool Chain Automation at American Express
    Real User
    Gives us enhanced visibility, and data points to enable continuous improvement

    Pros and Cons

    • "It drives the conversation behind some of the pain points the teams have, based on the data that we're able to pull out of the system. As a result of that, we're able to make better decisions, to become better as a whole."
    • "More customization capabilities would be helpful. Providing a little bit more structure around how the system should be set up in terms of the hierarchy structure might be helpful as well."

    What is our primary use case?

    I have a couple of individuals on my team that help manage the utilization of CA Agile Central to make sure that we are being as mature as we possibly can for Agile practices.

    Performance has been good. It allows for a lot of customization, which has been very helpful, because we pull key metrics, report up to our unit CIO on certain areas.

    How has it helped my organization?

    The benefit of the solution is enhanced visibility, that is probably the key one. And it provides data points to enable continuous improvement.

    The ability, for example, to use the deep export report, and pivot tables and that kind of thing in Excel, has helped us out a lot.

    It drives the conversation behind some of the pain points the teams have, based on the data that we're able to pull out of the system. As a result of that, we're able to make better decisions, to become better as a whole.

    What is most valuable?

    The customization and the dashboarding that is available. We utilize some of the customization we put into play to help the business see inputs versus outputs, because we obviously use Clarity as well as CA Agile Central. Just being able to correlate the amount of hours someone is working versus what work they're getting out of Rally has been helpful.

    What needs improvement?

    More customization capabilities would be helpful. Providing a little bit more structure around how the system should be set up in terms of the hierarchy structure might be helpful as well.

    What do I think about the stability of the solution?

    The stability has been good. I don't think we've really had any problems. There have been a couple of issues, but they've been on our side in terms of Okta, the single sign-on solution we use.

    What do I think about the scalability of the solution?

    Scalability has been good. Again, the reporting, helps with it.

    How are customer service and technical support?

    A couple of my direct-reports have used tech support, and it's been fairly useful. If we don't have the solution developed at the point of time when we ask, they are more than willing to help us get to that solution, from a customized perspective.

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

    This was the solution that we had in place when I joined American Express - I'm a year into Amex. Seeing how teams utilized the solution when I initially joined, it wasn't streamlined, it wasn't something that we put much thought into. Creating a process to rally behind was, I think, a key aspect.

    How was the initial setup?

    I wasn't involved in the initial setup, but the upgrade, yes. I think the upgrade itself was straightforward. The rolling out across the organization was the complex part. Communicating the new benefits of the upgrade, and that kind of stuff, has proved to be difficult.

    What other advice do I have?

    When selecting a vendor to work with, the most important criteria are the scalability and the availability of the data to us, to be able look at in the reporting aspects.

    You need to have a good strategy in terms of rolling the product out, if its something that you're getting into the first time. Make sure you have a strategy surrounding how the team should use the product, what it should be used for. Some of the benefits, some of the sign posts for success, need to be set up along the way, as well.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user779133
    Manager Application Developer at a comms service provider with 10,001+ employees
    Vendor
    Brings visibility to scrum plans, captures tasks so they can be traced throughout the process

    Pros and Cons

    • "The visibility it brings to the plan, the ability to capture tasks, and trace them all the way through the life cycle. Providing that visibility helps both me and the team, or teams, to be able to understand where we are in the development process."
    • "The navigation within the tool sometimes is a little tricky for me. I'm sure with more use, more practice, I'll become accustomed to it, but some of the things just aren't intuitive."

    What is our primary use case?

    Planning for the scrum team.

    It has performed excellently.

    How has it helped my organization?

    It's the ability to bring visibility to the work. Previously we had another tool. Actually, it's a tool that I built, but it was limited in its ability to provide that start-to-finish visibility. And the traceability, from inception of the project to final test and deployment. Agile Central provides us that, not directly, but with its integrations to other tools in our tool chain, so that's a great help.

    What is most valuable?

    The visibility it brings to the plan, the ability to capture tasks, and trace them all the way through the life cycle. Providing that visibility helps both me and the team, or teams, to be able to understand where we are in the development process.

    What needs improvement?

    The navigation within the tool sometimes is a little tricky for me. I'm sure with more use, more practice, I'll become accustomed to it, but some of the things just aren't intuitive.

    For how long have I used the solution?

    Less than one year.

    What do I think about the stability of the solution?

    The tool is much more stable that I am. It's very stable. We've had no problems.

    What do I think about the scalability of the solution?

    Scalability hasn't been an issue. I wish it were, but so far the adoption has been good. We have a ways to go before I would imagine that there would be any scalability issue.

    How is customer service and technical support?

    I have not used tech support. We have an application administrator and he handles all that.

    How was the initial setup?

    Although I wasn't involved in the initial setup, I do know that there was some complexity to it. But not terribly complex. It was not hard to do, because it is a SaaS solution. It was basically: Give us the URL and point us to the training, and that was it.

    Which other solutions did I evaluate?

    No, Agile Central, had been on our radar for quite a while.

    What other advice do I have?

    For me, the most important criterion when selecting a vendor is finding a partner, versus just a vendor who's going to deliver a piece of software and wait for the money to come in.

    Don't think just about the tool, but think about the entire lifecycle of the tool, or the lifecycle of your application development. That's very helpful.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user779193
    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.
    it_user778923
    Senior Analyst Developer at a manufacturing company with 1,001-5,000 employees
    Real User
    Helps everything flow through the SDLC, breaks large projects into workable tasks

    Pros and Cons

    • "The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop."
    • "I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."

    What is our primary use case?

    We use it move projects through the software development lifecycle.

    It performs pretty well. It's nice that everybody throughout the whole process has access and is shown the relevant information to their part of the job, their part of the SDLC.

    How has it helped my organization?

    It really does help everything just flow through the cycle better; everybody just worrying about their small piece of the pie. And then the project managers can have a bigger overview of it. I like how it moves things. It moves development through the whole lifecycle. 

    What is most valuable?

    The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop. You don't have to worry about the whole big picture. It's nice how it breaks everything down into chunks.

    What needs improvement?

    I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    Very stable. I can't think of any down time we've ever had with it, to be honest.

    What do I think about the scalability of the solution?

    I don't think we've had to worry about scalability too much yet. We just use it for one piece of software still, right now. So it's still very small, we're almost kind of piloting it right now.

    How are customer service and technical support?

    I don't think we've needed to use tech support. Honestly, if we did, it wouldn't have been my job in our company. We have a relationship manager that I'm sure would take care of that.

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

    We were using Waterfall, which worked for decades, but it's definitely showing its age. I think they just wanted to switch to the Agile methodology and Rally was probably the best software to do that with.

    It just came to us and all of a sudden, management said, "Hey we're going to use Agile and Rally, and good luck." So we've been trying to learn it for the last year. 

    How was the initial setup?

    I wasn't involved in the initial setup. but they put it out pretty fast, and I have seen changes in it being made fairly quickly. So I would say it's pretty straightforward.

    What other advice do I have?

    The most important criterion when selecting a vendor is support. I know as a team lead for a developer team, I've personally worked with other third-party softwares that we integrate with. They've assigned people specifically to our account, which I'm sure happens at a lot of Fortune 200 companies working very big accounts. So the personalization is nice. We can have a weekly meeting with the same person, the same point of contact. If anything goes down, if we need assistance with anything, that person is available. Don't take the people out of IT. We work with computers so much it's easy to get out of touch, so keeping a personal touch is probably the best thing.

    I would rate it a "high eight" out of 10. It's a very capable software. Like I said, I just would like to see it presented a little bit more visually. It's definitely got some power but everything's got room for improvement. 

    Try to put yourself in the mind a developer and try and use it and see how you think it would flow. Really, it's a whole team collaboration. I'm not in the project support aspect, but I can empathize with them and think how they'd want to see things. Just try using it. See how you can move a project through it.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user778581
    Director Delivery at a hospitality company with 10,001+ employees
    Real User
    Streamlines defining user stories and tracking sprints, but dependency flagging should be easier

    Pros and Cons

    • "It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that."
    • "The main ways that I used it when I was in it day to day was keeping up with the burn rate within the teams. Also, to track at the feature level too, as far as how we were doing with actually being able to deliver that feature."
    • "The stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, ​they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."

    What is our primary use case?

    Most of our development teams are Agile, meaning they do development in two-week sprints. So they use Agile Central for the input of all of their user stories, all of their test cases. We just recently moved to Planview Enterprise so that we can actually start doing dependency mapping across features. 

    But it's mainly a way for all of the individual teams to define all our user stories and keep up with the overall tracking of how they're doing, sprint by sprint. 

    How has it helped my organization?

    It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that. 

    I think where we as an organization can get better - and this may be something that is out there in the functionality now, and we're just not using it - is better mapping across projects and having that cross-project dependency mapping.

    It's good, you don't have everybody in separate emails and Excel spreadsheets with all their various stuff and requirements, but we're still filing within the projects and not keeping track of everything across.

    What is most valuable?

    The main ways that I used it when I was in it day to day was keeping up with the burn rate within the teams. Also, to track at the feature level too, as far as how we were doing with actually being able to deliver that feature. So a lot of the in app features, where you can set up your dashboard; that's where I used it a lot.

    What needs improvement?

    I don't know that I can answer this, because I'm not using it day to day. I'm using CA PPM now, and I know we're looking to integrate Agile Central into CA PPM, which I believe is an option. 

    When I used it before I would say the stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success.

    For how long have I used the solution?

    More than five years.

    What do I think about the stability of the solution?

    I think it's been fine. We used Agile Central when it was Rally and we were actually in the beta, the first version, without really having any problems with it being down or not running. I would assume the SLA is somewhere in the 98, 99 percentile. That seems to be the case.

    What do I think about the scalability of the solution?

    Regarding scalability, I don't know. I only know how we're using it as a company. Like I said, I think there's probably more that we could be doing. We're just not quite there yet.

    How are customer service and technical support?

    I haven't had to use tech support, myself. I don't know if the direct teams have. But, like I said, we haven't really had any issues with the tool.

    We had a guy who was an Agile coach come work with several of the teams. So we've kind of had onsite support from a coaching perspective; not necessarily the ins and outs of the tool. I think he was able to provide some technical support as needed to get the teams up to speed.

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

    I can't remember what we were using previously. It wasn't JIRA. There were some teams using another user story repository before they started using Rally, now Agile Central.

    We decided to move to the Agile development framework. Based on that it was clear that to do so you need a platform for your user stories. And I think it was just one of those next steps in the evolution of moving to the Agile development framework.

    We switched because we wanted everybody in the same platform. I'm sure money was somewhat involved, as well.

    How was the initial setup?

    I wasn't involved in the inital setup from a technical perspective. That happened on our technology side. But I was one of the first ones to use it, five or six years ago.

    In terms of it being complex or straightforward to learn, the team that I worked with had training on it. So once we had training on it, it was very easy to understand. I don't know I if you could just come in and use the tool without any training on it.

    I think in order to use the tool you have to understand what the Agile development platform is. You have to understand what a user story is. You have to understand how that connects to the test cases. You have to understand the background of why you'd be using the tool before you can use the tool. You couldn't just sit someone down and say, "Go." There has to be a little bit of training on why use the tool before you use the tool.

    What other advice do I have?

    There hasn't been anything surprising within Agile Central. As CA has taken in Clarity, which is now CA PPM, what I'm learning here at the CA World conference is the full breadth of everything we can do better under the CA umbrella. I don't know if there's anything particularly surprising about Agile Central. There's JIRA. They're all fairly similar. So there's nothing that wowed me there.

    When it comes to the most important criteria in selecting vendors, budget always plays into, but I think it's also the breadth of the solution. I think that's one of the reasons we've stuck with CA, because now we're using several of their tools.

    I rate Agile Central six to seven out of 10. For it's core functionality, it works. I think when you get into the details, there are some improvements that could be made as far as being able to better track across. There is dependency functionality now that you can use, but I think there are always improvements that can be made. But for it's core functionality, it works.

    In terms of advice to a colleague who is researching a similar solution, I think most people who are developing in an Agile way are familiar with it now. I might give some tips on dashboards that I've set up. If you're familiar with Agile you're familiar with Agile Central, really. The tips and tricks that I've given my colleagues are more around how to build out dashboards to be able to see, in that first glance when you walk in, your view for the day. So it would be around the dashboards. 

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user778926
    CEO at ZAPTEST
    Real User
    It has allowed the quality assurance team to keep all information in sync with the application requirements and user stories

    Pros and Cons

    • "It scales very well. It improves in technology constantly and gets up to speed with the latest and greatest."
    • "​It is very stable. It has been on the market a long time."
    • "It has allowed the quality assurance team to keep all information in sync with the application requirements and user stories for our general development."
    • "As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."

    What is our primary use case?

    The entire application lifecycle from user story to the quality assurance for the testing. It has performed great. It has a great set of features which address the whole process. 

    How has it helped my organization?

    It has streamlined the entire process of development from getting the requirement for the application, supporting all the testing processes, and reporting all the defects back to development.

    What is most valuable?

    Its integration of support of the quality assurance process. It has allowed the quality assurance team to keep all information in sync with the application requirements and user stories for our general development.

    What needs improvement?

    We would like maybe to have more integration with test automation. As it is right now, it does not support automation of the quality assurance process. It just supports manual testing. 

    What do I think about the stability of the solution?

    It is very stable. It has been on the market a long time.

    What do I think about the scalability of the solution?

    It scales very well. It improves in technology constantly and gets up to speed with the latest and greatest. Basically, all the functionality. 

    How is customer service and technical support?

    We use the technical support once in a while. They are very responsive and knowledgeable.

    How was the initial setup?

    The initial setup was fairly streamlined.

    What other advice do I have?

    If you are looking for a stable ALM that supports the agile process, this is the solution to go with.

    Most important criteria when selecting a vendor: functionality and stability. So, for it to be a stable technology with a solid road map.

    Disclosure: IT Central Station 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.
    it_user778848
    IT Manager at DISH Network Corporation
    Real User
    It allows us to work in a more dynamic fashion and track more of the development lifecycle, however it requires better scalability.

    Pros and Cons

    • "With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."
    • "It allows us to work in a more dynamic fashion and track more of the development lifecycle."
    • "It requires better scalability for the implementation of the whole suite. We do not use it in that fashion, and visibility is sometimes a problem."

    What is our primary use case?

    Managing our development life cycle. In the ways in which we use it, it has been adequate.

    How has it helped my organization?

    We have gotten away from so much paper, which is more dynamic. It allows us to work in a more dynamic fashion and track more of the development lifecycle. 

    Essentially, we are replacing TeamTrack. TeamTrack was more of a waterfall type of process and documentation for us. In fact, I have tried to go back and look for some of those old projects and it is not possible to find them. Although with this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot.

    What is most valuable?

    Better requirements. As the story is developed, there is not so much time devoted to clarification of requirement. It helps us get a better product to production.

    It is a more detailed process for a lifecycle. We go from requirements to implementation. I use it with my teams for time management as well, time reporting and management.

    What needs improvement?

    We are not on the most current version, so it may have been addressed, I have not really seen the new product yet. 

    I would like to see more in the way of capitalization. I spend a lot of time on capitalization. Working out capitalization, it is largely manual work, where it does not have to be. The tool, I think can support it. When it is a story, capitalization in the current version of the solution we are using, occurs at the task level. I would like to see it roll up a little better to the story level, then up to the feature.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    I have not had any issues with stability at all.

    What do I think about the scalability of the solution?

    It requires better scalability for the implementation of the whole suite. We do not use it in that fashion, and visibility is sometimes a problem.

    We are housed with our business units and we are a Fortune 200 company, but not all the elements of the business units can always see an aspect of a project or stories. They can't get those stories, which are not necessarily visible. I happen to manage development on a product that has impact across all business units, across all business departments. So, I have to do some housekeeping, and maintenance in trying to broadcast what we are changing about the software to those other units that do not necessarily have the ability to see those changes, or awareness that those changes are happening.

    How are customer service and technical support?

    I have not used technical support. I work with a person in-house who liaises with CA.

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

    We underwent a philosophical change, if you will. We consciously chose to move away from waterfall as a development mechanism to more of an agile framework. We are not a traditional agile approach, because of the nature of our business. I would really like to see more flexibility, flexibility in adopting hybrid approaches. 

    How was the initial setup?

    I did not find it to be complex. I find the methodology to be more complex than the tool.

    One of my development teams was one of the first teams to use and embrace it. It was a new team, so it was an easier transition for that team to begin using this product over the other tools that we use.

    What other advice do I have?

    Have a clear vision of where you want to go, and make sure the elements of the tool accommodate that vision.

    Most important criteria when selecting a vendor: 

    • Cost
    • How well we can adapt the practices of the vendor to have some pretty clear direction on where we want to be, not necessarily how to get there. It has to be a partnership. 
    Disclosure: IT Central Station 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.
    it_user778650
    Senior Consultant at a tech services company with 5,001-10,000 employees
    MSP
    Facilitates recording user stories and tracking burndown, velocity, and defects

    Pros and Cons

    • "Helps me determine how fast I can launch, go to production."
    • "We would like more meaningful, customizable dashboards."

    What is our primary use case?

    We use Agile Central to record all our user stories, features, and then to track down the burndown, velocity, defects.

    How has it helped my organization?

    My launch. How soon or how fast can I go to production, is what this helps me design.

    What is most valuable?

    From a solution perspective ,we use the Burndown to see whether the velocity for the entire sprint is okay or not. Am I going, did I pass? Do I need to prioritize? How many impediments do I have? What does my backlog look like? Have I taken up enough in that given sprint? Will I be able to deliver all that? It helps me track that down.

    What needs improvement?

    Primarily, producing more meaningful dashboards is what we have given to them, saying "customizable." 

    Customized reporting, so that rather than going to them, if I can produce my own UI, that would be meaningful.

    What do I think about the stability of the solution?

    The solution is stable. 

    What do I think about the scalability of the solution?

    Scalability is good. Based on what we have done so far, it is scalable. No problems faced so far.

    We have a solution group as well, Testing Services within our organization. If we are looking for any modification within the tool, we can go to them saying, "Okay, when the tool came in it had a particular layout of, say, 100 fields. But based on my requirements, I want to improvise that, I don't need them. Eighty fields are good, but the remaining 20 fields I want to change over to this, make it more meaningful, more for my own organization. Customization.

    So when we go to the Testing Services group, they take their time to have it implemented on Agile Central and then we pull a report. For example, the Defect Dashboard. Now, the Defect Dashboard came with some basic things. My anticipation regarding the Defect Dashboard is, I need to see more details, like what was the root cause, sub-root cause. I track it down to that level. So that customization we can easily do. That makes it helpful.

    How are customer service and technical support?

    As I said, we have a Testing Services group, so we just give our requirements to them. If they needed to contact CA for any sort of modifications the would have done that. We don't know.

    We don't directly interact with the CA technical team. We talk to our technical team and they might internally talk to them.

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

    What we used to do in, say, HPE Quality Center, is now getting done Agile Central.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    it_user779259
    SCRUM Master at Transunion
    Vendor
    Capacity and release planning help me determine potential velocity for each of our teams

    Pros and Cons

    • "Gives me a dashboard where I can see what things are not being worked on, what things are blocked."
    • "It helps me evaluate teams' historical performance using velocity charts."
    • "We've actually used it for virtual PI planning. We have teams in different locations, and we actually virtually do PI planning, big-room planning, using the tools."

      What is our primary use case?

      As a Scrum Master, helping the product group define feature stories, and portfolio management, and helping manage the teams, their scrum backlogs, their performance, and velocity.

      It has performed well.

      How has it helped my organization?

      It helps us not to have to use any sticky notes. We project up every day, on a daily standup using the iteration planning part of it, and using the post-it portion of it in the Kanban, to communicate daily with the team on how things are going. 

      It helps me to have a dashboard where I can see what things are not being worked on, what things are blocked, for instance. It helps me evaluate teams' historical performance using velocity charts. 

      Capacity planning and release planning for the next PI help me figure out what the potential velocity is for each of the teams. It rolls it up, so that across teams we can figure out how many features we think we can get in for the next PI. 

      And we've actually used it for virtual PI planning as well. We have teams in different locations, and we actually virtually do PI planning, big-room planning, using the tools so it's been really helpful there.

      What is most valuable?

      I like all the features of it, especially the Team Planning board, and the Release Tracking. It helps us track the features and stories that line up with those features. I like it for the most part, and how it works.

      What needs improvement?

      I can't think of any off the top of my head.

      What do I think about the stability of the solution?

      I have found it to be fairly stable. I know there have been a couple performance issues when we're all on it, but I think that was maybe about six months ago, maybe when we went to the cloud. But since then I haven't experienced any performance issues. I think that's really gone down.

      What do I think about the scalability of the solution?

      It scales well in terms of setting up the workspaces and the hierarchy, we find that that works really well.

      How are customer service and technical support?

      We've used tech support very little. But we're satisfied with the support we've received.

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

      We were using Team Foundation Server (TFS). But some people were using JIRA, so there really wasn't a consistency there. We switched because it was really determined that it was probably the best tool out there to use.

      How was the initial setup?

      It was actually pretty straightforward, and it did seem more intuitive than what we were using, which was TFS from Microsoft.

      What other advice do I have?

      When our company is looking for new products, and new vendors, the criteria is more of a consensus, or global acceptance across the board, and executive support. I'm sure price tag comes into play.

      I give it an eight out of 10. I tend not to give anything a 9 or a 10, because I always think there is probably room for improvement on it, not that I can't think of anything right now. It's not perfect, but it's definitely very good.

      I would tell colleagues looking for a similar solution that Agile Central is very easy to use, and it's easy to build dashboards. It's very intuitive. I'd recommend it.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user779217
      Service Manager Build Automation at a healthcare company with 1,001-5,000 employees
      Vendor
      Provides visibility across the team, how much free time, how many deliverables

      Pros and Cons

      • "Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
      • "There's a lot of support for Scrum and Agile, but it needs something for the Kanban side."

      What is our primary use case?

      To manage our work in a common way.

      In terms of performance, we're just getting started on it. No issues so far.

      How has it helped my organization?

      It helps me plan the work. Also helps me plan an estimate of how soon or how far out we'll be able to deliver something. Those are big things.

      What is most valuable?

      • Visibility across the team
      • Ability to see the team's capacity - how much free time, how many deliverables

      What needs improvement?

      It could use some templates and patterns that we can follow. There's a lot of support for Scrum and Agile, but something for the Kanban side, I'd really appreciate that.

      For how long have I used the solution?

      Less than one year.

      What do I think about the stability of the solution?

      I don't have a comment on this because we've just started to use it. From what I've heard from other users, it seems like a good, stable product.

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

      We were looking for a tool to support our work, to support our process, especially in the Kanban area. Without that, we started to use Excel, we started to use SharePoint but, really, they were not giving us value, the visibility. Then we started to look for something which is specifically made for supporting this kind of process.

      What other advice do I have?

      When our company is looking for a new vendor we float an RFP; there is a set of criteria, we get together, list down all the requirements that we have. Any tool that we look for we look for, we typically look at four different vendors, four different tools, and try and compare them.

      I would recommend CA Agile, certainly, but it all depends on what processes you have and whether it's a fit for them. 

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user663606
      Quality Assurance Manager at a transportation company with 1,001-5,000 employees
      Vendor
      Gives us visibility into what we're doing, but needs better user-story management

      Pros and Cons

      • "The Defect feature. In one view you can see all your defects and you can push them into the different releases."
      • "I wish there was a view, like the Kanban view, where you could see the parent, and see all the children visually, so you could drag and drop where you want it to go. Something like that might help."

      What is our primary use case?

      Release planning, test case writing.

      It's performed plenty, I'm happy with the performance.

      How has it helped my organization?

      I get to see what we have, what test cases we need to deliver, per release.

      It gives us the visibility into what we're doing and how we're doing on a day to day basis, to see if we need to refocus or to try to change things before it gets down into the negative. The daily iterative working part of it is what I like. And I get to see the visuals of what's going on.

      What is most valuable?

      The Defect feature. In one view you can see all your defects and you can push them into the different releases.

      I also like the Release view, where you can select different user stories and just dump them into the releases you want them to be in.

      I also like the reporting. I can see my Burndown, my Burnup, and other reports that we use to see if we're delivering on time.

      What needs improvement?

      One thing that my team struggles with is when they have so many user stories. You have the parent's story, and then you have a child of a child of a child and it goes "down into the drain." Sometimes it's hard for them to quickly search for a user story. I know there is a part where you can just type the user story number, but that's if you know it. 

      I wish there was a view, like the Kanban view, where you could see the parent, and see all the children visually, so you could drag and drop where you want it to go. Something like that might help.

      What do I think about the stability of the solution?

      It's been around for a while so it's pretty stable. 

      I'm assuming it's our infrastructure, but since its web-based, at certain times of the day, it's slow. At certain times of the day I've noticed it takes a while for the page to come up and for updates and the like. Sometimes you have to shut it down and restart.

      I opened up a ticket with CA about it. I don't think I got a response back. It's been a while, I didn't look back into it, and nobody contacted me about it.

      What do I think about the scalability of the solution?

      It scales.

      How is customer service and technical support?

      Generally I'm satisfied with the tech support I get from CA.

      How was the initial setup?

      I wasn't involved in the setup with my current company; my previous company, yes, I was. I think it depends on who you're working with. With the person I was working with in my old company, it was straightforward.

      We had that one on one relationship with CA, and they were on site to help us out. If we had to be on a call for anything they were there.

      Which other solutions did I evaluate?

      At my old company we had a demo for VersionOne, then Rally (now Agile Central), and one other tool. One of the reasons we went with Rally is it was easier to use than VersionOne. The reporting was great, it was what we were looking for. And at that time it had another feature called Timesheet, that became the Timesheet in Agile Central.

      What other advice do I have?

      When selecting a vendor, what's important to me is that the product be user friendly. It also has to be able to produce. My bottom line is the outcome, so I want to see that it can help deliver correctly, on time, within the budget. Also resource planning, resource management, those are the kinds of things I'll put into consideration if I'm looking for a tool to use.

      I think CA has been consistent in trying to improve Agile Central, but they also still have room for improvement, so I give them seven out of 10.

      I would tell colleagues to try Agile Central because of the features I noted above. And then, I don't know about VersionOne, but the support for Agile Central is also great.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user779166
      Senior Developer Analyst at a retailer with 10,001+ employees
      Vendor
      Helps us find our user stories and allows us to see what our team members are working on

      What is our primary use case?

      It helps us find our users stories and allows us to see what everyone on our team is working on, and if we have any blocks.

      It's performed pretty well.

      How has it helped my organization?

      It allows our team, and all the external teams that are waiting on us for dependencies, to see where progress is on the stuff that we're about to develop and deploy.

      What is most valuable?

      It integrates well with the things that we have. We're able to tie our stories in with our code repository, so that way our check-ins are tied back to our user stories.

      What needs improvement?

      I can't really think of any additional features that it needs. It pretty much has everything that we use it for.

      What do I think about the stability of the solution?

      It's been really stable. There have been some downtimes with it, but they're fairly short.

      What do I think about the scalability of the solution?

      I'm not sure how well it scales. It's worked so far with our team.

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

      I know a lot of our teams are using JIRA. The switch is because it has more features.

      What other advice do I have?

      When looking to select a new vendor, our criteria are

      • price 
      • feature set.

      I give it a nine out of 10, just because of the slight downtimes, which make it hard to go in and update things.

      Definitely look into it, because of all of the different tools for user stories and test case management. It's been one of the best I've experienced.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user778977
      Senior Engineer Manager at a manufacturing company with 1,001-5,000 employees
      Real User
      Makes it easy for us to track metrics, team velocities, what we should plan for/anticipate

      Pros and Cons

      • "The metrics - collecting metrics. It's because we've used several other tools in the past, and they don't give you a full indication of how well your teams are performing, at a portfolio level, at a product level, and at the team level."
      • "In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."

      What is our primary use case?

      We are promoting SAFe within our organization and we have a organization that actually follows the Scaled Agile Framework. We're using Agile Central right now to track our users' portfolio items, our product features, our product backlog, our iteration status, and to track metrics. That's what we're using it for right now.

      It's been pretty good. We've been using it for the last two and half years. We've tried a couple other products in the past, before we moved on to Rally CA or Agile Central 2. So it has really worked out very well.

      What is most valuable?

      The metrics - collecting metrics. It's because we've used several other tools in the past, and they don't give you a full indication of how well your teams are performing, at a portfolio level, at a product level, and at the team level. CA Central actually makes it very easy for us to track metrics for our trains, for our teams, to find out what the velocities are, what we should plan for, and what we should anticipate.

      How has it helped my organization?

      It really helps us scale in terms of our organizations, and be more predictable. That's one of the biggest advantages that the Agile Central tool has provided us. As I said, gathering metrics and being more predictable, that really helps us in the long run.

      What needs improvement?

      We have a couple of pain points, but I can't remember off the top of my head what those are. Every once in a while we'll submit feedback through their online tool. 

      In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool.

      For how long have I used the solution?

      One to three years.

      What do I think about the stability of the solution?

      It's quite stable, we haven't had many issues. Every once in a while, we have had some problems with the total number of features that it runs into but other than that, nothing else.

      What do I think about the scalability of the solution?

      I haven't had much of a problem with scalability. It seems quite scalable.

      How is customer service and technical support?

      There are times when we struggle with stuff but we haven't really called customer support yet.

      There are some features of the product, a couple of the things, that were not really intuitive. We just had to go through online documentation. They have good online tutorials, support, documentation, where you can go and read up on things, so we just used that.

      How was the initial setup?

      We started using the product, so we were more of the consumer than the actual installing team. That was done by a different team.

      Which other solutions did I evaluate?

      We explored a lot of tools when were trying to promote SAFe or Agile across the entire organization, so we moved through the Scaled Agile Framework. And then there were only three or four tools that we explored, and Rally, or CA Agile Central, was one of those that we thought would really work.

      We looked at VersionOne, the Atlassian tool, I can't remember the name of it, I think it's just JIRA, and Rally.

      What other advice do I have?

      What's most important to us when selecting a vendor are 

      • ease of use
      • how intuitive it is
      • customer support
      • metrics, for us, that is really important.

      I give it a solid eight out of 10 because of the way that things are laid out. It's more user friendly, it's intuitive. As I said, it's easy to use. I think they've done a good job with the metrics in general.

      I would tell colleagues who are looking at this type of solution to do their homework and see which one works best for their company, for their teams, and for their organization. We went with Agile Central because of a lot of the things it provides, in terms of the features. I know every company is different, every team is different, and things that might serve their needs may be different than what is useful for us. My best advice would be to do their homework and explore.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user778893
      Senior IT Manager at a insurance company with 201-500 employees
      Vendor
      It has allowed us to experiment with approaches that we would have been a bit afraid to experience before

      Pros and Cons

      • "It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows."
      • "We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them."

      What is our primary use case?

      Primary use case is agile development and Mode 2 development.

      It has performed really well. We have taken some teams that were non-Agile and tried to do a combined approach. This eliminated some of the heavy documentation that we were used to with waterfall. We have been able to deliver our integration between CA and HPE ALM in a period of time that is about half of where we were before. 

      What is most valuable?

      It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows. We are able to create those stories in a more of a just-in time approach. Since we are doing combine and not scrum, we want to get those stories on as we think of them and immediately work on them instead of waiting for a time box. So, it was the ability to adapt quickly. 

      How has it helped my organization?

      We are very new on agile and Mode 2 devolvement. It has really allowed us to experiment with approaches that we would have been a bit afraid to experience before. So, it has allowed us to try new things and to take risks. 

      What needs improvement?

      When you copy a story, I would like the attachment to copy with it. This is a big one for us. We do requirements in one sprint, then do development in the next, which still is a little bit of waterfall. So when we copy those requirement stories and they become development stories, the attachment does not come with it. So, it is a lot of manual effort to do that. It would save us a lot of time. 

      We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them. 

      Also, there are a few things in the way things trickle up from category to theme to feature that I do not really like. I wish there would be some enhancements there.

      For how long have I used the solution?

      One to three years.

      What do I think about the stability of the solution?

      It is very stable. It was purchased by CA from Rally, which I was familiar with beforehand. It has gotten better since CA has taken over, adding some new features, but it is a very stable platform. 

      What do I think about the scalability of the solution?

      Since we are more of a Waterfall shop, as we bring new teams into the agile approach, I think it is quite scalable for us. However, it will probably be a more longer term poll. 

      How are customer service and technical support?

      We have used them quite a bit. They have been very responsive. We use a competitor's tool for our waterfall approach. I won't say which competitor it is. However, we have been very happy with the speed and the availability of CA's technical resources.

      Our issues have been lower scale problems, but we do not have a support staff to manage Agile Central. What we found was technical support was not only giving us the ability to get help, but also helped us evolve our support team into a team that can be managed well on its own. So, I have felt they have helped us in a lot of ways.

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

      We did not have a solution in place. We were looking at Mode 2 and agile teams and we knew we needed something. Putting post-its on the board was not going to work anymore for a company of our size. While we still do some post-it exercises, it all ends up in Agile Central and we knew we needed something to manage this. We still have PM's who want to see portfolio management, so we knew it had to be digital. It could not be paper anymore.

      How was the initial setup?

      We took our instance and revamped it from the beginning, which was very straightforward.

      Which other solutions did I evaluate?

      We were. We were looking at a few. Not sure if I can say which.

      They were not providing a solution that was mature and developed. They were providing solutions that they wanted us to be like a test customer on.

      What other advice do I have?

      They still feel like a small tech company. The support we have gotten and the way they have managed or accepted some of our enhancement requests. They still treat it like a small company, like Rally was before they purchased Agile Central. They still have that feel, knowing how big they are and seeing how they can act small. It is really nice.

      Make sure your agile processes are really well-defined before you go out into the market and look for a tool. Tools do things differently, they call things a feature in one and a subfeature in another. Make sure your processes are defined, and once you have that, look for your tool after that. Do not look for your tool first.

      Most important criteria when selecting a vendor: We have price, which I would not say is our most important. We are looking for more of a fit and finish to our process, though price is really important to us. One of the things that we look at is: We want to create a really good process, then find a tool that fits that process. I think a lot of customers do it the other way. So, if our process is mature and we like it, the tool really needs to fit that.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user778653
      PMO Manager at Chipotle Mexican Grill, Inc.
      Vendor
      It keeps our teams all in the same place in terms of where information is stored

      What is our primary use case?

      Software development and infrastructure.

      What is most valuable?

      Sprint planning and overall work management of the stories and the project lifecycle.

      Sprint planning is valuable because it keeps our teams all in the same place in terms of where information is stored. We always know what the status of a project is and anybody can see it.

      How has it helped my organization?

      • Ease of use
      • Visibility

      As a PMO Manager, I need to be able to look and see what the project status at any time without having to go ask somebody or look for a status report. So, I could go there and see exactly what percentage is complete, what the blockers might be, and just see who is assigned to what, so I can look at resourcing.

      It has made our company more organized and it is helping us be more true to the agile principle. When I came to the company, we did not have any agile practices in place. So, it has helped us, because it gives us a framework to put the agile practices in place. 

      What needs improvement?

      The integrations with the PPM tool and making sure those two work well together. 

      Improved engagement with TFS, because we still used TFS for code management. There is an API between the two. I think that the APR could be easier to set up and the API could be a little more fluid in terms of when the code is checked in. It really relates to how a project is updated based on that.

      For how long have I used the solution?

      Three to five years.

      What do I think about the stability of the solution?

      Stability is better. A couple years ago before CA bought it, we had a lot of problems. Now, we do not have as many problems. So, it has been good.

      What do I think about the scalability of the solution?

      Scalability is getting better. It used to not be as good, but they are adding some features that make it easier to build portfolio items in.

      The problem before was that there were just a lot of little bugs where you create a project in one place and it would not continue to exist in another. Also, there were not very good templates or anything. So, they are improving on that. 

      How are customer service and technical support?

      I have not really used the technical support.

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

      We did not have a solution when I started. I picked it because I was familiar with it from a previous company. I actually used it for a couple years before that, as well. I just knew we needed something that we could hit the ground running with pretty quickly.

      How was the initial setup?

      I was involved in the initial setup and subsequent upgrades. 

      I am not really sure how it is now to set up. If you are putting into a GreenField brand new product, I do not know how that would work now. Previously, it was just figuring it out on your own.

      Upgrading was pretty straightforward, especially if you are used to using any of the agile tools in the agile practices. Once you get used to some of the unique namings for Agile Central, or formerly Rally, it is pretty straightforward. It is a like-for-like, in terms of what you have learned, in terms of being agile in what you learned on what you are doing on a day-to-day basis. 

      Which other solutions did I evaluate?

      The vendors on the shortlist would be TFS's Project Management through Microsoft, ServiceNow's Project Management, and JIRA.

      Earlier on, we went a little faster and we did not do a full software evaluation. We actually are doing a tools assessment now. We are going to be looking at replacing CA, possibly, because we want to make sure we have the right tools. We want to make sure that they flow between all the different tool sets that we have. 

      What other advice do I have?

      It has performed well so far. It has improved over the past couple of years.

      For any product, do a full software evaluation and make sure you actually test them side-by-side with like-for-like test cases. Then you know exactly what you are getting yourself into. Otherwise, you build out and realize it might not be the right product for you. So, a full software analysis is important.

      Most important criteria when selecting a vendor: Initial support is always important. It is always great when you can have a few free hours to have somebody to come in and help you understand the idiosyncrasies of any software, figuring out exactly what the best way is for it to be set up. Otherwise, you are just trying by trial by error. So, that is important. Also, stability is important.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558372
      Director, Curriculum Development at a tech vendor with 1,001-5,000 employees
      Vendor
      At the portfolio management level, we can see everything at one glance.

      Pros and Cons

      • "It's designed around Agile, so it has all of the pieces that match up with the process."
      • "I'd like to be able to color code timeboxes, so I have an easy visual way to track the success of sprints."

      What is most valuable?

      It's designed around Agile, so it has all of the pieces that match up with the process. For us, at the portfolio management level, we can see everything at one glance, all of the projects, where they're at; and, at the iteration level, we’re able to populate the iteration, and view progress reports on it. We've recently moved all of our defect tracking onto it also - it's nice to be able to pull defects right into sprint plans.

      How has it helped my organization?

      • We're using it to manage the training content development we're doing, so it's kind of a one-off case. It's not your typical agile project, but so far it's working well, and we're able to incorporate most of the agile methodology into our processes. We get all of the transparency that comes with the tool; so we have a clear view of what's happening with all of our projects, what state they're in, and where all the pieces are. Blockers stand out, so they're getting more attention. It's become our single location for project information. Although there's been a bit of a learning curve for the team (more around the processes we're using than with complexity in the product), I've had several team members tell me that it's a good product that they enjoy working with.




      What needs improvement?

      I'd like to be able to color code timeboxes, so I have an easy visual way to track the success of sprints. Workflow is not a strength, we've cobbled together our own workflows around changes in State and Ownership.

      For how long have I used the solution?

      About a year now. What we're doing in CA Agile Central is pretty stable now, although we still tweak our own internal processes from time to time. Still exploring and learning the wonderful world of Agile.

      What was my experience with deployment of the solution?

      We weren't involved in it.

      What do I think about the stability of the solution?

      It's been extremely stable for as long as we've been using it.

      What do I think about the scalability of the solution?

      I see no problems with scalability. In addition to what we're doing, I know our Services team and Product Development team are using the product, so I expect scaling is not an issue.

      How are customer service and technical support?

      Customer Service:

      Haven't really used it.

      Technical Support:

      Haven't really used it. Which I like.

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

      Spreadsheets and MS Project. CA Agile Central is designed around Agile methodology, so it was a perfect fit for the processes we wanted to put in place. We couldn't do the things we're doing now with the previous products.

      How was the initial setup?

      I wasn't involved in setting up the product itself. I jumped in after it was already in use.

      What about the implementation team?

      Wasn't involved.

      Which other solutions did I evaluate?

      The decision to use it came from our development team. The whole development team is using it. Our Services team has been using it for years.

      If you're focusing on agile, this is the right product to use. It's built around it. I've tried to do things with MS Project and that sort of thing, and you just can't manage it the same way. It's just not built for the same kind of cycle.

      What other advice do I have?

      It is a well thought-out solution. It's a great centerpiece for Agile methodology. It works.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user631626
      Reservations Supervisor at a transportation company with 1,001-5,000 employees
      Vendor
      I can track each iteration of each project, and see where I'm at and where other people are at, visually.

      What is most valuable?

      I like it because I have several projects, and it keeps me on track for each one. So, I can track each iteration of each project, and see where I'm at and where other people are at, visually. I guess maybe the iteration planning and tracking status is the most valuable feature.

      How has it helped my organization?

      It has helped a great deal in the fact that we are able to take small chunks of data and get them actually moved forward end to end. Previously, we had to wait several months before something would actually be available for the end user. This has helped us to break that and to move forward quickly.

      What needs improvement?

      I think I'd like to be able to color-code the words more easily, not just the side. You can change the color on the side, but to actually change the font color would be useful.

      Currently, I use an HTML color font to change the title of a user's story or something. If, instead of having to put in the HTML version of it, to make it change the color of the font, and I could easily change the color of the fonts, it would be a lot better.

      For how long have I used the solution?

      I have been using the solution for two years.

      What do I think about the stability of the solution?

      I think occasionally it will slow down, particularly when we have a lot of users on the same project, especially around stand-up time or whatever, because we're spread out across the country, so we usually do it by phone. So when everybody is on the project at the exact same time, it will slow down a little bit.

      Also, if I make a change and somebody else makes a change, you can't retain both changes. It doesn't accept both. The first one who finishes, who hits Enter, Save, Done or whatever, will get the change.

      Then, it will warn you. It will say, "Do you want to keep your changes or the other person's changes?" But you don't know what they are changing, and they don't know what you're changing!

      What do I think about the scalability of the solution?

      It slows down a little bit if you have a lot of information in there. It seems to work really well, however.

      I like the personalization of the home screen because I may not want to look at everything, i.e., the same things that other people want to look at. So it's nice to be able to personalize my home screen. I have a lot of stuff on my home screen, and it seems to be able to handle it just fine.

      How are customer service and technical support?

      We have an administrator, and I've had to have people added back in because they don't go in there and use it, and get suspended. Then they ask, "How come my name's not in here?" So you have to respond: "Because you never use it."

      I haven't really had any help from technical support.

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

      We previously used a different solution. We switched to be able to move more quickly to a resolution. Because the industry changes quickly, we can't still be in development stages on a product that needs to be out in the consumer's hands today. That's why we moved on to something like this where we can actually get things out there quicker.

      How was the initial setup?

      The setup is very straightforward.

      What's my experience with pricing, setup cost, and licensing?

      I have no input as far as the cost is concerned. That goes further up the chain than me.

      What other advice do I have?

      I would definitely say it's a very good solution to have for a company, yes.

      Disclosure: IT Central Station 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.
      it_user355629
      Director Corporate Systems and Emerging Business at a insurance company with 1,001-5,000 employees
      Vendor
      JIRA can do incident management, work configuration, and a lot of other different things. But we haven't found anything as compelling as CA Agile.

      How has it helped my organization?

      The tools are not overly complex for Agile. It appears that CA has recognized that. They're not just building the connector for Rally, but they are also allowing other groups to build connectors from JIRA into CA PPM and from other tools to CA PPM.

      If you are looking at open source products, why isn't somebody building an open source product so that it could actually do this interface? I build open source interfaces that allow me to get to use different products.

      In terms of the APIs, you have consulting companies that are building other products that you buy and you pay for maintenance

      In the open source community, they are attempting to tie the old to the new, or they are just looking at the new. In the open source community, there's a lot of need for tying the old to the new. (The old refers to CA PPM.)That's the old way to do project management, which involves governing and controlling.

      The new way is Agile. While you still have to do some governance and control, Agile allows you to get away with a lot of things that CA PPM doesn't allow you to get away with.

      There is a need to connect these two elements. What I'm seeing in the open source community is more of a focus on the new products.

      There is a lot old stuff out here that has to be connected to the new. You can't just ignore it.

      The Agile release management is ready to go. When I take this function and try to run it as a discreet element, the other function of the system is rendered as a separate sprint.

      All the other vendors wrap around this core. They interface with SharePoint and Clarity. They will also interface JIRA to Clarity. It is a methodology. It is basically taking the Agile methodology, doing some things, and not redefining the whole process. It is, rather, adding some additional components to it, so you can understand what you can do with it, and what cannot be done with it.

      What is most valuable?

      PPM: Has administrative overhead associated with the waterfall approach and a lot of DTL tracking.

      JIRA: The scrum masters have a lot of flexibility in the sprints in terms of how they actually track work. In financial organizations, or in organizations that are regulated, you need to be able to have that governance component that PPM provides. You also need to provide the flexibility, which is what JIRA or Rally provides. JIRA has been around for a long time. It is open source, so a lot of people have moved to JIRA. It is a suite of products and not just one piece. It is not just about Agile development. It can also do incident management, work configuration, and a lot of other different things.

      We have adopted JIRA, as well as Rational. Connecting both PPMs is important, because you still need the governance.

      However, we haven't found anything as compelling as Rally. If we didn't have JIRA, and we didn't have other tools, Rally would probably be a strong consideration. However, we already have teams that are familiar with the other tools.

      You have intake and change management, which is part of PPM, but you can also tie into it. You have release management and testing.

      What needs improvement?

      It would really be interesting to see an open source community that actually focused on how we build the connectors from the old to the new, and then make that transition possible.  Once you build those connectors, you transition the old into open source, so the old goes away.

      I was just looking at a small company and their release management. It felt like it was very close to this, but it's the opposite end of the spectrum. They tie in to CA PPM and they do the development and the project management. 

      They are doing Agile this way, but they have these other components that they have to put in front of it and behind it, to make it tie into release and change management.

      Agile comes at this development piece of work. It's now production ready and I put it on the shelf. Most systems don't allow that. I put it on the shelf. Somebody else develops another piece of work. My piece of work has to come back off the shelf. 

      They interact with one another, so I can't just say this one is ready for production, and then that one is ready for production. I have to go into a system test mode, and not just the function test mode. Agile generally doesn't look at it that way. Agile is really built to run on building services.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user356046
      Commercial Manager at a consultancy with 51-200 employees
      Consultant
      It seems reliable and we are happy with this product.

      What is most valuable?

      It is a very complete solution. It provides a full solution for us, which is extremely essential.

      How has it helped my organization?

      The principal is because they listen and that helps a lot and the business, this is very important to us.

      What needs improvement?

      So far it seems to be doing everything we need it to. We don’t require any improvements at this stage.

      What do I think about the stability of the solution?

      So far it seems reliable and we are happy with this product

      What do I think about the scalability of the solution?

      We are not sure so far on this as we haven’t used it long enough but we hope it will be scalable

      How are customer service and technical support?

      They are smart people, knowledgeable and helpful.

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

      It was time to get a product like this in house, previously we were using a local software and it was time to upgrade. For us it is all about the support of the company, and we really like this from CA, they have been very helpful.

      How was the initial setup?

      It has been a straightforward partnership so far. We are in the initial stages, but all looks good.

      What other advice do I have?

      I think that you should do some research but ultimately go for someone that addresses what you need and who is able to provide great support.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user637830
      Software Engineer at a healthcare company with 10,001+ employees
      Vendor
      It helps us to track and manage the way we work.

      What is most valuable?

      My company uses it for managers, project management, and all the release management team.

      How has it helped my organization?

      It helps us to track and manage the way we work. We follow the Agile method and it really helps us to manage things and divide up tasks. It is quite a good tool.

      What needs improvement?

      I am pretty much happy with the use of the solution. I want to recommend it to other people. The way we work, get the reports, and check on things is very clean. I can customize things from my dashboard. I would like to see better scalability.

      For how long have I used the solution?

      We have used this for almost four years.

      What do I think about the scalability of the solution?

      I guess if it can give more integration, something like Outlook, and more automated instead of manual entries, then scalability would be OK. We have around five thousand people using the tool.

      How are customer service and technical support?

      I guess I am good with the level of technical support.

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

      I didn't use any other solutions. I came to know about this program management solution from working at my company.

      How was the initial setup?

      In terms of the setup, there was one thing that was a little difficult. I got to change it very quickly, and the team was helpful.

      What other advice do I have?

      I would recommend it. It is a very good product, very helpful in managing, and pretty good at checking things. The way we manage our projects and the way we work with it is pretty good.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user637806
      Software Engeneer at a tech vendor with 201-500 employees
      Vendor
      In our orgaization, every team can follow what the other team is doing.

      How has it helped my organization?

      We have many teams that work on different modules and every team can follow what the other team is doing at the moment, so as to take a decision about taking the user story into the sprint or wait, till the dependent team finishes its work. So, it suits distributed and big projects.

      What is most valuable?

      The most valuable features of this product are

      • Creating, updating and deleting (CRUD) operations.
      • Search for the user stories, defects and test cases (I simple search by the ID and do not often use the Advanced Search option).

      These functions are valuable for me, because I do use them every working day.

      What needs improvement?

      Probably, the user story history details could include the candidate. Now, it is ugly looking and is not informative. I would prefer to use it to restore details.

      What do I think about the stability of the solution?

      I did experience stability issues. 

      Sometimes, it has short hanging periods during a planning session, i.e., when you discuss the user story, without the screen displaying the acceptance criteria, mockups and so on.

      What do I think about the scalability of the solution?

      As usual, there were some scalability issues. If you have many items on the screen, it becomes a bit slow.

      How was the initial setup?

      Sometimes, the UI is not intuitively understandable.

      What other advice do I have?

      Make it user-friendly. 

      Probably, you can add some UI templates such as a combination of filters/functions, etc.

      Disclosure: IT Central Station 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.
      it_user635454
      Sr. Technical Analyst at a leisure / travel company with 10,001+ employees
      Vendor
      As an administrator, the most important tool is looking up the subscriptions of my customers to see if they had logged in recently.

      How has it helped my organization?

      It helps us organize our projects so that we can get down to really detailed work items; really granular, busting up a task, a feature, and parsing it out so that we really understand what's needed. We can put it into small, bite-sized pieces that can be addressed quickly. If somehow there's a misunderstanding or miscommunication, it can be adjusted and corrected fast and easy.

      What is most valuable?

      I'm the subscription administrator. I rarely use it as a user. I generally only use it as a user to troubleshoot. So to me, as an administrator, the most important tool is looking up the subscriptions of my customers to see if they had logged in recently.

      What needs improvement?

      To me, the biggest thing I see that needs improvement is the navigation. When somebody's using more than one workspace, it's not obvious how to go from one workspace to another. It's simple enough once you know, but is you're looking at the screen, you don't notice it.

      I actually have to write documentation, and I sent it out often to tell people how to navigate from one workspace to another when they're on more than one workspace; in a sense, more than one project, though a workspace is a bigger bite of a project. If you're really just on a different project, and they're all on the same workspace, it’s not a big deal. But when they have to switch from workspace to workspace, it's not obvious. So, that's where I see they could improve in their navigation. Make it more intuitive.

      What do I think about the stability of the solution?

      For the most part, stability has been good. They did go through a small shaky patch when CA bought them (Rally) and they decided to move data centers. It seemed like there were some outages, but that has been fine since. It can be a little slow at times, but as far as up time, it seems to be quite good.

      What do I think about the scalability of the solution?

      I don't know about scalability. From my understanding, we're medium to small in the grand scheme of things. There are much bigger shops than us. But we're not small either. We're in the hundreds. So, it seems like there's plenty of scalability.

      How are customer service and technical support?

      I have to say, since CA bought it, support has actually improved; which I'm very surprised about. I found in the past, when it was wholly owned by Rally, they forced you to always go through their website first, search their knowledge base, and then post a case. And then they'd contact you within a day or so. It was okay, but it was less satisfying when that's the only way to contact them; and I always had to go that way.

      The technical support seems to have improved quite a bit since CA bought them, which, again, I was very surprised that it has improved instead of get worse. It seemed to be able to handle phone calls better and are even more responsive. I'm very happy.

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

      I wasn't part of the discussion to buy initially. It was already here when I started. It seems that we have grown, though, and switched from other tools. It just seems like the granularity it provides and being able to really be good for development teams and really focus on their needs, and that is why we use it so much and it's growing.

      How was the initial setup?

      Setup seems relatively straightforward. It was easy to learn. Most teams teach themselves how to use the tool and new teams generally hire somebody who understands the concepts, so just a cursory show them the fields and the setup, and they're good to go. There's nice three- to five-minute videos that CA provides from their website that helps teams understand the concepts and the usage.

      What other advice do I have?

      Just be open and take advantage of the videos to see if they understand what the product is and to reach out to the vendor and ask them questions. They seem very willing to help without necessarily charging. If they feel that you're a potential customer, they're happy to talk to you and give you some guidance. If you need a lot of help, then of course, then they have programs to actually send experts.

      Disclosure: IT Central Station 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.
      it_user638709
      Product Owner at a healthcare company with 10,001+ employees
      Real User
      The BQ score lets us evaluate whether a team has understood the requirements completely or not.

      How has it helped my organization?

      The velocity of work that we were doing prior to using CA Agile Central, was not quantitative, i.e., we were not able to quantify how many user story points we had delivered or how much work, we were doing.

      By using the CA Agile Central tool organization-wide, it gives us a clear picture of how many user stories we can pick and the capacity of the entire team. It is a very good tool; we can see the capacity and the entire velocity of the team. So, this is how it has improved our deliverables. Earlier, we used to deliver in around an 8-week sprint. Now, since our company is using it for about two to three years, the team has matured on the process. They have really improved deliverables and reduced it to a 5-week sprint, that we are giving to the clients.

      What is most valuable?

      One of the features that I like is the discussion thread, that we can subscribe to, if at all, someone wants to discuss something. It has to be in that particular feature or the user story itself, rather than in an email. Thus, one can subscribe to know whatever discussion is taking place. So, you can get an email regarding what is new and what has been added to that discussion, which is a great feature.

      Another feature that is valuable, since I have used JIRA as well, is in regards to the BQ score, that we are giving after having the grooming sessions. This gives us an important way to evaluate whether a team has understood the requirement completely or not. So, the scaling part as to how the team is doing, is really a good feature.

      I can be assured in terms of the rating. Initially, I got a 3 star rating, as my teammates were not clear with most of the things. However, when I gave them some clarification and they are good with it, then they changed the rating to around 4 or 5. This gives me confidence to do a release plan, as my team is very confident and have given me a higher rating. This is a great thing.

      What needs improvement?

      The product is really good and there is very little space, as to what needs to improve.

      The only thing that I can think of is to improve the section of the acceptance criteria, that is located far below the user story description. Sometimes, what happens is that people who are looking at the user story are not looking at the acceptance criteria, because they need to scroll down to look at it. It would be better to display it on the top, where you can see the user story, without having to scroll down; perhaps, by having another screen where you can see the acceptance criteria field.

      For example, from what I have seen often is that, instead of our developers going to the acceptance criteria field after the user story, instead they come to me and ask me where it is. That means, they haven't gone through the entire user story until the bottom of the page. The practice that I have asked them to follow is to read the notes right at the bottom of the user story, so as to access the acceptance criteria field. So, if one is looking at the laptop screen, then there should be a button aligned somewhere on the topmost part, that will immediately prompt as to where the acceptance criteria field is located, i.e., somewhere within the description box itself. So, no one will have to scroll up or down to look for it. This is the only thing that I found that needs improvement; rest of the stuff is great.

      What do I think about the stability of the solution?

      We have experienced some crashing instances.

      Sometimes, I enter my password; however, then something gets downloaded on my desktop and it asks me to put my password in again for the CA Agile Central tool. Within a two-year framework, this has caused me to log in and change my CA Agile Central password around three to four times. It doesn't give me any notification that the product is down or undergoing maintenance. There are some caution notes displayed as well, such as "This is scheduled maintenance time and CA Agile won't be available currently". However, there have been various instances where people are not getting any notifications as such, and they are being logged out off their accounts.

      Sometimes, there are minor stability issues, such as when inserting your password and getting a message that you have to insert it again. We have had some instances where the users are logged out of their accounts.

      We have two workspaces and while switching from workspace 1 to workspace 2, recently, we have seen some of the records getting lost, i.e., it was either in the recycle bin or orphaned. This has been noticed for the first time, while migrating workspaces.

      Most of the times, to get a report, we are going to user stories and grabbing the columns into one particular view, which we then export to Excel. From there, we get a pivot table, so as to extract the exact data that we need. For example, sometimes, we need to perform a matrix analysis, in order to know how many defects have been encountered in a particular release. In this case, we cannot simply make a comparison matrix chart and but if we need to search it by a particular criteria, we can do that. However, if we want to do a graphical representation/chart of the data, then it will not show that.

      I wrote a user story before my PA planning; after my PA planning, 2 got deleted and 3 got added. We want to know from the previous user stories as to how many got deleted or were newly added, in a graphical chart. This is something from the matrix side.

      Thus, matrix is an area if CA can improve it, i.e., without having to export data from Excel, we will be able to get the information easily.

      What do I think about the scalability of the solution?

      Although, it is a manual task, we can get the data easily in a table format. Since it is a manual process, it is not straightforward. However, we do have a large number of users, who are doing this kind of matrix analysis. We have around 52 to 55 product owners, who are managing up to three scrum teams each. Thus, you can take an average of around two scrum teams. At the end of every release/sprint, we are pulling up this data matrix, to know what has happened exactly during this particular release, i.e., where we were good or not. There are charts, where we can do burnup/burndown and have all those variations between accepting the user stories, until the time it is completed.

      We need some similar type of matrix for other criteria as well, such as how many defects are there or the BQ scores that have been given to the user stories. For example, if my release plan comprises 30 user stories, then how can I identify out of my release plan, how many user stories are not created well, due to issues such as the requirements were not clear enough or they were too big or did they have architectural insignificance or not. Thus, if we get this type of matrix, then we have the justification for it. However, if we have to pull out the data manually and if, we haven't grabbed the correct parameters, then we can miss out on some of the criteria, for this 30-point user story. We won't be able to pinpoint exactly as to why the release plan has not been carried out correctly.

      How are customer service and technical support?

      I would rate the technical support at around 9/10. They were very aggressive in terms of looking at the issue and providing the correct guidance. So, I appreciate them.

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

      In my current company, from the very beginning, they have been using the CA Agile Central solution.

      At my previous company, I was using Microsoft Team Foundation Server (TFS) for similar purposes. It was not too friendly. For example, if you are in their UI, there is a big chance that you are going to get lost somewhere and you won't know how to come back to the point where you started. This wasn't very good. Probably, they are not matured yet.

      Since I started using CA Agile Central, I found it to be very good in those terms. We have feature descriptions, detailed user stories, attachments, discussions and we can even see the revisions. So, having those features in different tabs gives us a kind of flexibility to look at what is going on and who did what to change it. They could add a tag to see if the user story is of architectural significance or UX significance.

      This tool is most productive in my day-to-day job.

      How was the initial setup?

      The setup is not very complex. As soon as you log in, the dashboard we see is really cool. One would really like to see the graphs and charts. So, that is very nice.

      What other advice do I have?

      There are many tools in the market out there. I have worked both with JIRA and Microsoft TFS, so it can be seen clearly that the CA Agile Central tool is entirely developed. There is a timebox and a sprint-based UI, as well, in it; it is very easy.

      When I used TFS, it was very clumsy and you can't see yourself, returning to the very first point. But, here you have everything; it is very flexible, very simple and decent. You can start anywhere and can return to the very same point, again at the end.

      I would suggest for most of the product development companies, if they want to have tracking of their user stories, then use a very simple tool like the CA Agile Central solution. It gives you a number a functionalities, along with a very decent UI. The UI is not very fancy, but it is going to give you a very nice picture of the status, as to what is going on with the features and user stories. So, my recommendation would be to go with the CA Agile solution. It is a very good tool.

      Disclosure: IT Central Station 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.
      it_user647424
      IT Business Systems Analyst at a manufacturing company with 10,001+ employees
      Vendor
      It enables us to document our epics and features and user stories to a fine level.

      How has it helped my organization?

      I work with our business units and they hand over a project to me. Then, I break it down and dissect it at the project level and break out all the features. Then, for each one of the features, I write all the user stories. Then, I coordinate with my software development team to get the work done for all of the user stories.

      We take it through the entire process from the conceptual stage to the business of getting the work done and showing the business that we got it done.

      What is most valuable?

      I guess the main thing is that it allows us to pull all of our user stories and manage our agile process together for our agile team.

      It enables us to document our epics and features and user stories all the way down to a fine level.

      What needs improvement?

      I'd say that there are a few things to improve.

      On the main screen, I think it's called the Team Planning screen, it should be able to run a backlog. For example, if I have 300 stories in my backlog, it would be nice to be able to filter those out by project because that's the main place that I look at them and my team looks at them, and you get 300 stories out there for numerous projects for our team, because we work on 85 different applications. There are five or six primary ones, but the rest are back-end components.

      We've got some technical stories for back-end stuff and we've got some continuous improvement items for our assisting applications. Within that backlog, to be able to have some type of filtering mechanism so that if I want to see all of the stories for a certain project, I can pull them out and view them, would be useful.

      Right now, I have to scroll down through 300 stories and try to group them all together and find them and then, by the time I go and group them together, somebody's going to ask me to group them another way. Then somebody's going to say, "All right, well, can we prioritize them in that backlog?" Well we can, but then I've got to change all my groupings.

      All this takes time. Basically, what I end up doing is just pulling those out, either copying, pasting or exporting them into a spreadsheet and then I'm back to managing them on a spreadsheet rather than in the tool and it's just time consuming.

      There are certain things that I think I would like to add that would make my job or my function easier. One example is that they have different levels of access within the system and I do not have the highest access, so there are certain things that I can't do. There are other people within our organization that can modify the system or make certain changes, but I can't.

      Also, for each one of the user stories, you can throw different tags on them so you can do searches or filters by those tags. Everybody can add a tag, and you can create new ones, but I'd like the ability to go in and modify and clean up those tags.
      I've asked to get that access and they said I don't have the right level of security so then, it's a matter of working with somebody back and forth to try to get everything cleaned up.

      For example, we have an internal system that we do a lot of work on. It's called Service Desktop. Well, there are about 10 different tags out there for Service Desktop; one of them is "Service Desktop", another one is "SD", another is "SERV D", etc.

      Because we have multiple people working on this and they've created their own tags for their own stories on different things but they all mean the same thing, so, to me, it makes sense to have only one so that everybody is on the same page with that same one.

      I would like to get it all cleaned up, so that when I do some sorting or filtering or running different reports and I'm basing it on a tag, I want to make sure that I've got everything and I don't even know all the different tags that are out there for Service Desktop.

      If I had those abilities to make these changes or create some of the modifications or to build some of the panes and windows that I would like to see, I guess I would probably give the solution a higher rating.

      What do I think about the stability of the solution?

      I have not encountered any stability issues.

      What do I think about the scalability of the solution?

      I have not encountered any scalability issues. We typically pull in 15 to 25 user stories every sprint so maybe 100, 125 stories for a specific PSI, and it has no issues meanwhile.

      How are customer service and technical support?

      I have never called the technical support in over three years.

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

      We switched because in my organization we have multiple teams. I'm just on one team, we probably have another 12 to 15 teams that are working on projects, and this is just one centralized repository across our organization.

      We have multiple sites, so everybody could use the same thing to put their work efforts into rather than individual spreadsheets where nobody could get access to them.

      How was the initial setup?

      When we originally got the product, I basically had to take my workload and transfer it into CA Agile Central at the beginning and that took me a few days to get done, but after that, we just built everything right from there.

      Which other solutions did I evaluate?

      At my level, I didn't do the evaluating. One of our staff within the organization did. I had no idea if they looked at other options or not but I think they chose CA Agile Central because of the versatility and the ability to handle multiple teams in multiple locations. It seemed to work out to help all of us transform to the agile methodology.

      What other advice do I have?

      Have a good plan, an overall plan, of the goals that you're trying to achieve. For those organizations that are going into CA Agile Central or going into agile or if you're currently doing agile, then do the following.

      1. Go through a process of learning the system or having a handful of people learn the system so that they know it well.
      2. Get the system customized because that's one of the strong aspects of CA Agile Central. We have a couple of CA experts within our organization and they connect directly with the folks at CA and make changes from time to time within the system.
      3. Get all of your modifications and everything done up front and then start inputting the details and all of your teams and individuals and work efforts.
      4. Just start using it!

      To me, it was very simple. A very simple type of tool to use.

      Disclosure: IT Central Station 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.
      it_user638703
      QA Manager at a tech company with 10,001+ employees
      Real User
      By tracking all of the user stories, I can know how much work is completed or is still pending in the backlog.

      How has it helped my organization?

      I am from the QA team and am using this especially for test automation. We have so many test scripts and this would take some time. Earlier, we used to have a different tracking system, but the difference is that, if there are any new changes, then it was very hard for us to get them into the system. However, with the CA Agile tool, we were able to have two-week scrums and two-week sprints. After each sprint, we were able to pull any new tricks that came up and we could easily prioritize, prior to the two-week period, instead of having to wait for a long time. We were able to easily create and track the user stories. We were able to understand the graph as to how the trend is going, so all this was really helpful.

      What is most valuable?

      I find that tracking of all the user stories feature is extremely beneficial, because I can know in terms of the user stories, how much work is completed and how much is still pending in the backlog.

      What needs improvement?

      During the last four years, there were four projects in there, that I was handling. However, one of the issues that I am facing is how to remove the old projects, as one of the projects is over. Although, CA Agile is still showing me all of those four projects and I don't want that information now. So, there should be a way to remove that project.

      I am not sure whether CA has their own bug tracking tools. However, if there are some tools like that, then it will be very much helpful, i.e., to have one integrated system, where the configuration management as well as this bug tracking tool are integrated. Bug tracking we have with NetApp's internal tools, but I don't think we are able to do the integration between CA Agile Central and what we have.

      So, it would be good to have one single complete solution for complete development, such as for tracking agile work, the bug tracking tool, and Perforce management, the version control system. Thus, an integrated system would be very much useful, I think.

      I am not sure if CA has the integration tool part, currently or not; however, I am unaware of that. Hence for me, the integration between other tools will be a very useful add-on feature. In the market, there are other tools that are available as a complete solution, providing tracking tools, bug tracking features and necessary support as a package. If CA Agile Central could also provide that kind of integration such as the bug tracking, a version control control system as a single solution, then it will be very much helpful.

      What do I think about the stability of the solution?

      Sometimes, we have noticed that our CA admin sends out an email, maybe that could be in regards to the maintenance work that is internal to the NetApp.

      What do I think about the scalability of the solution?

      There weren't any scalability issues. For my work, it is perfectly suitable as of now, so I don't see any scalability related issues, for my work as of now.

      How are customer service and technical support?

      If we experience any issues, then we have the NetApp internal support and will basically reach out to them. Thus, we don't directly contact CA Agile Center support, as we have enough people internally to get NetApp support. I would give them a 8/10 rating.

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

      Initially, I was using Microsoft Project. Since it was not compatible with the agile environment and we then started using the agile methodology in our project, we started using this solution. Also, NetApp is providing support for this tool.

      How was the initial setup?

      The setup was simple but I also remember that the one thing that is missing in CA Agile Central is the integration of data, as when you compare it with Atlassian JIRA or similar tools.

      Which other solutions did I evaluate?

      I did not evaluate other options because my company is providing the tool. I believe that before choosing it, my company may have done some kind of comparison with other tools, and then selected this one.

      More than a team or a manager decision, this was a company-wide decision.

      What other advice do I have?

      This is a very helpful solution, especially for those who are planning to switch over to the agile environment. Although I have not evaluated any other tools, I do have experience with other tools as well, but I have never compared both of them.

      This is a great solution, especially in terms of the graphs and how the trend is going on. That is the one of the main features, which is helping me a lot. During a two-week sprint, if I look into it, I can exactly know where the trend is going or whether all the work is getting completed or not. Thus, it provides a good forecast as to how much of your work is getting done or is still pending. This is a good positive aspect to suggest to others.

      Disclosure: IT Central Station 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.
      it_user637815
      Quality Assurance Manager at a financial services firm with 10,001+ employees
      Vendor
      The portfolio items, the quality module, and the reporting are probably my top three features.

      What is most valuable?

      I don't know which feature would be more specifically valuable. I guess the portfolio items would be the ones I use the most, but I also am very familiar with the quality module as well.

      Some of the reporting stuff would probably rank right up there as well. Those are probably my top three.

      How has it helped my organization?

      I think what it's helped with in general is that we've learned a lot about how to break things down a little more in detail. Going from primarily a waterfall organization into an agile organization, the tool has been very helpful to help people make that transition.

      It's a relatively slow process, unfortunately, as it's a large organization we're dealing with, and everybody interprets things a little bit differently. We've had some people that have really spent a lot of time with the CA resources, who really understand the product and help the users use the tool effectively.

      What needs improvement?

      I think one of the things that we stumble upon is how to organize the teams. We have one overall workspace, but outside of that workspace we have many, many teams underneath it. I think you can organize them in two different directions. You can organize them by leadership or organizations, or you can organize them by, for lack a better term, product. And those two don't sync together, because you have many organizations contributing to a product that don't roll up to the same leadership level.

      So from a reporting aspect, for different things, we struggle trying to get that balance; to get the reporting for the leadership side, and then get reporting for the product side. That is one aspect. It's not necessarily a hierarchical issue, it's a flexibility issue, if you ask me. If you put it in one direction, you can't get it to the other. So you need to be able to balance it both ways. That would be something I think that could be worked on.

      For how long have I used the solution?

      I have been using the solution for more than three years.

      What do I think about the stability of the solution?

      I personally haven't had any stability issues. The only time that it's been a problem for me is when I've extracted data around test and defect information. The extraction process has to be broken up; you can't do it all at one time. It's not impossible; it's just a little more work. Whether it's just because of the amount of volume we're talking about, or if it's just that there would be no way to fix that, I don't know.

      Specifically, in our case, we're getting very close to the millionth test case written in the 3+ years that we've been doing this, and that's a lot of data. But you can't extract it all at one time; you have to break it up into chunks.

      What do I think about the scalability of the solution?

      I personally have not encountered any scalability issues.

      How are customer service and technical support?

      I would rate the technical support at 9/10. That's a very, very strong nine. We work very closely with some of the technical support people, and have for a very long time, and they are great partners.

      I think what they do today, especially with their tech support side and the relationship we have with them, they are very open, they listen, and we understand that we're not the only client. We know what our users come to us and ask for. We take that information in and compile it, and have conversations with CA Agile Central, saying, "Here's what we've come across," and they've actually been very responsive to some of the things that we propose.

      We know we can't get it all, because they have to make the tool useful to all their clients. So we'll present what we think is viable, and it's just like anything else. Some of it makes it, some of it doesn't. I really can't ask for anything more than what they do. They're very open, they will listen, and they will do it if they can. That's fine by me.

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

      This was the first Agile Central tool that we used on a grander scale. Again, we switched from a waterfall organization to an agile organization, and this tool doesn't support waterfall.

      How was the initial setup?

      I wasn't involved in the setup process.

      What's my experience with pricing, setup cost, and licensing?

      I am not involved in the pricing and licensing side of the operation.

      Which other solutions did I evaluate?

      I wasn't involved in any such evaluation.

      What other advice do I have?

      I have had some experience with one of the other tools out there and personally, I like this one better, so I'm a little bit biased around that aspect. If somebody were to ask me, "I'm looking between this and that ...", if I know the tool, I would have my biases towards CA Agile Central, for sure. I think it's a pretty good tool.

      Disclosure: IT Central Station 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.
      it_user635421
      Senior Analyst, Business Process Design at a comms service provider with 10,001+ employees
      Vendor
      The ability to customize and change the processes, so as to respond to changes in the organization, was helpful.

      How has it helped my organization?

      Previously, we had an in-house solution that was very difficult to update and customize. Thus, when we had acquired new businesses that we were working with, we weren't able to add the right type of information that we needed or get the right type of support and customers. We weren't recording half of all our new work that was coming in through my team because we couldn't do it. So, when we started using CA Agile Central, those changes could be made in a day or two and we had better data integrity, than my team had ever had before.

      What is most valuable?

      Since we went through a series of work changes in the last two years, the most valuable feature is how easy it is to customize it. The ability to customize and change the processes really quickly, so as to respond to what the changes of the organization and processes, were the most helpful.

      What needs improvement?

      It takes a very long time to load and, if you make some small changes, then the whole page has to reload. I know that's a major frustration for a lot of people using the tool.

      I know that they're constantly updating and providing new features. As I have mentioned elsewhere, I set it up for two different teams. By using it in it's most standard and straightforward route, it is definitely a ten out of ten. However, working at the portfolio feature level, which is what my main team did, there were some functionalities that were missing and over the last two years, I've seen more and more of it come along the way. I would have liked to have the same development support at the portfolio feature level as well, that I was seeing at the user story level.

      What do I think about the stability of the solution?

      We are facing some stability issues. This is a pretty regular occurrence, especially when using custom reports.

      What do I think about the scalability of the solution?

      I've not necessarily put the scalability factor to test yet, but the nice thing is once you have a small handful of people using it, the number of people and information in it has tripled over the last couple of years. So, it was scalable for us in that sense and then, also in terms of the number and diversity of customers, as I mentioned. It's been good in the sense, that we've needed it but I don't think we've really put it to the test.

      How are customer service and technical support?

      I had a question when looking into custom scrums and I think, the overall community for CA Agile Central is incredible. Not only does our organization have people here, but there's a wealth of information online as well. When we reached out for technical support via the CA Agile Central team at our organization, when we had some particular requests, they were absolutely incredible. We really liked the tool because it's really easy to learn and there's a really good community.

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

      As I have mentioned eslewhere, we had an in-house solution and before that, it was all managed via Excel spreadsheets. Excel was the worst of it all. The in-house solution was only good enough maybe for the first couple of months, until one or two or more changes came along, that we couldn't afford to keep up with. That's definitely one of the main reasons as to why we switched, since we couldn't keep up with the updates. If we say that CA Agile has stability issues, that again are not poor, but it just takes a while to load, then, our in-house tool was significantly worse.

      How was the initial setup?

      I thought that the setup was very straightforward, but we also had people on the side of our organization, i.e., a dedicated team, to help get everything set up smoothly. My team intended to change a few things about how you would traditionally use the product. I set it up for two different teams. When I used everything in the straightforward way, it was very easy. When we were modifying and customizing some things for my team, then it got a bit more complicated; just to get my head around the rules and then, having to manipulate them. So, the setup is very easy when the product is being used as it's meant to. When we were manipulating things, it got a little more complex. However, we were able to work through it relatively easily, because of the support that we had.

      Which other solutions did I evaluate?

      I evaluated about half a dozen of the other vendors out there and one of them was JIRA, for portfolio management. JIRA was the other top competitor, although we did evaluate other small vendors as well. CA Agile Central was much better. We actually had a relationship on JIRA's side, but I was the first one to venture into the CA side, as we didn't have the relationship in my team. However, CA Agile was just a far more superior product, as compared to what JIRA was able to offer then.

      What other advice do I have?

      It is important to truly understand it! In order to use it the best way that you can, you really have to understand your process, terminology and the way that CA Agile Central is meant to be used. We had a lot of issues with the terminology; for example, at what level should we be, does this count as a user story, does this count as a feature, etc. So, it is crucial to really do all that work in the beginning and to map out everything meticulously, so as to make sure that the definitions are clear. After that, setting up of the process becomes much easier; but, if there's a lot of back-and-forth in terms of the definition, the setup and adoption will be much more difficult.

      Disclosure: IT Central Station 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.
      it_user642177
      Software Developer at a manufacturing company with 10,001+ employees
      Vendor
      Provides storage and accessibility to share documents and objects.

      How has it helped my organization?

      This product provides easy storage and accessibility to share documents and objects.

      What is most valuable?

      Personalization of the dashboard and its design are the most valuable features of this solution.

      What do I think about the stability of the solution?

      There were no stability issues.

      What do I think about the scalability of the solution?

      Sometimes it takes a few seconds to scale, such as when changing the size of Windows.

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

      This tool was already present before I started working here.

      How was the initial setup?

      The setup was easy.

      What other advice do I have?

      It takes time to configure and clear the dashboard to make it useful.

      How has it helped my organization?

      This product provides easy storage and accessibility to share documents and objects.

      What is most valuable?

      Personalization of the dashboard and its design are the most valuable features of this solution.

      What do I think about the stability of the solution?

      There were no stability issues.

      What do I think about the scalability of the solution?

      Sometimes it takes a few seconds to scale, such as when changing the size of Windows.

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

      This tool was already present before I started working here.

      How was the initial setup?

      The setup was easy.

      What other advice do I have?

      It takes time to configure and clear the dashboard to make it useful.

      Disclosure: IT Central Station 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.
      it_user637812
      Technology Business Mgmt. at a transportation company with 1,001-5,000 employees
      Vendor
      Some of the valuable features are configurable portfolio management and object classification.

      Pros and Cons

      • "The configurable Portfolio Management and parent-child relationships."
      • "The Reporting feature can improve, especially around executive summaries and dependency mapping."

      What is most valuable?

      • The ease of user provisioning, i.e., bulk provisioning via API
      • The configurable Portfolio Management and parent-child relationships
      • The object classification (tags/colors)
      • The seamless integration with many other systems such as Salesforce and GitHub
      • Consistent uptime
      • Rapid response support

      How has it helped my organization?

      Team collaboration is made easy and effective to meet business initiatives, while tracking progress across all the solution groups, regardless of their geographical location.

      What needs improvement?

      • The Reporting feature can improve, especially around executive summaries and dependency mapping.
      • One report that would be especially useful is a Release Dependency report that displays the relationship of dependencies, across release trains. Currently, Agile Central will show you respective dependencies, but only if they exist within the same release train.
      • CA Agile is hosted on a multi-tenant server, which prevents duplicate user names to coincide. This has become bit of an issue, in terms of provisioning users that had demo accounts in the past. In our experience, when provisioning a user who held a demo account with their company's email address, we had to reach out to the user to have them rename their old demo account. This opens the door for us to then proceed with the account creation.

      For how long have I used the solution?

      I have used this solution for four years.

      What do I think about the stability of the solution?

      CA Agile Central is very reliable, in terms of consistent uptime. We have, however, encountered site latency during peak times of activity (far and few).

      What do I think about the scalability of the solution?

      There were no scalability issues experienced by us, to date. We had a user base of 500 in 2015, and will have 3,000 by the end of 2017. We have not encountered any noticeable limitations.

      How are customer service and technical support?

      The support staff at CA is excellent! They are very responsive and work to resolve any requests or issues, within a time span of a day on the average.

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

      Previously, we were using VersionOne. CA Agile offers a more structured model of Portfolio Management.

      VersionOne tends to offer a more open and free configuration setup, in terms of creating portfolio items. For example, in VersionOne, you can create child features, and then produce another set of child features for each parent feature. It is nearly impossible to restrict a portfolio model that allows for consistent reporting.

      In Agile Central, you can configure and define your portfolio structure in the administrative console. Each child must roll-up to its assigned parent, i.e., Task > User story > Feature > Epic > Initiative (bottom-up).

      How was the initial setup?

      The initial setup of Agile Central was straightforward and very repeatable. If you get it right once, the process to scale your subscription is consistent and efficient.

      What's my experience with pricing, setup cost, and licensing?

      The license costs are fairly high as compared to some of the other solutions out there. CA Agile Central licenses are “one shoe fits all”, i.e., in terms that a Viewer license is the same price as an Editor or Project Administrator license.

      A tiered pricing model would be a better approach. For example, the cost of the Viewer's license would be less ($) as compared to the cost of the Editor's license ($$).

      What other advice do I have?

      CA Agile Central has worked very well in our ever-growing, agile-centric organization. If you’re looking to implement an agile development solution that scales extremely well and is backed by solid performance, stability, and an outstanding support team, this is the solution for you!

      We recently went through a rigorous analysis across ALM tools in an effort to justify the continued use of the Agile Central, in comparison to the alternative solutions. CA Agile Central was chosen hands down, as our one and only ALM development tool across our enterprise!

      Disclosure: IT Central Station 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.
      it_user635460
      Process Transformation Manager at a financial services firm with 10,001+ employees
      Vendor
      We are using this solution for IT project management in our organization.

      What is most valuable?

      It is the only solution that we are using now for all of the project management activities in our organization.

      How has it helped my organization?

      This tool is basically used for our IT project management in our organization.

      What needs improvement?

      In regards to the customization part, sometimes it is not understandable. Things are not so clear, such as how to customize it for our needs. We need to have a lot more user-friendly options.

      Most of the things are associated with the user-friendly options. Currently, the reporting and matrix connections are a little bit sketchy.

      There should also be a lot of customization opportunities, especially being able to add additional filters for the project management. If those things improved, it would make this tool more beneficial for us.

      For how long have I used the solution?

      In my current organization, I have been using this solution for three years.

      What do I think about the stability of the solution?

      We did not encounter any issues. The stability is good.

      What do I think about the scalability of the solution?

      In terms of the scalability, not many issues were experienced.

      How are customer service and technical support?

      I've never used technical support. Most of the things are always working all of the time.

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

      Before CA Agile, we were using HPE Application Lifecycle Management (ALM) and HPE Quality Center software.

      HPE was mostly for waterfall and this CA solution was more for agile. That is the reason why we switched to the CA tool.

      For the ALM tool, they are still implementing the agile part, so the full functionality was not available on ALM's side.

      How was the initial setup?

      The setup was complex. We have a very big connection, extremely big. Everything is complex.

      Which other solutions did I evaluate?

      I was not involved in any evaluation process because we are an organization level division. We have nearly 20,000 developers in the IT support team and most of them use this tool. This tool's implementation in the enterprise was from the senior management level.

      Disclosure: IT Central Station 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.
      it_user639684
      Front End Manager at a transportation company with 10,001+ employees
      Vendor
      Some of the valuable features are creating a new iteration and adding new user stories.

      What is most valuable?

      It is easier to:

      • Create a new iteration
      • Add new user stories
      • Copy from the old user stories
      • Add tasks
      • Search for user stories

      How has it helped my organization?

      The agile methodology has made it easy for all disciplines of software development such as the developer, QA, software architect (SA), and the product owner. Thus, anybody can open up CA Agile Central and find out what they need. That has improved our productivity. It is easy to use this tool.

      What needs improvement?

      When you open up a user story, consider opening it up as a modal/dialog box on the top of the page, rather than splitting up the screen. In my opinion, if it opens up by splitting up the screen, then it becomes hard to read.

      For how long have I used the solution?

      I have been using this solution for about a year.

      What do I think about the stability of the solution?

      There were no stability issues.

      What do I think about the scalability of the solution?

      There were no scalability issues.

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

      In my previous company, I used JIRA. In my current company, I am using CA Agile Central. I found CA Agile Central to be more user-friendly.

      How was the initial setup?

      The setup was quite straightforward.

      What other advice do I have?

      Please go ahead and try it out. It is a good product.

      Disclosure: IT Central Station 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.
      it_user638706
      System Validation Engineer at a tech company with 10,001+ employees
      Vendor
      The dashboard and planning board are the most valuable features.

      What is most valuable?

      The dashboard and planning board are the most valuable features. These help me track the progress of my user stories.

      How has it helped my organization?

      I can review my pending tasks daily. In this manner, I can organize my day-to-day work.

      What needs improvement?

      In terms of the loading speed, sometimes I have noticed that the website takes a long time to go over to the Planning Board for the user stories. However, this could be a network issue.

      When creating a task, sometimes the Description field is left empty, either because the user is missing or it is a mistake. However, there is nothing in the tool that makes us aware about this missing field. The tool should post some kind of warning message indicating that the Description field is empty.

      For how long have I used the solution?

      I have been using this product for approximately 30 weeks.

      What do I think about the stability of the solution?

      There were no stability issues.

      What do I think about the scalability of the solution?

      There were no scalability issues.

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

      It is the first agile tool that I have used.

      How was the initial setup?

      The initial setup was easy to carry out.

      What's my experience with pricing, setup cost, and licensing?

      The pricing policy is transparent for me.

      What other advice do I have?

      There is a need for some training, but overall, it is easy to use this solution.

      Disclosure: IT Central Station 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.
      it_user635475
      DCDP in Indian dept at a hospitality company with 10,001+ employees
      Vendor
      We can filter the defects and user stories. We use the reporting features.

      What is most valuable?

      The part that I like the most is that we can filter the defects and user stories. We use the reporting features at our own convenience. We use different types of filters and they help us a lot in finding anything we want.

      How has it helped my organization?

      This solution saves us lots of time and it is central for everyone. Everyone can see the revisions whenever anyone has made any sort of change.

      For example, if there are changes in the user story, we can track it. That's very useful for us, because in regards to the test cases, we have all the results available for us.

      What needs improvement?

      One feature that can be improved is the extraction and importing of reports. It should be easier and should be available everywhere.

      For example, we have applied all kinds of filters. If we want to extract that report only, then we should be able to extract that part.

      Also, we have placed a certain number of test cases in the folder and we should also be able to extract that report from there as well.

      For how long have I used the solution?

      I have used this solution for around two years.

      What do I think about the stability of the solution?

      There were no stability issues. It is very rare that we are not able to access the CA Agile solution.

      In around two years, we have only faced this issue one or two times. Otherwise, it is up and working fine.

      What do I think about the scalability of the solution?

      There were no scalability issues.

      How is customer service and technical support?

      In regards to the technical support, they can improve and make the procedure easier. In order to import/export any reports or test cases, we have to create certain queries. They should be more user-friendly.

      How was the initial setup?

      The setup was easy.

      Which other solutions did I evaluate?

      We have compared it with JIRA, the other agile-friendly tool. However, we find this solution better.

      What other advice do I have?

      I would recommend that you use this product for your productivity.

      Disclosure: IT Central Station 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.
      it_user637821
      Sr. Developer at a comms service provider with 10,001+ employees
      Real User
      The most valuable features are logging user stories, listing tasks, and tracking work in progress.

      What is most valuable?

      • Logging user stories
      • Listing tasks
      • Estimating and tracking work in progress (WIP) for each project

      These features are most valuable to me because they are useful for my job functions. I’m a software developer and I use these features more than any other features of this tool.

      How has it helped my organization?

      It helps us to track work in progress for each project and for each user story. We can also learn project details from a high level.

      What needs improvement?

      The search feature may need some improvements. Sometimes it is hard to pull a specific user story just by adding the user story number. It is not straightforward to search for a specific user story using its ID number.

      My suggestion would be to add a search button. In this way, the user could search for a specific user story based on a given user story ID number, or on the user story description.

      I don’t think that I’ve seen this option. Even if it is there already, it is not intuitive to the end user.

      For how long have I used the solution?

      I have used this solution for around two and a half years.

      What do I think about the stability of the solution?

      There were no stability issues. However, I have not used this tool extensively enough to comment on this topic.

      What do I think about the scalability of the solution?

      There were no scalability issues. However, I have not used this tool extensively enough to comment on this topic.

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

      Initially, we were using an internal tool within our company.

      Disclosure: IT Central Station 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.
      it_user639675
      Project Lead at a financial services firm with 501-1,000 employees
      Vendor
      Provides visibility from a high-level portfolio view to individual tasks.

      Pros and Cons

      • "What I like the most about Agile Central is that it is the only system I need to have full control and visibility of our entire body of work plus the activities and processes required to deliver it."
      • "There are few customisation options. For instance, the workflow for story cards cannot be changed out of the box from the standard (Defined, In-Progress, Completed and Accepted)."

      What is most valuable?

      What I like the most about Agile Central is that it is the only system I need to have full control and visibility of our entire body of work plus the activities and processes required to deliver it. This visibility is particularly good from a high-level portfolio view to individual tasks, staff.

      What needs improvement?

      There are few customisation options. For instance, the workflow for story cards cannot be changed out of the box from the standard (Defined, In-Progress, Completed and Accepted). However, this will not be a big problem for most organisations that follow a standard scrum framework.

      The issue is mostly relevant to team using Kanban boards with customised workflows. A very common flow for instance is: To Do - > Analysis -> Development -> Testing -> Completed. So teams wanting to bring that kind of workflow to Rally will not be able to our of the box. And Rally will rightly discourage that kind of workflow.

      And I’ve seen teams doing Scrum that have added additional columns to their workflows such is “Waiting” or “Blocked” and other not having the “Accepted” column.

      Rally of course offers other options to manage blocked stories/tasks so perhaps the “improvement” tag might not be entirely fair. They do offer the functionality so what I was referring to was the ability to customise that functionality to more personal preferences.

      For how long have I used the solution?

      I have used Agile Central for close to one year.

      What do I think about the stability of the solution?

      We have not had any stability issues. The system is web-based and hosted by CA. There is very good communication around system maintenance and upgrades.

      What do I think about the scalability of the solution?

      We haven’t had any issues with scalability. We have increased our user base seamlessly.

      How are customer service and technical support?

      We haven’t really required much technical help as things have worked as expected. The CA Agile Central website provides updates on maintenance schedules or any other unplanned outage. When we have required help on how to use the tool, the CA Agile Central team has been quick to respond with solutions or suggestions.

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

      Team Foundation Server (TFS) was quite suitable for us when we started to use agile as a delivery methodology, but as our maturity increased, the need arose for a more sophisticated tool to give us better visibility and control and CA Agile Central has certainly given us that.

      How was the initial setup?

      Setup was very simple actually. There is some work required upfront to define standards, best practices and governance on how to use the tool but CA Agile Central itself was very straightforward to set up. Everything is web-based and very intuitive. We had a CA Agile Central coach here for a few days and that was enough for us to get started.

      What's my experience with pricing, setup cost, and licensing?

      Licensing depends on a few things. The assessment starts by looking at your portfolio of work, number of projects, resource profiles, etc. Then you need to assess the level of maturity the organisation has around agile. Teams should not be forced to start using agile methodologies if they are not willing and ready, so you might want to start with a small pilot.

      Which other solutions did I evaluate?

      We evaluated JIRA and also looked at the TFS roadmap for future improvements and upcoming features.

      What other advice do I have?

      The most important thing is to have very clear requirements as an organisation. That includes having all the internal processes, governance and ways of working well understood so that the selected tool can be assessed against those requirements with confidence.

      Disclosure: IT Central Station 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.
      it_user636111
      Validation Engineer at a tech company with 10,001+ employees
      Vendor
      The ability to see my team status and find out about roadblocks is valuable.

      What is most valuable?

      Iteration status tracking: The ability to instantly see what my team status is and to quickly find out about roadblocks to existing tasks is very valuable.

      How has it helped my organization?

      It made it much easier to adopt agile methods of execution. The learning curve on using agile is now much more approachable.

      What needs improvement?

      General performance could be improved. The tool is not the fastest or most responsive. Creating stories, saving story changes, updating status; regular transactions are not instantaneous and make the tool feel sluggish. More complex tasks, such as automated reports and aggregate information queries can easily take a few minutes. Improvement could be through backend software optimization.

      What do I think about the stability of the solution?

      We have not had any stability issues.

      What do I think about the scalability of the solution?

      For larger projects, the tool gets significantly slower.

      How are customer service and technical support?

      I have never used technical support.

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

      We previously used manual methods. Switching to this IT-based solution was a welcome change.

      How was the initial setup?

      It was a simple setup! Thanks.

      What's my experience with pricing, setup cost, and licensing?

      I was not involved in the licensing for the company.

      Which other solutions did I evaluate?

      I was not involved in choosing this specific product. It was provided by our company’s IT department.

      What other advice do I have?

      Take the time to go through the Agile Central tool training videos. They are very useful and well worth your time.

      Disclosure: IT Central Station 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.
      it_user636108
      Security Analyst at a transportation company with 10,001+ employees
      Vendor
      The Story Board helps me keep track of my stories and assigned tasks. There are things we often forget to update or change.

      What is most valuable?

      I like the Story Board since it helps me keep track of my stories and any tasks assigned.

      How has it helped my organization?

      It keeps everyone involved accountable to make sure the project moves along in a good pace. Since it is also viewable to all involved, it allows everyone to see where the project is at any moment.

      What needs improvement?

      I think the areas for improvement are mostly related to the user. There are things we often forget to update or change.

      For how long have I used the solution?

      I have been using Agile Central going on 3.5 years.

      What do I think about the stability of the solution?

      We have not had problems with stability.

      What do I think about the scalability of the solution?

      We have not had problems with scalability.

      How are customer service and technical support?

      I haven’t requested any technical support.

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

      I haven’t used anything but Agile Central.

      How was the initial setup?

      It’s been so long, that I honestly don’t recall the initial setup. It must not have been difficult, since it’s not something that sticks out in my mind.

      What's my experience with pricing, setup cost, and licensing?

      I was not involved in any of the pricing or licensing. I’m just a user.

      Disclosure: IT Central Station 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.
      it_user636105
      SAP Consultant at a manufacturing company with 10,001+ employees
      Vendor
      The Kanban view helps track user stories. The reporting tools are easy to configure and use.

      What is most valuable?

      I liked the overall user interface of Agile Central. It’s so much more user friendly. The Kanban view really helps daily tracking of user stories. The reporting tools available are easy to configure and use.

      What needs improvement?

      Previously, to upload test cases we usually used the Agile Central add-in for MS Excel. But as per recent changes, they have made Single Sign On to access Agile Central due to which, the add-ins seems not to be working.

      For how long have I used the solution?

      I have used Agile Central for two years.

      What do I think about the stability of the solution?

      I remember that there were two incidents Agile Central was down or I was unable to login.

      What do I think about the scalability of the solution?

      We have not faced any issues.

      How are customer service and technical support?

      I haven't had a chance to use technical support.

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

      I have not used a previous solution.

      What's my experience with pricing, setup cost, and licensing?

      I’m not aware about price and licensing because of my role.

      What other advice do I have?

      CA should keep doing what they're doing to make it better.

      Disclosure: IT Central Station 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.
      it_user636102
      Sr Tech Ops Support System Analyst at a transportation company with 10,001+ employees
      Vendor
      The Plan/Plan and Plan/Time boxes have proven to be the most useful for me to keep track of the development progress.

      What is most valuable?

      The Plan/Plan and Plan/Time boxes have proven to be the most useful for me to keep track of the development progress.

      How has it helped my organization?

      In the past, we used the JIRA system. It was very difficult to track progress. With the agile method, we can break things down to manageable pieces. Our deliverables to production have increased as a result, and I can clearly see if we are moving at the speed and in the direction to best serves the business.

      What needs improvement?

      It’s hard to say if it is a product improvement or business use improvement that is needed. But, managing the backlog has proven to be an issue. There are stories written for the same purpose, but in different words. If there was some way to question the writing when the subject is very similar; as to the need for the new story.

      I don’t really think this is a product issue. The tools are there, but the business seems to not be utilizing them. The duplicate story issue is a business issue. I don’t see how the application can prevent this; especially since when developing, the same words can be used in multiple stories with minor differences in the tasks desired.

      I know initially I thought Agile could put some sort of alert if the wording was similar; but that is a task too large and out of the scope of design.

      As a business user, I just need to insure myself and my PM are taking better care in reviewing our backlog

      For how long have I used the solution?

      We started using this system about 3-4 years ago. My only issue is that I work on 3-4 different projects and each team uses the application differently.

      What do I think about the stability of the solution?

      No stability issues for me. I’ve never been unable to access and/or update.

      What do I think about the scalability of the solution?

      No issues with scalability for me either.

      How are customer service and technical support?

      I’ve only needed technical support to allow a new user access; I would like a clearer process. Currently, I email the project manager and then they take up to a week or more to provide access. If this could be streamlined and expedited, this would be great.

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

      We used the JIRA method and changed as our business leadership directed me to change to Agile Central.

      How was the initial setup?

      The initial install was complex. But this was due to the lack of training. As with most changes, I was thrown into it first and then had classes. But this is a business practice, not that of Agile Central.

      Which other solutions did I evaluate?

      I was not part of the decision process.

      What other advice do I have?

      Take a course or two before you start using it, so that you understand the process. Especially if it is different from your current business practices. The courses have been well run and informative. But, take care in choosing the class; some are for more experienced users.

      Disclosure: IT Central Station 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.
      it_user635472
      Principal Scrum Master, Coach at a tech vendor with 51-200 employees
      Vendor
      I really value the customizable dashboards, taskboards and easy filters. Enterprise backups could be improved.

      What is most valuable?

      I really value the customizable dashboards, taskboards and easy filters.

      How has it helped my organization?

      New features with Team Capacity Plan have helped our organization.

      What needs improvement?

      Performance is very bad especially late evening and on Fridays. Enterprise backups could be improved.

      For how long have I used the solution?

      I have used it for three years.

      What do I think about the stability of the solution?

      I did not encounter any stability issues.

      What do I think about the scalability of the solution?

      There were some scalability issues after integration with internal tools like TFS.

      How is customer service and technical support?

      Technical support has lots of room for improvement. We do not get the support that we need for…

      What is most valuable?

      I really value the customizable dashboards, taskboards and easy filters.

      How has it helped my organization?

      New features with Team Capacity Plan have helped our organization.

      What needs improvement?

      • Performance is very bad especially late evening and on Fridays.
      • Enterprise backups could be improved.

      For how long have I used the solution?

      I have used it for three years.

      What do I think about the stability of the solution?

      I did not encounter any stability issues.

      What do I think about the scalability of the solution?

      There were some scalability issues after integration with internal tools like TFS.

      How is customer service and technical support?

      Technical support has lots of room for improvement. We do not get the support that we need for problem resolutions.

      How was the initial setup?

      Initial setup was straightforward.

      What's my experience with pricing, setup cost, and licensing?

      This is expensive compared to other tools like JIRA.

      Which other solutions did I evaluate?

      We evaluated JIRA and VersionOne.

      What other advice do I have?

      Compare other products before making a decision on features and pricing along with customer support reviews.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user631623
      Principal Analyst at a comms service provider with 1,001-5,000 employees
      Vendor
      Allows us the opportunity to not need a Kanban board and physically co-locate it. We can do it online.

      What is most valuable?

      The most valuable feature is the ability to track projects; not so much the reporting, but what you enter and the use of the product, and that's for tracking purposes. That's why it's important to me.

      How has it helped my organization?

      It allows us to better scrum and Kanban. It allows us the opportunity to not need a board and physically co-locate it. We can do it online.

      What needs improvement?

      Building custom reports is difficult and cumbersome. Trying to find the correct field name to test is only part of the problem. The field name and qualification changes depending on what level I am trying to report.

      When reporting at the task level, the story needs the story qualification whereas when reporting at the story level, the qualification is not needed. When reporting at the task level, I cannot qualify based on Feature Group. This limits my ability to programmatically limit my results. The syntax of the reporting is also cumbersome. The help is only limited help and is not written for non-programmers.

      Solution: Provide a query help that actually lists all of the fields at each level. Even when selecting “To see a list of all fields available for each type of work item, check your Web Services API documentation

      It is easy to put information into Rally but it is all overhead without an easier way to get the data back out. I have team members who continue to double entry the Rally data into a spreadsheet just so they can more easily produce the reports that are helpful to them.

      For how long have I used the solution?

      I have used it for about three years.

      What do I think about the stability of the solution?

      Over the last couple of years, it's had moments of slowness, but it seems like they've resolved that, and every so often it goes down, but that just seems like it's a few minutes, so that's more like a support type of thing. So, it's not a big stability problem.

      It is very hierarchical in structure, rather than relational. Maybe if it was built on a more relational database concept, it might be a little bit easier to manage.

      What do I think about the scalability of the solution?

      I don't see any scalability problems.

      How are customer service and technical support?

      I've talked with tech support but mostly about reporting and trying to get the information back out of it that we need. I use internal support teams, so it's Comcast employees that are supporting me.

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

      It was a corporate direction to switch. The tool that we were using before was very poor at accomplishing what it needed to accomplish, so anything would have been better.

      How was the initial setup?

      I wasn't involved in the setup; I was a consumer.

      What's my experience with pricing, setup cost, and licensing?

      I was never part of the pricing and licensing. Training definitely; everybody that's using it should go through some training, but a lot of the training was very generic in terms of using CA Agile Central and it wasn't specific to the team's application.

      The tool actually includes a lot of things that most teams don't do. That information was included in the training, but was never applied, and yet some of the things that we needed to do weren't covered in detail in the training like they should have been, so it was a lot of groundwork to come up to speed on that.

      What other advice do I have?

      My advice would be to make sure that you're implementing it in conjunction with agile methodology. If you implement this tool with waterfall, you will see that it's very oriented towards agile, and it's set up and structured to support agile and not set up and structured to support waterfall methodology.

      I think that it isn't that flexible for helping with teams to migrate to agile; it's not very flexible with customizing for my team. There are a lot of pieces of data that my team needs, and we're having to use non-ideal fields for those. I know that that's the way that it's installed in our application, but a lot of the customization that's available in CA Agile Central isn't available to me to do. So, I would say that it would need to trickle down to the group admins, the ability to be a little bit customized, to be able to customize it to the team.

      Disclosure: IT Central Station 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.
      it_user629046
      IT Project Portfolio Manager at a tech vendor with 5,001-10,000 employees
      Vendor
      Shows how much capacity each team member has for the next sprint. Tasks can be traded between users.

      What is most valuable?

      • Sprint tracking + Kanban board (Iteration Status app): Informs me how well we are doing in our sprint, and what is the next part to work on.
      • Burn-down graph.
      • List of stories sorted in priority order.
      • Kanban Board to visualize work in progress.
      • Sprint planning (Iteration Planning app): Helps me draft plans based on my team’s velocity, and visualize my team’s roadmap for feedback on my team’s priorities for the upcoming sprints (user story level).
      • Team sprint capacity management (Team Status app): Useful app to elicit the conversation of how much capacity does each team member have for the upcoming sprint, and calculate whether we are stretching our team members too thin. In addition, we can easily trade tasks from one user to another, as needed.
      • Release planning (Release Planning app): Helps me draft plans based on my team’s velocity and visualize my team’s roadmap for feedback on my team’s priorities for the upcoming months or quarters (feature level).
      • Portfolio hierarchy (Portfolio Items app): Allows me to define the epic, feature, story breakdown of my team’s work. Also, it allows me to visualize the dependencies between teams.

      How has it helped my organization?

      It provides teams the ability to define, prioritize, and monitor the progress of both their operational and project work. The big win is the fact that we are using the same tool outside of IT. It’s a huge win when your internal customers are also using the same platform for defining, tracking, monitoring progress on their objectives. The non-IT departments that have teams using the tool are marketing, operations, training, and human resources.

      Provides portfolio, department, and program managers the ability to define, prioritize, and monitor progress on larger initiatives being delivered by multiple teams.

      What needs improvement?

      Make it easier to export information outside the tool for additional data visualizations and metrics. The tool does have a REST API, but that requires us to use a developer. The tool does have CSV exports for everything, but that’s a manual step.

      Make it easier to share CA Agile Central information to non-CA Agile Central users. Not everyone in our organization is a licensed CA Agile Central user. Those users who are not licensed and provide work to the users on our platform, have a hard time tracking their work requests.

      Provide the ability for team members to customize their custom fields/custom workflows without needing a tool administrator to set it up for them.

      Mobile friendliness: It would be nice if we had the ability to view and change the state on assigned tasks from a phone.

      CA Agile Central integration is great! Currently, everyone who has an CA Agile Central license has a Flowdock license. Unfortunately, it costs a lot of money to add non-CA Agile Central users to Flowdock. And a messaging platform is useless if you can’t message all your stakeholders within the organization.

      There is no ability to easily create a work intake portal where a stakeholder can enter new work, have it routed to the appropriate team, and be able to track the work status. You can buy an integration engine that syncs your ticketing system with CA Agile Central, but again, that’s more money.

      For how long have I used the solution?

      I’ve used CA Agile Central for four years.

      What do I think about the stability of the solution?

      Once in a while, it has performance problems. Nothing terrible and nothing we have not seen with other SaaS vendors.

      What do I think about the scalability of the solution?

      We have not had any issues with scalability.

      How are customer service and technical support?

      Technical support is fine. They assign a customer success coach that we use for tools training and tips. We are pretty self-sufficient now that we do not have to lean on them very often.

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

      We did have other tools before CA Agile Central and we currently still use other vendors for managing other types of work. The best tool for the job really depends on the type of work you do, the work management methodology the team uses to get work done, and who the team’s stakeholders are.

      How was the initial setup?

      Setup was easy for team-level usage. It gets more complex as you try to scale up your agile practice. Scaling up only happens when teams agree to portfolio standards such as your work hierarchy and planning cadence.

      What's my experience with pricing, setup cost, and licensing?

      It is an expensive tool. Bring in a good negotiator. The money is worth it when you are trying to do agile at scale.

      Which other solutions did I evaluate?

      We evaluated:

      • VersionOne
      • JIRA
      • Trello
      • Smartsheet
      • Taiga.io
      • Tuleap

      What other advice do I have?

      The nirvana for all organizations is to implement end-to-end enterprise business agility. It’s a lot easier to do that when you have a tool that allows you to capture all the data you need and systemically roll that up for your enterprise portfolio reporting. CA Agile Central is a tool that enables you to do that. BUT, in order for data to be entered consistently, you really do need an enterprise coach. If you are not implementing agile at scale, I would recommend a cheaper tool that is also mobile-friendly. CA Agile Central is a tool that solves the agile-at-scale challenge, and is still user friendly enough to handle non-IT work loads.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user631632
      Director of Digital Engagement Delivery at a healthcare company with 10,001+ employees
      Vendor
      The UI allows me to collaborate, capture decisions, and so on.

      Pros and Cons

      • "The most valuable features are in-line editing, easy custom view setup, intuitive and helpful visuals (e.g., contextual formatting) and the collaboration features."
      • "More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc."

      What is most valuable?

      The most valuable features are in-line editing, easy custom view setup, intuitive and helpful visuals (e.g., contextual formatting) and the collaboration features.

      The CA Agile Central tool’s UI is robust and user-focused enough that it allows me to collaborate, capture decisions, etc. right there in the tool in real time, versus having to add any steps outside the tool – e.g., hold a meeting, take notes, then translate notes into the tool. That is a huge efficiency and accuracy booster for us.

      The platform comes with built-in and easily configurable reports that are optimized for audiences up and down the stack, from team level through leadership. That means no translation or manual re-representing of information stored in the tool into complicated spreadsheets, PowerPoints, etc. I can easily run a view, screen capture, and pop in a slide as needed. This is a much better use of a PM’s time. We can now stop spending half our time running things and half our time translating it into pretty pictures for leadership, and instead invest more time in facilitating and improving the high-quality interactions that form the backbone of successful agile delivery.

      How has it helped my organization?

      In setting up agile delivery operations, CA Agile Central’s training and platform have been instrumental to our progress and success. CA Agile Central was a key ingredient to that delivery transformation. Also, CA has updated the tool to support Scaled Agile Frameworks, which is a key competitive differentiator for them.

      What needs improvement?

      I miss the “Rally” brand – I do not find the CA Agile Central branding as compelling, but I get the reasons driving the re-brand.

      More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc.

      It would be good for CA to develop a strategy to address the competitive threat coming in from Atlassian.

      For how long have I used the solution?

      We have been using the product for about four years.

      What do I think about the stability of the solution?

      I didn't encounter any stability issues.

      What do I think about the scalability of the solution?

      I didn't encounter any scalability issues.

      How are customer service and technical support?

      I have not engaged their technical support, so I cannot offer a perspective there.

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

      Our enterprise was historically a Rally shop, so I did not switch from anything else.

      How was the initial setup?

      The setup was straightforward, as long as you have some grounding in agile processes and philosophies.

      What's my experience with pricing, setup cost, and licensing?

      Frankly, pricing is expensive and needs to be carefully planned for when budgeting. Our licensing is handled by a centralized group at our company called the Application Lifecycle Management team.

      Which other solutions did I evaluate?

      CA Agile Central/Rally was already embedded at my company when I came on board. However, while I have been here, there was a move from some factions of IT leadership to make us move to the IBM Rational Suite. We were able to push back on that edict by demonstrating the clear superiority of the CA Agile Central solution over IBM’s. However, there are still pushes happening from that team, focused on the higher cost of CA over IBM.

      What other advice do I have?

      Get training first on agile methodology. Then, consider engaging professional services to help you launch your first release, if you are completely new to agile. There is a very high benefit to bringing in experienced experts as they will greatly increase your chance of success.

      Disclosure: IT Central Station 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.
      it_user635481
      Engineering at a comms service provider with 10,001+ employees
      Real User
      With the reports that can be generated, I can create a test case and results, and share with other members who don’t have access.

      What is most valuable?

      I am a software tester, so the features I found that are valuable to me are importing of test cases, creating new test cases, editing test cases, executing test cases, and generating test reports.

      Creating test cases is important to me because it allows to me write test cases in an MS Excel spreadsheet and quickly import them into CA Agile Central, saving me a lot of time having to manually rewrite the test cases.

      Editing of test cases is also very important because I can quickly make changes to reflect changes in the user stories.

      Generating reports is a great tool and is very important because I can create a test case and results, and share with other members who don’t have CA Agile Central access.

      How has it helped my organization?

      Using CA Agile Central, my organization was able to develop, test, and deploy software much quicker than we used to under the waterfall methodology.

      What needs improvement?

      The ability to customize reports needs improving by providing users with features for selecting what they want to see on the reports, how they want to lay out the reports, and create a schedule for a report to be generated automatically and sent by email.

      When I create a custom report (see below screen), I want to be able to have my report run automatically once a day and email the scrum master.

      For how long have I used the solution?

      We have used this solution for over five years.

      What do I think about the stability of the solution?

      We have not encountered any stability issues.

      What do I think about the scalability of the solution?

      We have not encountered any scalability issues.

      How are customer service and technical support?

      I have never had to use technical support.

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

      I am not aware of any other previous solutions.

      Disclosure: IT Central Station 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.
      it_user627027
      Scrum Master at a tech services company with 10,001+ employees
      Consultant
      I like the real-time status tracking and the ability to see vital information in one screen.

      What is most valuable?

      • Real-time status tracking
      • Capacity planning
      • Ease of configuration of reports and dashboards
      • Iteration and release planning
      • Ability to personalize views
      • Ability to see vital information in one screen as opposed to having to navigate to multiple pages

      How has it helped my organization?

      Capacity and resource planning help us understand how much work an individual can accommodate per sprint and if any one person is over-allocated.

      Release planning is made simpler by the Agile Central interface.

      What needs improvement?

      Honestly, I can’t think of any areas that need improvement.

      For how long have I used the solution?

      I have been using Agile Central for four and a half years.

      What do I think about the stability of the solution?

      Once or twice in a couple years we experienced outages, but not frequently.

      What do I think about the scalability of the solution?

      I have used Agile Central in small organizations, as well as large organizations working in a Scaled Agile Framework (SAFe) environment.

      How are customer service and technical support?

      I have never had to use technical support.

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

      I have not previously used another solution, but I have to use JIRA now and I would rate JIRA a 3/10 compared to Agile Central at a 10/10.

      How was the initial setup?

      I was not an admin of the tool, so I’m not sure how complex the application setup was.

      What's my experience with pricing, setup cost, and licensing?

      I don’t know about the pricing.

      Which other solutions did I evaluate?

      I was not in charge of making the decision to purchase the product.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user628020
      Dealing Technology at a financial services firm with 1,001-5,000 employees
      Vendor
      Provides traceability from the strategic objective to task level.

      What is most valuable?

      There are so many high-value features it is hard to choose but I will say the most valuable feature is the fact that it provides traceability from the strategic objective to task level with rolled up and detailed reporting. This is valuable as activity is joined up from top to bottom; a developer in a feature team can trace their input at the task level all the way up the hierarchy to the strategic objective they are helping to deliver. On the flip side, the CTO can have a view of real-time progress against the delivery of strategic objectives, drill down to the portfolio epics and business outcomes with the potential to see the value being delivered.

      How has it helped my organization?

      It has enabled the transition from a project-based portfolio to a product-based portfolio.

      What needs improvement?

      It could do with a wider range of colours for cards and the Kanban features need some improvement (which I know is on the way this year). The colour swatch for cards in Kanban board views is quite limited; I think there are 9 possibilities. Using these to visually differentiate cards on a busy board becomes less valuable when multiple themes are sharing a card color.

      Kanban features should be built around flow, which implies they should not be constrained by time boxes. This is of particular relevance when considering many of the views that, by design, require one to select a time box. This is also true of reporting. There are some things to consider, though, as when viewing a personal or team board, one doesn’t want to see the entire backlog, so it would be useful if that could be limited to a user-defined number of stories.

      For how long have I used the solution?

      I have been using Agile Central for seven years.

      What do I think about the stability of the solution?

      We have never had stability issues in seven years of use.

      What do I think about the scalability of the solution?

      It is the most scalable product of its kind out there.

      How are customer service and technical support?

      Technical support is excellent.

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

      I have used JIRA, Trello and IBM Rational, but none of them are close to Agile Central.

      How was the initial setup?

      Initial setup was very straightforward and guided by CA consultants.

      What's my experience with pricing, setup cost, and licensing?

      If you want the very best, expect to pay accordingly. But you will get ROI from it, especially if you are doing agile well and at scale.

      Which other solutions did I evaluate?

      In my current role, the firm evaluated JIRA, Agile Central, VersionOne and IBM Rational (I think).

      What other advice do I have?

      You will only regret it if you have chosen the Rolls Royce when you could have got by with a Nissan Micra.

      Disclosure: IT Central Station 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.
      it_user628026
      Senior Software Engineer at a healthcare company with 1,001-5,000 employees
      Vendor
      The UI/UX is good with friendly navigation.

      What is most valuable?

      The UI/UX of the tool is good with friendly navigation.

      How has it helped my organization?

      We can track of our tasks and project estimations.

      What needs improvement?

      It’s a good tool to use. Charts and dashboards should be more interactive.

      For how long have I used the solution?

      I have used Agile Central for over two years.

      What do I think about the stability of the solution?

      Stability is good.

      What do I think about the scalability of the solution?

      Scalability is good.

      How are customer service and technical support?

      I rate technical support 8/10.

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

      I used to use JIRA.

      How was the initial setup?

      Setup was easy.

      What's my experience with pricing, setup cost, and licensing?

      What is most valuable?

      The UI/UX of the tool is good with friendly navigation.

      How has it helped my organization?

      We can track of our tasks and project estimations.

      What needs improvement?

      It’s a good tool to use. Charts and dashboards should be more interactive.

      For how long have I used the solution?

      I have used Agile Central for over two years.

      What do I think about the stability of the solution?

      Stability is good.

      What do I think about the scalability of the solution?

      Scalability is good.

      How are customer service and technical support?

      I rate technical support 8/10.

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

      I used to use JIRA.

      How was the initial setup?

      Setup was easy.

      What's my experience with pricing, setup cost, and licensing?

      They should go for it.

      Which other solutions did I evaluate?

      I evaluated JIRA.

      What other advice do I have?

      They should definitely use it.

      Disclosure: IT Central Station 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.
      it_user629055
      QA Analyst, Business Unit at a healthcare company with 1,001-5,000 employees
      Vendor
      Its Excel plugin provides real-time extraction of data. On the test case level, I cannot create a day-over-day report.

      What is most valuable?

      The most valuable feature is that it follows the agile methodology more than ALM or JIRA. However, I know companies using more than one tool, separating test management and requirements, which I agree to.

      Currently, I would prefer to use QAComplete by SmartBear to track test cases, since CA Agile Central doesn’t work well with reporting on that level or for that matter on any level.

      How has it helped my organization?

      One of the jobs that I adopted was to design procedures using CA Agile Central. In the beginning, without a procedure (not sure if the online help has much “method” suggestions, which it should), it does allow the agile process to be followed easily from features > user stories > team capacity > sprint sizing > test management and defect management. If properly used, it can be an amazing tool relaying to scrum masters, project managers and for all management levels to show exactly how a sprint is going. I will say the CA Agile Central Excel plugin is great for real-time extraction of data, i.e., if you know how to use it correctly, and out-of-the-box you will not know the hidden tricks that I have learned. But, CA Agile Central Support is actually very good.

      What needs improvement?

      On the test case level, I feel there are a couple fields missing, i.e., I cannot easily create a day-over-day report. I cannot find out what is planned for the QA team, as I cannot track what is “ready”, or as to the day when it’s planned to execute.

      For how long have I used the solution?

      I have been using this solution for one and a half years now.

      What do I think about the stability of the solution?

      No outages have yet been experienced.

      What do I think about the scalability of the solution?

      There are always latency issues when accessing anything in CA Agile Central Portfolio Manager; it takes a good 10 seconds to load. This isn’t only due to concurrent users, it can be the case at 1 AM when no one is on. It hasn’t been that much of a nuisance.

      How are customer service and technical support?

      I would rate the technical support a 10/10. The funny thing is that I didn’t care much for the CA Online Support. I didn’t know there was a ticket support system. However, once I did, my goodness they were great in returning answers.

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

      We did previously use HPE ALM. HPE ALM didn’t produce much of good reporting, yet neither does CA Agile Central. Plus, the agile process was all wrapped up in CA Agile Central, so we decided in our department not to maintain two tools. Other departments and UHG do use both tools, and some HPE ALM still.

      How was the initial setup?

      The setup was very simple; it was probably easier than HPE ALM.

      One major problem when obtaining CA Agile Central is ensuring the framework is exactly what you want. Many don’t look at this aspect and later realize that they have lost traceability and that they should have created a dropdown menu instead of free text (i.e., there is a defect found in the free text field – this should be a code drop version, adaptable by iteration). Yet, I’m still not sure at the moment what is and what isn’t adjustable since I’m not an admin. However, from what I did hear is, when something changes, it may change the enterprise and not just the project; not sure about that yet though.

      What's my experience with pricing, setup cost, and licensing?

      Count the cost! Find out what you have in place and how much longer you are charged for and then compare this to your budget. I find it a big waste in having too many tools, but it really matters as to what you want to see and how much you want to maintain. For example: With the SOP that I created for using CA Agile Central, I can create almost perfect reports from Excel. However, the problem here lies in Excel! You need manual intervention to formulate and macro out the data, thus involving more costs.

      Which other solutions did I evaluate?

      Only afterwards did I evaluate other options, since I was not a decision-maker; they already owned HPE ALM and CA Agile. SmartBear QAComplete is a great tool and probably my number 1 choice, i.e., if I had the choice. It also works with SoapUI, XML, Selenium and manual scripts.

      What other advice do I have?

      I would consider it highly. Be sure what you want to accomplish; it’s not reporting-friendly. It is good with team burndown and sizing.

      Although, it’s agile-based, it’s not like HPE ALM that informs you via emails when something changes, i.e., even if you enable notifications, it’s fluky, as you get more emails than needed. CA Agile Central has a dashboard per user feature, as to when logged in that must be viewed.

      The key thing is process! You must know how it works and how you want to use it, before you implement it. To be honest, there is only one way to use it that I have identified above.

      Disclosure: IT Central Station 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.
      it_user631638
      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.

      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 technical 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: IT Central Station 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.
      it_user631641
      Director of Project Management at a financial services firm with 51-200 employees
      Vendor
      It is intuitive to use and is customizable.

      What is most valuable?

      The product is very intuitive to use, which drastically reduces training and onboarding time with new employees. It is highly customizable, which is both good and bad.

      How has it helped my organization?

      CA Agile Central helps us plan, organize, schedule and prioritize hundreds of feature requests into our release calendar. There is simply no way we would be able to release as many new products, enhancements or defect fixes without it!

      What needs improvement?

      Customization can be a bit complicated but it is a highly customizable tool, which has its own significant benefits. It just takes a bit of practice working through the tool and its many options.

      You need to use caution when adding custom fields as you can only disable them once created; you cannot delete a custom field.

      Overall, standard/canned reporting options are probably the weakest part of the platform but exporting a data dump for reporting outside of the tool is very easy.

      For how long have I used the solution?

      Rally/CA Agile Central has been in use at our organization for eight years.

      We are a hybrid SDLC/agile shop and use the tool heavily to support our release planning and execution plans. We did adapt our SDLC process to use the terminology in the tool (Features, User Stories, Tasks and the Portfolio Hierarchy). We have people build features under a portfolio hierarchy which creates our master backlog. We assign built features across various releases to build our deployment schedule.

      We use CA Agile Central with the following enabled modules:

      • Integration Hub
      • CA Agile Central Portfolio Manager
      • CA Agile Central HP Quality Center Integration
      • CA Agile Central IBM ClearQuest Integration
      • CA Agile Central Idea Manager
      • CA Agile Central Quality Manager
      • CA Agile Central Support Manager
      • CA Agile Central Time Tracker
      • SSO
      • IP Restriction
      • Extension Whitelist

      What do I think about the stability of the solution?

      As with any cloud-hosted, SaaS model, we occasionally run into unscheduled downtime but they are usually able to switch data centers quickly where there are issues. They also maintain a system status page to monitor maintenance and repair time/updates.

      What do I think about the scalability of the solution?

      The tool scales effortlessly. The only drawback is if we wanted to create a new workspace because migrating existing data between workspaces is difficult, especially if heavily customized.

      How are customer service and technical support?

      The technical support is outstanding! We have a rep who contacts us quarterly to review what’s new and what’s in their development pipeline. Online and the web knowledge base answers most questions. Support is quick and easy to access and they turn-around tickets quickly, most times on the first call. They also helped us with building custom reports, pages and add-on apps.

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

      I don’t know of any previous solutions, as this tool was here well before me.

      How was the initial setup?

      I built out the most recent workspace and it was pretty easy after a week or so of trial and error, but that was mostly getting our portfolio hierarchy structure right.

      What's my experience with pricing, setup cost, and licensing?

      Pricing is competitive for what you get even at the most basic level. It reflects a typical SaaS model of pricing/licensing.

      Which other solutions did I evaluate?

      I am not aware of any other evaluated solutions.

      What other advice do I have?

      If you are an agile or even hybrid agile shop, this is an excellent tool. If you are a more traditional PM or waterfall model, it may not be your best option. It’s really built to support agile methodologies.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user629931
      Associate consultant at a tech company with 10,001+ employees
      Vendor
      It helped me keep track of the bugs that the app has and the status of each one.

      What is most valuable?

      There are multiple valuable features of this product and the most important for me is the section related to bugs. It helped me during this time to keep track of all the bugs that the app has, the status of each one and at the same time, we were able to keep notes for each element. In addition, the ability to add the concerned developer as a watcher, so in this way if the bug is not fixed, then they would be notified.

      How has it helped my organization?

      This product had helped my organization so much because it helped us keep everything tracked.

      We are now able to predict each team member's capacity in a single click.

      We use the report to see if we are going to reach our deadlines and we are able to easily make decisions thanks to the available reports.

      What needs improvement?

      I think the only area that needs improvement will be the front end. It is very good as is but I think it could be better as the colors are a little faded.

      For how long have I used the solution?

      I have been using this solution for almost a year and a half.

      What do I think about the stability of the solution?

      There were no stability issues.

      What do I think about the scalability of the solution?

      There were no scalability issues.

      How are customer service and technical support?

      I have never contacted the support.

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

      I have used multiple tools before CA Agile Central. I switched because in CA, everything was in the same platform and it is a pretty intuitive tool. I didn’t need any tutorial, as I did for the other tools.

      How was the initial setup?

      The setup was pretty intuitive.

      What's my experience with pricing, setup cost, and licensing?

      I don’t have a lot of information about the pricing because I had the IT team handle that for me.

      What other advice do I have?

      Give it some time. It is very difficult to change this kind of tool, especially when you are in the middle of a project. However, I would advise people implementing it to take their time to check all the different functionalities and think about how to use it effectively.

      It has everything that I need in my daily job routine.

      Disclosure: IT Central Station 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.
      it_user629937
      Product Owner - Business Analyst at a healthcare company with 1,001-5,000 employees
      Vendor
      The portfolio views and reports helped me to create, prioritize, manage and accept portfolio capabilities, features and user stories.

      What is most valuable?

      As a Product Owner/Product Manager on an application team, it was my job to create, prioritize, manage, and accept portfolio capabilities, features, and user stories. The portfolio views and reports were the tools I used the most to do that.

      The Agile process my team follows anticipates that requirements and priorities will change from sprint to sprint. Having a real-time view of what has been accomplished, what is in progress, and our backlog, that is easily accessible to all stakeholders, (customers, executives, implementation members, and delivery leads, as well as our staff of multi-discipline Product Owners and Managers) is critical to building and creating a high quality and viable product.

      My scrum masters walked through the analysis, development, and testing tasks every day with team members, using the Team Status page to ask each team member (onshore, nearshore and offshore) for status on the prior day’s work and plans for today. As a Product Owner, I monitor User Story status via a Ready To Accept app on my Dashboard for User Stories that are ready to be accepted because all the required tasks are completed.

      By using the Portfolio Items page I can adjust priorities and accept completed features from a single page.

      How has it helped my organization?

      It is used as a source of truth on workstream, workstream progress and issue management.

      What needs improvement?

      • Bulk priority change of portfolio items
      • Portfolio feature
      • Dependency reports

      In our project, when a feature is completed, we mark it as completed but then don’t want to have it show at the top of the priority list and don’t want to constantly add filters to filter out completed items. So we put the completed items at the bottom of the backlog by changing the priority. There’s no way to do this except one at a time. With thousands of features, this is cumbersome.

      There is no good way to get an overall view of feature dependencies except to go to one feature at a time and look at its specific dependencies. The team could have made great use of a report/dashboard of some kind (I failed at coding my own) that gave a larger view of feature inter-dependencies.

      For how long have I used the solution?

      We have been using the solution for two years.

      What do I think about the stability of the solution?

      Generally, we did not encounter any issues with stability.

      What do I think about the scalability of the solution?

      There was some slowness noticeable on days of heavy usage by many users (peak usage impact).

      How are customer service and technical support?

      I did not use the technical support.

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

      We did not previously use a different solution.

      What other advice do I have?

      Use relational database concepts to relate items together instead of continuing to use old location-based organization concepts.

      Disclosure: IT Central Station 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.
      it_user627030
      Delivery Pipeline Manager at a comms service provider with 10,001+ employees
      Vendor
      I like the manner data is entered/viewed. It provides a range of out-of-the-box reports.

      What is most valuable?

      • It is easy to use.
      • The flexible manner data is entered/viewed.
      • Good technical and company support.
      • Good range of out-of-the-box reports and easy-to-construct customized reports.

      How has it helped my organization?

      Parts of our business use Agile Central to deliver in an agile and features-based method. It is a much more user-friendly product compared to other products in market.

      What needs improvement?

      Pricing could be improved. Compared to JIRA, it is not cost effective for a large user base (1000 user plus). User licenses should be a group level within the company, rather than company level.

      Jira is more cost effective once set up – no cost per user seat.

      RALLY costs around $60/month/user seat

      If you then multiply this cost by the number of users (let's say 2000 – 5000 users), it's a very large amount of money, not effective from a price point of view.

      If we could get an Enterprise license at a reasonable price then, management's view of the product may change.

      For how long have I used the solution?

      I have been using Agile Central for two years.

      What do I think about the stability of the solution?

      It has good availability.

      What do I think about the scalability of the solution?

      We did not have scalability issues.

      How are customer service and technical support?

      Technical support is good. A local resource is always available, is knowledgeable and visits us on site when needed.

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

      Excel sheets were previously used, prior to moving to an agile-based delivery.

      How was the initial setup?

      Setup was easy in conjunction with technical/local support to discuss the method of working in our company.

      What's my experience with pricing, setup cost, and licensing?

      There is good pricing for a small number of user licenses (i.e., 50 to 200) for outcome (effective usage including reporting).

      Which other solutions did I evaluate?

      We evaluated JIRA and others.

      Disclosure: IT Central Station 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.
      it_user627045
      System Engineer at a comms service provider with 10,001+ employees
      Real User
      As a requirements engineer, most valuable is user story writing/editing/reviewing with peers.

      What is most valuable?

      As a requirements engineer, most valuable is user story writing/editing/reviewing with peers.

      How has it helped my organization?

      It is supposed to shorten the project’s lifecycle. I do not have proof of this.

      What needs improvement?

      The text editor is for sure an area with room for improvement. Under IE 11, the Backspace key is not functioning as expected; it deletes and also inserts empty rows. If you continue, you end up with a lot of empty rows that you do not want. The DEL key, as well. Formatting is difficult.

      A CR (carriage return) always creates a new paragraph. But sometimes you just want to stress something in relation to previous statement, but you do not want it in a new paragraph.

      Pasting text from Word can create a lot of formatting issues, mostly in cases when the font is not recognized. Also, features such as graphics and tables are supported but only if coming from Word. So, if you want to eliminate a column or a row, you need to go back into Word, make the update, and then past back in the editor. In fact, if you want to come back to a text and edit it, it is very difficult to maintain the initial format.

      These issues slowed down my work.

      My comments are meant to help improve the product, not criticize it.

      For how long have I used the solution?

      I have used Agile Central for five years.

      What do I think about the stability of the solution?

      We have not had stability issues.

      What do I think about the scalability of the solution?

      We have not had scalability issues.

      How are customer service and technical support?

      Technical support is very good.

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

      This is our first solution for agile projects.

      How was the initial setup?

      Setup was somehow difficult until all folders had been created and the rules on how to use them were set up. This has nothing to do with the product itself.

      What's my experience with pricing, setup cost, and licensing?

      I had no involvement in this, so no advice.

      Which other solutions did I evaluate?

      It was a company decision. I just adopted the company decision.

      What other advice do I have?

      Be very clear in agile and then “map” your knowledge into the product setup.

      Disclosure: IT Central Station 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.
      it_user627060
      System Analyst at a tech company with 10,001+ employees
      Vendor
      I can start at the user story level and then go upstream to create features and link those together. It could have more reporting options besides generating a chart.

      What is most valuable?

      The connection between user stories, tasks, themes, initiatives and test cases, can be easily linked together. And, it allow users to start from any level of structure. For instance, I can start at the user story level and then only go upstream to create features and link those together. The tools provide the flexibility for the user to configure any way they want based on the delivery team working mode.

      How has it helped my organization?

      The project team can easily keep track of progress and the burndown chart that, if auto-populated by the tools itself, is a good indicator for the team to keep track of their velocity.

      What needs improvement?

      For the reporting side, it could have more options besides generating the chart. It would be good if it also allowed infographics.

      For how long have I used the solution?

      I have used Agile Central for a year and a half.

      What do I think about the stability of the solution?

      We have not encountered stability issues.

      How are customer service and technical support?

      I have not used support before.

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

      I did not use a previous solution. So far, I have only used this tool.

      How was the initial setup?

      The initial setup was quiet straightforward and user friendly. The UI interface is not too complex and allows inline editing.

      What's my experience with pricing, setup cost, and licensing?

      I am not sure about this, as the licensing subscription is made under company.

      Which other solutions did I evaluate?

      We did not evaluate any alternatives as our management introduced this tool to us.

      What other advice do I have?

      Have a score card for features that HPE ALM has. I do see some project teams uncertain when adopting Agile Central tools, as they don’t have the score card features and thus it is very hard for them to change.

      Disclosure: IT Central Station 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.
      it_user613554
      SAFe Release Train Engineer (Program Manager) at a tech services company with 1,001-5,000 employees
      Consultant
      The Release Tracking view shows us which features each team is working on during a PI. The discussion feature should be front and center when opening any item type.

      What is most valuable?

      We find the most value in the Release Tracking view. We use this view during draft plan review for our scrum teams. This view allows us to see which features each team is working on during a PI. We can easily see where stories for a feature are scheduled within or across sprints, and we can compare that to priority and any logical sequencing requirements. We can also see any interdependencies between teams. This view is also very useful during a PI to track progress using the burnup chart with its forecast based on empirical trend lines. We view these forecasts per team and also in aggregate for an entire release train.

      The other features that we find valuable include the task board, which is useful sorted by team member for daily scrum; the iteration status for sprint planning; the team and iteration planning pages, which are useful for PI planning and draft plan review; and various Kanban views at the portfolio, program, and team levels.

      The “follow” and “discussion” features are also very valuable for qualitative tracking of work items.

      How has it helped my organization?

      This product is a great fit for organizations using the Scaled Agile Framework. It follows and facilitates best practices for agile and scrum. In many instances, the built-in constraints of this tool have opened discussions about agile best practices, and the comprehensive documentation in the online help knowledge base has provided solid guidance for agile transformation where needed.

      One example of this would be the question of what to do with unfinished work at the end of a sprint. Because the right action is counter-intuitive, this is an area of much controversy and contention across the industry; however, there is an established best practice, which the help section explains and which the tool facilitates. See Manage Unfinished Work: https://help.rallydev.com/mana...

      What needs improvement?

      The discussion feature should be front and center when opening any work item type. The description and acceptance criteria can become irrelevant as soon as work begins. Those areas are better suited to being buried back in a tab rather than the discussion area. The adaptive changes should be the primary focus once work is underway. Updates, questions, decisions, and suggestions should all be the first thing seen when opening a work item. This is implemented well in tools like Asana.

      It should be possible to assign an epic or feature as the parent of a defect. Many organizations struggle to use defects because they do not roll up in the hierarchy to specific features and epics.

      Kanban boards should allow local exit criteria. Currently, the policies are set and viewed globally.

      For how long have I used the solution?

      I have used Agile Central for two years.

      What do I think about the stability of the solution?

      Stability has been an issue at times. We have seen an unacceptable amount of system downtime. This has improved over the last year.

      How are customer service and technical support?

      The product team has been somewhat unresponsive to popular community requests for feature enhancements. Technical support has been responsive, and customer service has been acceptable.

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

      We have previously used Team Foundation Server and we have evaluated JIRA. This product was chosen because it was a good fit for Scaled Agile Framework.

      How was the initial setup?

      The initial setup is relatively straightforward compared to other products.

      What about the implementation team?

      This was implemented through a vendor team. Because this tool is so flexible and can be used in so many ways, we do not recommend attempting the implementation without outside consultation. It is easy to have the configuration fall victim to local anti-patterns.

      What was our ROI?

      Efficiency and effectiveness in our processes have improved by 10 percent with this tool. At scale, and across multiple release trains, this gives us a 15X return on our investment.

      What other advice do I have?

      Do not try to implement this product if you are not using agile at scale. There are simpler, more elegant and intuitive tools.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user607434
      Business Analyst-Property & Casualty Insurance at a tech vendor with 51-200 employees
      Vendor
      Plan, Quality, and Track are valuable menu features. An error appears when updating the status of cards or defects.

      What is most valuable?

      Plan, Quality, Track [Iteration status, burnout charts, etc.]: All these menu features are highly valuable.

      How has it helped my organization?

      Highly helpful for defect tracking and maintaining story cards.

      What needs improvement?

      At times, when we update the status for cards or defects, it shows a message that says something like, "Someone updated the status before, which one to consider: yours or theirs?"

      For how long have I used the solution?

      I have been using CA Agile Central for over 10 months.

      What do I think about the stability of the solution?

      We have had no Issues with stability.

      What do I think about the scalability of the solution?

      We have had no Issues with scalability.

      How are customer service and technical support?

      Technical…

      What is most valuable?

      Plan, Quality, Track [Iteration status, burnout charts, etc.]: All these menu features are highly valuable.

      How has it helped my organization?

      Highly helpful for defect tracking and maintaining story cards.

      What needs improvement?

      At times, when we update the status for cards or defects, it shows a message that says something like, "Someone updated the status before, which one to consider: yours or theirs?"

      For how long have I used the solution?

      I have been using CA Agile Central for over 10 months.

      What do I think about the stability of the solution?

      We have had no Issues with stability.

      What do I think about the scalability of the solution?

      We have had no Issues with scalability.

      How are customer service and technical support?

      Technical support is good.

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

      No solution was used before.

      Which other solutions did I evaluate?

      We didn't evaluate other options.

      What other advice do I have?

      Perfect product for implementing the agile platform.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user572916
      Group Product Manager at a financial services firm with 1,001-5,000 employees
      Video Review
      Vendor
      We still have an organizational hierarchy within the tool. We need to be able to report from different levels of the hierarchy.

      What is most valuable?

      The portfolio manager add-in is very valuable for our company, because it allows our business partners to create their road maps, and then link their road map to their user stories, that our engineering teams then work on. They can roll up the progress and see that at the portfolio hierarchy level. That's a very powerful aspect to the tool.

      Also, all of their reporting, the dashboards, the custom apps, everything that you can create within the tool, makes it very powerful for us as an organization, as well.

      How has it helped my organization?

      The benefits of the solution are the collaboration and transparency. We encourage everyone across the organization to have an ID and to log in to the tool – daily or weekly, whatever their needs are – to see the data. They log in to the tool to see the real-time data. We have really pushed back on teams that would still want to do external reporting, where the data is old and stagnant. I would say that real-time transparency is one of the most valuable aspects for us.

      What needs improvement?

      One of our main challenges right now is that we have not deployed our value streams yet. We still have an organizational hierarchy within the tool. We have the need to be able to report from different levels of the hierarchy. We really need to be able to have a virtual project hierarchy within the tool. I'm looking forward to seeing it. I know that the company's working on a slightly different approach to solve that issue, and we're working with them on those user needs and we'll be working with them on the beta as well.

      What do I think about the stability of the solution?

      We're on the SaaS platform; it is very stable. One of my favorite things about being on SaaS is that, when there's an issue, I don't have to panic and try to work internally with a support team to try to bring the tool back up. I reach out to my technical account manager, she gives me updates, and it's usually back up, relatively quickly.

      How is customer service and technical support?

      I love technical support. They have a personal touch. When you start to work with someone, they stay on your case. Even if it's a long-term case, you get to stick with that person that knows what you're working on. I've been working with someone for months on a rollout of a new piece of functionality and he's stuck with me the whole time; he'll check in with me. I would say that that's a very valuable aspect.

      What other advice do I have?

      I was talking to someone at a recent CA conference. They don't use Agile Central yet and she asked me, "What should we do?" I told them that they should take advantage of CA’s transformation consulting group, to come in and provide that entire solution from start to finish, so they don't get stuck like we did and not having their value streams identified, not having the tool set up and the best way to make them effective.

      It's a partial solution. It's a big problem for us right now.

      Disclosure: IT Central Station 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.
      it_user603816
      Enterprise Agile Coach at a tech consulting company with 10,001+ employees
      Consultant
      Tracks progress against plans and links strategy to execution.

      What is most valuable?

      • Requirements management
      • Development team planning
      • Tracking progress against plans
      • Linking strategy to execution

      How has it helped my organization?

      We now have a more holistic view of how development teams are executing against the enterprise’s strategic roadmap. This improves our ability to prioritize work and to manage our risks and dependencies.

      What needs improvement?

      • Defect and test case management
      • Executive-level reporting capabilities
      • Project management functionality (financials, EVM, resource planning, etc.)
      • Lacks the ability for non-coders to create custom app/widget charts

      For how long have I used the solution?

      I have been using Agile Central for eight years.

      What do I think about the stability of the solution?

      We haven’t had any stability issues. We’ve experienced reliable uptime and few defects.

      What do I think about the scalability of the solution?

      I’m currently working for a large Fortune 500 company and we haven’t any issues with scalability.

      How are customer service and technical support?

      Technical support is excellent; however, some of our users find it a little confusing as to how to submit a case/help ticket.

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

      We previously used a home-grown solution and wanted to switch to a more scalable solution.

      How was the initial setup?

      The initial setup is fairly straightforward but there are certain best practices as to how to configure Agile Central. Typically, the CA Agile Central account manager will provide guidance as to how to best configure Agile Central and will be available to answer ongoing questions as they arise.

      What's my experience with pricing, setup cost, and licensing?

      You can negotiate prices, technical services, and professional services if you need a large amount of seat licenses.

      Which other solutions did I evaluate?

      We looked at VersionOne, Pivotal Tracker, and Trello.

      What other advice do I have?

      Work with your CA Agile Central account manager to determine the best way to implement and configure Agile Central based on your needs. Put together a basic usage policy, training document, and training presentation for users. Limit the number of administrators to a small handful of people. Integrate Agile Central with your other SDLC tools.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user603810
      Test Automation Engineer / Qc Analyst Ssr Advanced at a tech services company with 5,001-10,000 employees
      Consultant
      Defect management helps us in QA with tracking. Rampup with this tool was straightforward.

      What is most valuable?

      Defect management is most valuable, since I am on the QA side. It's a very good tracker.

      How has it helped my organization?

      We have centralized all our agile process on it, so it's been our agile central during the project.

      What needs improvement?

      Based on my experience and the level of use, I think this tool fits everything we need.

      For how long have I used the solution?

      I’ve been using Agile Central for 1.5 years.

      What do I think about the stability of the solution?

      Sometimes the app freezes when creating either user stories or defects in Safari. The performance, in terms of response time when creating elements, is not as expected.

      What do I think about the scalability of the solution?

      I have not seen any scalability problems.

      How are customer service and technical support?

      I have never requested for support before.

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

      I had the chance to work with Atlassian JIRA in a prior project. When I arrived at my current project, it was the first time I worked with Agile Central and I am still using it.

      How was the initial setup?

      The rampup was very straightforward.

      What's my experience with pricing, setup cost, and licensing?

      Pricing and licensing it is not my responsibility. I am an end user only.

      Which other solutions did I evaluate?

      Choosing the tool was not my responsibility. However, I was using another tool and the rampup with this one was very straightforward.

      What other advice do I have?

      I would recommend using it without any doubt. I think it fits perfectly with the agile processes.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user598992
      Software Engineer at a tech services company with 501-1,000 employees
      Consultant
      Offers user story tracking and team status management. The UI can be slow to respond and difficult to navigate.

      What is most valuable?

      The valuable features are:

      • User story tracking and team status management, including capacity and burn down
      • Allows for the creation and scheduling of detailed user stories including attachments, assigned tasks, discussions, child stories, and revision history
      • Allows for the association of defects and test cases. (I have not used these features as we use HPE Quality Center for that purpose.)

      How has it helped my organization?

      Some of the improvements to my organization are as follows:

      • Helps my team organize our planning and testing activities.
      • Removes the need to have separate products for tracking the various ancillary records for our user stories.
      • Helped us to organize team effort and keep the team on track by providing a burndown chart and team status breakdown at the task level.
      • The ability to create child stories and track discussions throughout the lifetime of a user story and its children removes the need to maintain additional external documentation.

      What needs improvement?

      The following are areas for improvement:

      • The UI can be slow to respond at times and difficult to navigate initially.
      • The home dashboard can be very slow to load.
      • Individual user stories can be slow to respond when navigating from the Iteration Status page.
      • The tool can be slow to respond when estimates or statuses are updated.
      • The difficulty in navigation relates to the learning curve of the application.
      • There is a help page with a great deal of information about the various features and processes, which helps to demystify the application a bit. However, even that page can be cumbersome to navigate.

      What do I think about the stability of the solution?

      This application is rarely unstable. Scheduled maintenance is conducted with ample warning.

      What do I think about the scalability of the solution?

      There have not been any scalability issues.

      What other advice do I have?

      Good estimates give the burndown chart value. If your burndown looks bad, first look at your estimates for team capacity and user story/task effort estimates, and then look at the members of your team.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user592689
      Software Engineering Manager at a tech company with 10,001+ employees
      Vendor
      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.
      it_user602427
      Manager Global Tools at a healthcare company with 1,001-5,000 employees
      Vendor
      You can view the hierarchy of issues. It is not compliant with FDA regulations on electronic signatures.

      What is most valuable?

      Visibility of the backlog hierarchy and issue status are valuable features.

      I like the way you can view the hierarchy of issues, i.e., within the tool in a tree view, showing the traceability between epics, features, stories and tasks. This is something that is not available in the other tools that we currently use.

      What needs improvement?

      It is not compliant with the FDA regulations on electronic signatures (21 CFR part 11), which is required for regulated industries.

      We produce medical devices, which means we have to comply with the FDA regulations if we wish to sell in the U.S. One of these relates to being able to have electronic signatures within the tool, when we close or reject future defects.

      CA Agile Central does not have this functionality and when we asked them, they said they had no plans to implement this. As a result, we cannot use this tool for defect management. In fact, the tool has such few security features that you cannot stop anyone with an account from editing, deleting, or otherwise interfering with the records storied within it. As a result, we cannot use the information stored within it as part of our quality system.

      For how long have I used the solution?

      I have used this solution for six months.

      What do I think about the stability of the solution?

      I have not encountered any stability issues.

      What do I think about the scalability of the solution?

      I have not encountered any scalability issues.

      How are customer service and technical support?

      I have not used it personally.

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

      We are using Atlassian JIRA. We have not switched tools but currently we use both solutions in parallel, due to the FDA regulation issues.

      What's my experience with pricing, setup cost, and licensing?

      It is very expensive; currently it is the single biggest tool cost that we have.

      What other advice do I have?

      Make sure it meets your needs before rolling it out. Don’t buy it just because it is recommended as the “safe” tool.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user597612
      Agile (Jira/Confluence) Tools Specialist at a financial services firm with 10,001+ employees
      Vendor
      It can integrate with HPE Quality Center. Excel imports and the ability to modify workflows are two important improvements I would like to see.

      What is most valuable?

      The ability to integrate to the HPE Quality Center is a powerful feature although we haven't used it yet and won't be doing it.

      The test case organiser is another useful utility which could help users still using waterfall methods of working if they intend to use it for a while. This functionality is not inbuilt but was showcased by one of their support guys from CA who are happy to share it with customers.

      Another notable feature is reporting at Portfolio level, and an organised business area which is set up from scratch with this tool can benefit from this feature. A senior manager will have more visibility as to what is happening in various projects and teams.

      How has it helped my organization?

      It needs to become more mature for large organisations with better integration required to DevOps. 

      It has the capacity to let you integrate if you have in-house development capability but not out of the box. 

      Solutions are available to integrate it with development tools or Atlassian tools but they are expensive.

      What needs improvement?

      I believe Excel imports and the ability to modify workflows are two important improvements which will enhance its competitiveness in the market. 

      I believe the feature to use Excel to import issues, tasks, test cases or any other relevant data will be a useful functionality which is missing and many teams are willing to have such a feature. Also, the ability to modify workflows to support custom requirements will increase acceptability of the tool. Currently it has a slightly rigid response to users wanting to tailor the project for their need.

      For how long have I used the solution?

      I have used this product for less than a year.

      What was my experience with deployment of the solution?

      It's a SaaS solution so no involvement in building it up. 

      For a large organisation, whether a bank or retail outlet, it has some challenges to integrate with the company's authentication methods. 

      Data integrity holds a challenge as data needs to be made secure which takes effort to achieve.

      What do I think about the stability of the solution?

      For a large organisation, whether a bank or retail outlet, it has some challenges to integrate with the company's authentication methods. 

      Data integrity holds a challenge as data needs to be made secure which takes effort to achieve.

      How is customer service and technical support?

      Customer service is 7/10.

      What was our ROI?

      I don't know the price but it's certainly cheaper than others.

      Which other solutions did I evaluate?

      Atlassian JIRA and HPE Quality Center: They are market-leading tools and still quite competitive with more features to support both waterfall and agile models.

      What other advice do I have?

      I would suggest to do a comparison chart for your organisation's needs and look at least 5 years ahead for the functionality and budget you are looking for in a tool. Not only the tool cost is relevant but also the resources to maintain it. For a very small organisation, I could certainly recommend a SaaS solution but for an organisation with more than 500 concurrent users, a standalone solution would be more apt, in my opinion.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user597591
      Project Manager And Disaster Recovery Coordinator at a financial services firm with 501-1,000 employees
      Vendor
      It has enhanced our ability to understand the work being done, especially on projects you may not be directly related to.

      What is most valuable?

      The ability to plan and assign work. Our project/product teams use this to effectively plan sprints and assign and track work assignments. It has greatly enhanced our ability to understand the work being done, especially on projects you may not be directly related to. By having all our teams use the same tool, we have better communication and coordination.

      How has it helped my organization?

      It greatly helped our adoption of agile project management techniques. More projects are completed on time.

      What needs improvement?

      Portfolio management and reporting may be the weakest areas.

      For how long have I used the solution?

      I’ve been using Agile Central for 12 months.

      What do I think about the stability of the solution?

      We lose connectivity at times when the site has issues. This is a hosted solution.

      How are customer service and technical support?

      Technical support is good.

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

      We used a Bamboo Solutions product that interfaced with SharePoint.

      How was the initial setup?

      Initial setup was relatively simple. In order to match our department organization, there were significant discussions. But the Rally representative helped set it up with us at no cost. It was Rally when we purchased. We had to develop a custom report from the information.

      Which other solutions did I evaluate?

      We did evaluate alternative solutions.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user597618
      Senior Member Of Technical Staff at a tech vendor with 501-1,000 employees
      Vendor
      With the portfolio management feature, we were able to understand our capacity and visually understand initiatives in-flight.

      What is most valuable?

      Portfolio management is a valuable feature.

      How has it helped my organization?

      It is 100% designed 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 our senior executives in order to be able to choose which projects we did and to check 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 it up and running quickly. They could have more controls around user types and as to what permissions they have.

      For how long have I used the solution?

      I have used this solution for 18 months.

      What do I think about the stability of the solution?

      We did not encounter any stability/scalability/deployment issues; 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 assume this is the same for any system whether cloud-based or self-hosted.

      How are customer service and technical support?

      I would give the technical support a 6/10 rating. There weren't too many problems, so I didn't have to use them much.

      However, if the issue was specific to your data, then they couldn't really help easily. They had to get permission to duplicate your 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 setup was simple as it only does agile.

      What about the implementation team?

      We implemented this product in-house. The adoption wasn't the hard part. It was the overall agile transformation that required the effort which was a culture/process thing.

      What's my experience with pricing, setup cost, and licensing?

      I am not certain but we couldn't work without it.

      What other advice do I have?

      You have to adopt agile and be true to it. This is an agile solution 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.
      it_user591864
      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: IT Central Station 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.
      it_user592353
      Strategic Analyst at a government with 1,001-5,000 employees
      Vendor
      With the Kanban board, you don't need to run projects with a scrum approach.

      What is most valuable?

      The Kanban board is probably the most useful feature. It is very customizable and is great for somebody who doesn’t need to run the project with a scrum approach. The second most important feature is the overall ability to customize almost all of the solution’s features and work products such as user stories, defects, and features.

      How has it helped my organization?

      The product helped engage the business product owners by increasing both their view into the development cycle and their responsibility to assist in setting up work priorities.

      What needs improvement?

      The weakest part of this solution is its primitive report generator.

      The report generator is very simplistic with a limited capability to filter, sort and group, and the designer is not WYSIWYG. The product would benefit from a more capable browser and a more compatible report builder.

      It needs a UI that has a Crystal Reports-like design and WYSIWYG capability. Right now, it is an early 80s throwback.

      What do I think about the stability of the solution?

      We have not had many stability issues. It is a stable product, but in the past, CA has fixed some server-side issues or implemented an “improvement” without any patch notes. That is usually just frustrating but one time, an “enhancement” broke our link to TFS. It took us two days to re-enter all the users.

      What do I think about the scalability of the solution?

      We have no scalability issues. We have 185 users. However, because we are a cloud product, we are at the mercy of the internet routers and traffic.

      How are customer service and technical support?

      Technical support is good once you get their attention. What is critical to you might not be critical to them. As an example, we had a broken TFS connector. It took about six hours for them to understand the problem, and that they were the ones who broke it. Once that happened, they were very helpful.

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

      We used Microsoft Project. At that time, it was very weak with agile projects. Prior to purchasing this solution, we created a vendor grading scorecard with the features that were important to my company. We started evaluating six products. We then eliminated three, re-compared them, and settled on this solution.

      How was the initial setup?

      Since we bought the cloud option, there was no specific setup. There was, however, lots of customization that we have done since 2012. It is straightforward once you are familiar with the product.

      We also purchased five days of CA Agile Central on-site training. It broke down like this: one day for developers, two days for project managers/scrum managers, a half day for product owners, and a half day for administrators.

      What's my experience with pricing, setup cost, and licensing?

      CA seems willing to give deep discounts when you have 100+ licenses.

      Which other solutions did I evaluate?

      We evaluated five other options. They have changed so much since we evaluated them in 2012, so it wouldn’t be fair to name them.

      What other advice do I have?

      Make sure you have adopted an agile methodology on a few small projects first and then work with IT and business colleagues to accept that methodology. We did that before we looked for a tool. That makes the purchase, acceptance, and customization of this tool much easier.

      Disclosure: IT Central Station 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.
      ITCS user
      Software QA Automation Analyst at a tech services company with 501-1,000 employees
      Consultant
      We can create and schedule detailed user stories that include attachments, assigned tasks, discussion, child stories, and revision history. The home dashboard can be very slow to load.

      What is most valuable?

      The most valuable features are user story tracking and team status management, including capacity and burndown. Allows for creation and scheduling of detailed user stories including attachments, assigned tasks, discussion, child stories, and revision history. Also allows association of defects and test cases, though I have not used these features as we use HP Quality Center for that purpose.

      How has it helped my organization?

      This product has helped to organize team effort and keep the team on track by providing a burndown chart and team status breakdown at the task level. Additionally, the ability to create child stories and track discussions throughout the lifetime of a user story, and its children, removes the need to maintain additional external documentation.

      What needs improvement?

      The UI can be slow to respond at times and difficult to navigate initially.

      The home dashboard can be very slow to load. Individual user stories can be slow to respond when navigating from the Iteration Status page, as well as being slow to respond when estimates or status are updated.

      The difficulty in navigation relates to the learning curve of the application. There is a help page with a great deal of information about the various features and processes which does help demystify the application a bit. But even that page can be cumbersome to navigate.

      For how long have I used the solution?

      I have used Agile Central for 4 years.

      What do I think about the stability of the solution?

      This application is rarely unstable. Scheduled maintenance is conducted with ample warning.

      What do I think about the scalability of the solution?

      We have not had issues with scalability.

      How is customer service and technical support?

      I have not contacted technical support.

      How was the initial setup?

      I was not involved in the initial setup.

      What's my experience with pricing, setup cost, and licensing?

      I am not involved in the licensing of this tool.

      What other advice do I have?

      Good estimates give the burndown chart its value. If your burndown looks bad, first look at your estimates for team capacity and user story/task effort estimates. Then look at the members of your team.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user591861
      Consultant at a recruiting/HR firm with 10,001+ employees
      Real User
      Tracks progress and activities, and facilitates interaction.

      What is most valuable?

      The valuable features are: Tracking progress and other parameters. Allowing a better overall picture of activities. Facilitating the interaction between team members and teams.

      How has it helped my organization?

      The solution now offers visibility on each activity and its status.

      What needs improvement?

      I would like to see team masters have an easier way of managing the tasks/stories for their team members when creating default tasks in advance.

      For how long have I used the solution?

      We have been using this solution for a year and a half.

      What do I think about the stability of the solution?

      We did not encounter any issues with stability.

      What do I think about the scalability of the solution?

      We did not encounter any issues with…

      What is most valuable?

      The valuable features are:

      • Tracking progress and other parameters.
      • Allowing a better overall picture of activities.
      • Facilitating the interaction between team members and teams.

      How has it helped my organization?

      The solution now offers visibility on each activity and its status.

      What needs improvement?

      I would like to see team masters have an easier way of managing the tasks/stories for their team members when creating default tasks in advance.

      For how long have I used the solution?

      We have been using this solution for a year and a half.

      What do I think about the stability of the solution?

      We did not encounter any issues with stability.

      What do I think about the scalability of the solution?

      We did not encounter any issues with scalability.

      What other advice do I have?

      In order to improve the organization of your work, make sure you put real info/data into the product.

      Disclosure: IT Central Station 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.
      it_user591855
      Senior QA Analyst at a tech services company with 501-1,000 employees
      Consultant
      CA Agile Central works ALMOST how you would expect it to.

      What is most valuable?

      Defect tracking is the one feature that behaves most like I would expect and I have found a good way get it to work for me.

      The features I use the most are the Test Planning, Test Set, Defect, and Defect Suite functionality. The Project Manager has stated multiple times that the reporting features of the User Stories & Sprint Planning work well for him. Though, like every other piece of the app, there are things that either do not make sense or have to be worked around to utilize the system as needed.

      The Defect Tracking of CA Agile Central functions well enough with some severe limitations. I believe the intention is for you to put Defects in Defect Suites and Defect Suites in Iterations. You can put Defects in User Stories, but only one User Story at a time. So, if the defect crops back in, you either create a new defect or pull the defect from the previous sprint's User Story, thus changing history.

      If you put them in Defect Suites you can add the same Defect to multiple Defect Suites in different Sprints. However, this also comes with some weirdness in removing a Defect from a Suite. You can't pull the Defect from the Suite directly, you have to go to the Defect and remove the Suite from there.

      There is a Notes section for each of the Defects. Unlike JIRA there is no way to keep straight who made what comment when in the notes section. You have to manually add your name and date and time to the notes field making it so that if you have a back and forth about the root cause of the defect there is no ease way to facilitate this on the defect itself.

      If one defect is causing failures in multiple Test Cases you cannot tag multiple Test Cases in the Defect. You either have to create multiple defects or note in the result that it failed because of the defect.

      Test Sets & Test Plans, again, ALMOST function how you would expect. You can fairly easily lay out Test Cases in a Test Plan, unless you want to move a Test Case from one Test Folder to another, then you have to do so from within the Test Case rather than on the Test Plan page. You can move an entire nested Test Folder from one Test Folder to another. Deleting of a Test Folder orphans all the Test Cases making you have to hunt them down manually for deletion.

      Test Sets are the method by which it appears you're supposed to keep execution results separate. Unfortunately, there is no way on the Test Plan to choose a Test Set to see the results. Test Plan only reports the latest results with no easy way to view historic execution results by Test Set. You also cannot view a Test Set's results independently. Further, adding Test Cases to a Test Set requires looking them up by Test Folder from the Test Plan. If the Test Folder has nested Folders, you can't search for the Parent Folder and add all Test Cases in the child folders. You can only create Test Sets in the Iteration, not in the Quality > Test Suites and then assign to an Iteration. Yes, It's called a Test Set and a Test Suite in the application.

      How has it helped my organization?

      I use this at a customer’s site. I cannot say for certain it is better than nothing, but I do not know what they were using prior.

      Generally speaking, I can usually think of a product that functions better than CA Agile Central for the features that are utilized the most.

      What needs improvement?

      I have yet to see a section of CA Agile Central that could not benefit from improvement. As I tell people, it ALMOST behaves how you would expect. There are so many twitchy bits that require workaround for the business process to function. It’s ridiculous and feels almost like it gets in the way more than it helps.

      For example, these problems come up when re-executing test cases. I have found no way to easily set up another testing cycle that reports the results independently and I’ve LOOKED. There is no way to assign a test case to multiple stories or a defect to multiple test cases. Associating a defect with a defect suite is easy. Removing it is hard; exceedingly so. Creating test cases in a test folder on the test plan page is easy. Moving those test cases around is exceedingly difficult. I could go on and on and on about how this product has let me down.

      For how long have I used the solution?

      I have used CA Agile Central for one year.

      What do I think about the stability of the solution?

      Stability hasn’t been TOO bad. There are occasions that I have had to close my browser and start a session over. But what do you expect when using Adobe Flash instead of something more modern.

      What do I think about the scalability of the solution?

      Opening new browser windows (middle-click) takes FOR-EV-ER, relatively speaking. While it is MUCH faster to just click a link in a given instance/tab, the general user behavior is to open new tabs and that takes WAY too long.

      How are customer service and technical support?

      I have not had to utilize technical support.

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

      I was not given the option to use a different solution, as this is the solution my client utilizes.

      TestRail is my hands-down favorite test case DB to work with. It has every feature a tester needs to easily create and design test suites, add defects, and retest with multiple configurations. CA could learn a LOT from TestRail about how to manage test cases properly.

      What other advice do I have?

      Choose a different product for your test case needs, and explore other options of managing of your agile processes, such as TFS.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558369
      Systems Annalyst Two at a insurance company with 501-1,000 employees
      Vendor
      It is flexible enough to use for anything within the development lifecycle. Making some features more obvious would make them more useful.

      What is most valuable?

      We needed something that we could collaborate with and was easy to use, and easy to access for business analysts.

      We are trying to be agile, but we still use waterfall for a lot of things. We are not working agile as much as we should. We don’t adapt as quickly as we should. The tools are all there; but we are not implementing it correctly and not enforcing the rules enough.

      The most valuable features of CA Agile Central for us are:

      • It provides organization.
      • It's a good collaboration spacing unit.
      • It does a really good job of tracking overall statuses.
      • There's a ton of flexibility. I can use it for anything I can think of within the development lifecycle. So that's really nice.
      • It is user friendly.
      • It really helps us with tracking progress, so we can see where we’re heading.

      What needs improvement?

      It's tough to think of areas for improvement. I mean, I think it's all there. Making some of the features more obvious would probably make them more useful. Right now, there's a lot of power and flexibility; but it's not always obvious. There should be something in the way of best practices and suggestions, and to know what makes logical sense. You really need to have a good plan for it. I've seen how it can be mishandled and not implemented strongly to where it becomes more of a hindrance than a value.

      What do I think about the stability of the solution?

      For the most part, the stability is quite good. We haven't had a lot of issues. There are little tweaks and quirks, here and there. I think a lot of that is because the tool is so flexible and powerful; and it can do a lot of different things if you want it to. You can kind of corner yourself, where you’re doing something not really modular. It is not really a stability problem, but in some ways, you could have too much content to the point that it drowns out the rationale for using the system.

      What do I think about the scalability of the solution?

      The scalability is incredible. It's not always straightforward and easy. It’s varied, but there is a lot of overhead in getting there. There is a lot of thought process that you need to put into it. People were already pressed for the work they already have. Asking them to set up entire systems to integrate and be flexible is quite a change.

      How is customer service and technical support?

      I can’t think of any big enough issues, so we haven’t used a lot of technical support. I did contact them with a small issue that went away and then came back. I didn't really have a lot of direction on that. It was a flow issue.

      What other advice do I have?

      Have a strong plan and clear requirements in advance for what you want to get out of the tool. You need to have strong leadership on the design: how you're going to use it, how you're going to set it up, what you expect out of it, what you might be integrated with, what you're angle is with the tool. If you just keep buying tools, you're not going to use them in the end; and it's just going to be a waste of money and a headache for people down the line using it.

      The most important criteria when selecting a vendor depends on which group gets to select the vendor, unfortunately. Price is always something, especially if finance is making the decision. When it comes to IT, I like flexibility and use of the system. There has to be more gain than effort. If it's too hard to implement for too little gain, then it's not worth your time. You're really looking for balance across the board. The cost has be there. There has to be value to it; so return on investment, the ROI, ends up being the big deciding factor in the end for any software company.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558609
      Software Release Manager at a financial services firm with 501-1,000 employees
      Vendor
      The reporting is valuable to us for controlling releases and milestones.

      What is most valuable?

      A lot of the reporting is very valuable to us. We really need to control certain releases and milestones, and so on. Being able to report and get statistics on all of that stuff is one of the features we really like, especially now that they're expanding that as well. We like that.

      How has it helped my organization?

      Honestly, it keeps us more organized. We have a lot of products and we ship them pretty fast. CA Agile Central is great for us because we can categorize all these different things. It really gives our top-level leadership visibility into what we're doing so that they don't pound down our door every two seconds. They can actually go into CA Agile Central and figure things out for themselves. They can make better decisions without really needing us.

      What needs improvement?

      I use it a lot. I don’t really have any complaints. There are a lot of alternatives out there. They are also useful, but I have no complaints with CA Agile Central or with CA in general. I don't find myself saying, “I wish it did this,” or ”It's really killing me here”. It has been a good experience.

      As a release manager, what they’re coming out with now in terms of release automation is going to be very valuable to me. I think that with CI (continuous integration), as much as it is expanding and taking over most software shops anyway, I think that's the way to go. I think they're doing it right. As a release manager, I'm happy. CA is coming out with a lot of CI-type things, which is good.

      What do I think about the stability of the solution?

      It is stable. There are no issues there.

      What do I think about the scalability of the solution?

      It is scalable. There are no issues there.

      How are customer service and technical support?

      Customer Service:

      The customer support at CA is good; however, we haven’t had to use it, which is good. It's always there if we need it. That's also good.

      Technical Support:

      I don’t believe we’ve needed technical support. It has been pretty stable. It fits our needs for what we need so far.

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

      My company has been using CA Agile Central for as long as I’ve been there.

      Which other solutions did I evaluate?

      I've been at other companies where they're using different tools, like JIRA and stuff like that; but CA Agile Central is fine. At one of those companies, we weren’t using JIRA all the time. It was really too convoluted for what we needed.; so we didn’t use them. Sometimes you needed to dig for certain things that were not necessarily laid out flat like CA Agile Central is. Even though, in JIRA, you can kind of organize them in different ways; but only if you use them. Like I said, CA Agile Central fits our needs pretty well.

      What other advice do I have?

      Our top reason for selecting an agile platform was needing to ship as fast as possible. Waterfall is good for new products coming out, but we have a lot of long-standing applications that have been out on the market for awhile. Getting releases together and shipping them as fast as possible is what we needed. It was kind of a no-brainer for us.

      I would say our agile maturity is intermediate. We're still learning. There's so much you can do. Like I said, we are even coming out with new products, so we have to use waterfall sometimes; but we're still learning about it. We're trying to integrate as much as possible and tailor it to our company.

      When we evaluate vendors, are most important criteria are the customer support, scalability, and availability. We've had problems in the past with some other vendors whose products’ availability was not what we needed. They would go down quite a bit, more times than you would think, honestly. That's a big deal for us, especially whenever we put so much into it. If a system goes down, the entire development department basically stops working. That's a big thing for us, especially as we keep putting more and more into CA Agile Central.

      If a colleague of mine was evaluating this solution, I would advise them to keep it small. Simple is better.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558174
      Senior Project Manager at a aerospace/defense firm with 1,001-5,000 employees
      Vendor
      We are able to communicate without everybody having to be in the same room.

      What is most valuable?

      Most valuable to us is being able to communicate without everybody having to be in the same room. Also the ability to capture information and distribute it to team members. We have people overseas or people working from home or in a different office building and they can all communicate via Agile Central.

      I think it is an excellent tool for tracking agile scrum activities. It's one of the best tools on the market, if not the best.

      How has it helped my organization?

      Primarily, it has given us a more structured approach than doing some kind of scrum using white boards and other manual methods. It's a very helpful tool. The push for Agile Central came when we asked the company to go agile and do scrum. This required us to go ahead and purchase a tool to unify us across the company.

      My personal agile maturity is about medium. Company-wide, some facets are medium to high and others are just starting. Our scrum masters also use it for coaching. Some of the best practices we use are keeping the tool updates timely and making sure stories are well defined and broken down in the right unit of work.

      What needs improvement?

      I would like to see greater ability to manage common teams that are working across projects and how that common team has tasks to do in both projects or in multiple other projects. I want to see more common services.

      The project might require common services, but if I'm a common services team and I have tasks in all of these other projects, it’s better to manage the common services team itself and their tasks; because they have tasks in multiple other Agile Central projects.

      What do I think about the stability of the solution?

      As far as I can tell, it has good stability.

      What do I think about the scalability of the solution?

      I can't comment about scalability.

      How is customer service and technical support?

      I have not used technical support personally. I haven't had to, so that's good.

      How was the initial setup?

      I was not involved in the initial setup.

      Which other solutions did I evaluate?

      I know of some people that were trying to use JIRA, but I don't believe that had near the capabilities that this does.

      What other advice do I have?

      I would advise potential users to get in touch with CA and have a representative sit down and show them the tool and how they can use it.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      ITCS user
      Software Engineer at a engineering company with 10,001+ employees
      Vendor
      Helps to justify our release date based on the defects we have. The API could be improved.

      What is most valuable?

      We're using CA Agile Central to track project development status, including the whole process, starting from the initial plan, followed by testing, development, and bug tracking.

      How has it helped my organization?

      From my personal viewpoint, it helps make sure everything is on track. I'd say our agile maturity is mid-level.

      What do I think about the scalability of the solution?

      I think scalability is good.

      How was the initial setup?

      I think initial setup was straightforward. The documentation was very clear.

      What is most valuable?

      We're using CA Agile Central to track project development status, including the whole process, starting from the initial plan, followed by testing, development, and bug tracking.

      How has it helped my organization?

      From my personal viewpoint, it helps make sure everything is on track.

      I'd say our agile maturity is mid-level.

      What do I think about the scalability of the solution?

      I think scalability is good.

      How was the initial setup?

      I think initial setup was straightforward. The documentation was very clear.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558213
      Associate Project Manager at a healthcare company with 1,001-5,000 employees
      Real User
      Transparency into work by teams enables identifying differences and aligning our processes.

      What is most valuable?

      The most valuable feature of the solution is that we are able to identify individual teams, and those teams can then break down their work, and watch it flow through their process. The benefit is that it provides transparency into the work that teams are doing.

      How has it helped my organization?

      It has brought a lot of light to the differences in the way our teams process the work through. They may be doing the same set of work, but Team A is doing it completely differently from team B. We've identified some of those differences; and we're now starting to align the process.

      What needs improvement?

      Our biggest struggle right now is that we're a SaaS customer, and that we don't have access to the database behind the scenes. So we're being asked by our Scrum masters and teams to provide data and reporting that we're not able to get to using the tool.

      What do I think about the stability of the solution?

      The stability has been very good. Although, this year and last year, we did notice problems on Monday, just as CA World started. I think it's very coincidental. It was just kind of odd.

      What do I think about the scalability of the solution?

      I think the scalability is there for our organization. We are not in a position to take advantage of any of that yet.

      How are customer service and technical support?

      There have been a couple of cases where we've asked questions, and the answer has been, "Here, go read this site." That's been a little frustrating; but, for the most part, all of the cases have been resolved, timely, and with good results.

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

      We were previously using a different solution, and it was not suiting our needs. We had teams circumventing the process and using spreadsheets, or wall-based paper models, which is good; but we wanted a way to report and review all the work that was being done. So we went with CA Agile Central when we converted. It's been much better and there has been a lot more adaption of this tool than the previous one.

      How was the initial setup?

      It was very straightforward. We didn't have any trouble rolling it out into our organization. The issues we had were internal in adaption.

      Which other solutions did I evaluate?

      We did a side-by-side demo and evaluation with two vendors. At that time, it was CA Agile Central and Version One. We chose CA Agile Central over VersionOne because of the reporting features and ease of use.

      The only solutions I've experienced are CA Agile Central and VersionOne, and obviously, we chose CA Agile Central. There was also Serena Agile Planner, which was not ideal. Of those three options, I would way that CA Agile Central is excellent. Among those three, we were very happy with it. We are able to incorporate it into our environment. That is the most important thing for us. We're pretty rigid in the way we do things.

      What other advice do I have?

      My advice is that they need to understand their environment and what they need. Then look for that in the tools that are provided. CA Agile Central was very flexible. You can configure it without customizing it. That was one of the things we really liked.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558177
      IT Manager at a transportation company with 1,001-5,000 employees
      Vendor
      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.
      it_user558051
      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.
      it_user558279
      Director, Program Management at a computer software company with 10,001+ employees
      Real User
      From a backend environment standpoint, it can scale for the whole business.

      What is most valuable?

      There are a couple things that our company found really good. One is that it’s scalable, and a lot of the other products on the market for us don't scale. We have close to 20,000 people using Agile Central. So that was one of the keys. Within the company developers, they all have their preferences. So some like JIRA, while some like Agile Central. But from a backend environment standpoint, Agile Central can actually scale for the whole business.

      How has it helped my organization?

      Agile Central helps in terms of Agile management, especially with our scrum teams. It's designed to be used from an Agile standpoint, so I think the teams that have struggled with it are the ones that aren't really set up for Agile. Agile Central is really founded as an Agile tool, so if you're not doing Agile, the tool doesn't work all that well for you.

      Our company is large and we've got a very wide gamut of Agile maturity. We have some teams that are very expert in Agile and we have others that are still Waterfall. It's a 100+ plus year old company, so it runs the full gamut. Personally, I have been using Agile for a couple of years, so I'd say I'm pretty familiar with it at this point.

      What needs improvement?

      We've been asking for a couple of things. A big one for us has been on the administrative side. Again, I'm coming from a very large company so these are the things that are, at that scale, very important to us, such as access. How do we get access to people? How do you move a large number of people?

      The other big one that we've been requesting for years is the ability to move people between workspaces. For us, that's really important. Every time we've had to do this, we have to get technical support involved and it's just a big pain in the butt. Within Agile Central, each workspace is very independent and one workspace can't talk to another workspace.

      We have multiple workspaces set up and when a team wants move from one to the other it's very difficult to do. For instance, with a big organization you're always going to have organizational changes. So you may have set the things up perfectly when you first set it up, but things change. Now when they go and change, since we can't move workspaces easily, the new teams that are together can't collaborate because they're in different workspaces. There's no easy, functional way of doing it.

      I also think the UI could use some improvement. I believe they're working on it. Also, it's not the most developer-friendly tool. So while management tends to like it, I don't know if developers are huge fans of it, at least in my business, from what I've seen.

      What do I think about the stability of the solution?

      I think stability has been fairly good. I don't know whether to attribute the issues that we've had to Agile Central or to our own network. And we have had issues, but they've been pretty quick to respond and try to come to the root cause of what's going on.

      What do I think about the scalability of the solution?

      We've had some scalability issues but, to be honest, because it's a SaaS product, I'm not sure if it's a function of our network or Agile Central. Sometimes it's difficult to tell, because we've got a lot of internal networking that we're doing in terms of security, etc., that slows things down. So when we have had complaints about it, a lot of times it may be us that's at fault and not so much Agile Central. But, an important factor in choosing Agile Central was scalability.

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

      We actually offer both JIRA and Agile Central within the company. So we try to somewhat make it a user choice as well. What we typically recommend is that if it's a very small project and it's a quick turnaround, JIRA's probably your best bet. If you have something longer term, Agile Central is probably going to be an easier tool for you to use.

      How was the initial setup?

      I wasn’t involved in the initial setup.

      Which other solutions did I evaluate?

      We didn't evaluate anything other than JIRA and Agile Central.

      What other advice do I have?

      I think you have to think through how you're going to organize, especially if you have a large company. We've struggled with the structure of our teams and the way they're set up. So that's something you need to consider. And I don't know if they've done a great job of it. They actually call teams “projects”, which is a bit of a naming issue.

      You definitely need to have some foresight when you set it up in terms of how that's going to work. You also need to think about how you're going to do workspaces, because there's no functionality there to change it once it's set up. You've got to get that right from the get-go or you're going to have a lot of trouble going forward.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558012
      Sea System En at Hauwei
      Real User
      It's easy to use, it integrates with our other solutions, and it scales well.

      What is most valuable?

      The best feature for our company is that it's easy to use, and it integrates with our other solutions, such as the code warehouse, the test solution, and the deploy solution. We wanted an ALM product that was easily integrated, because we have 170,000 users in my company. We need a strong solution to support us. We must have:

      • Ease-of-use
      • Easy to integrate with other solutions
      • Good stability

      What needs improvement?

      I don’t know this product well enough yet to offer suggestions for new features. I recently went to a conference to learn about CA Agent Manager as well.

      See below regarding stability.

      What do I think about the stability of the solution?

      Stability of the product is not good. It is critical for us to make the solution stable.

      What do I think about the scalability of the solution?

      CA Agile Central scales very well. We have 170,000 users.

      How is customer service and technical support?

      We have not used technical support. We bought the product and were ready to work with it.

      How was the initial setup?

      Initial setup was easy for me. A consultant came to our company to sit with our people.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558066
      Safe Agilist Scrum Master at a comms service provider with 1,001-5,000 employees
      Vendor
      Data extraction provides metrics with an accurate picture of team progress and time-to-release changes.

      What is most valuable?

      The ability to extract data to provide feature and release metrics for our executives and our customer stakeholders is very important. It provides reports on the cycle time from the time that feature requirements are initially defined to when they are available for release. Release in this case does not mean production, because it does not include that capability.

      For me, it's important that it supports both an agile scrum and a Kanban implementation. I've had responsibilities for operations in the past in which people were trying to force the operations team into a scrum implementation or methodology, that doesn't work in an interrupt-driven world that you have sometimes have in production when you have to deal with production issues. 
       

      How has it helped my organization?

      • By using this extracted data, it provides a real picture, instead of a perceived picture, of the amount of work the team is doing, the time it's taking to get new changes out, ready to put into a user acceptance test area, and production, which is really where our problems are. It's not solving those problems right now; but it is providing data that I use to present data on the deployment delays. For example, we can see that we’re finished at point A, but we're not actually deploying it to a production environment until point B, which is sometimes only three months later. So there is a delay in getting the features that customers want to production. This is because we lack a DevOps culture. CA Agile Central is giving me real data to show that for many features. 
      • Our company implemented the scaled agile framework. I believe they've created a heavyweight bureaucratic implementation, and I think they have some work to do there. It’s putting wear and tear on our team. We just did a total pivot. With scaled agile, we work in three-month program increments. I'm actually used to planning out that long, but we had a business situation that came up in which our whole department did an immediate pivot; so we are pretty agile. I just think that we have some work to do on the wear and tear on the team.
      • I think I have a great handle on agile methodology, but I haven't done any portfolio management using agile tools. 
      • Our team’s agile knowledge is intermediate, but they're learning; and they're learning on their own now. They actually understand their limitations. When I started, they had been doing the whole methodology for a couple of years, but they didn't realize where they had opportunity to grow, which is one of the reasons why I was brought in. Before, they just needed to be directed.
      • For people outside my team, we created a scrum master guild, and we use that all the time. One of our best practices is that we created agreements across all of our teams regarding how those specific teams work. Those agreements are not the same on every team, which I think is exactly the right way to go. It is definitely a positive change for the organization now that each team can provide information transparently to executive management. Everybody seems to think that’s a good thing.
      • We also do a retrospective across our teams, which I think is very open. That's pretty refreshing to see.

      What needs improvement?

      • I would like them to give me back the fields I used to have. We lost the release field because they mentored our scaled agile framework trainer to actually use the release field as what I would call a program increment.
      • We're releasing every two weeks, so it's pretty hard. They also should put a product field in there. We have work areas. Our work area is our team, it's not our product. So my team actually supports four different products. I'm doing name mangling that I then have to write code around to understand how to get metrics out. That is challenging.
      • The other thing is that I think I can pull out data from the release, but we're not using all of the CA Agile Central projects. For example, we're not using the testing part of it. We do use the defects. I don't know how I'm going to integrate the testing tool that was selected by the test organization. I don't know how I'm going to integrate all of that. They might have plug-ins for that. I don't know.
      • The only thing I can think about is finishing the lifecycle. There are tools in there, and I don't know how I can close the loop.

      For how long have I used the solution?

      I have been using Agile Central for 10 years. At my last company, I had access to just go in and look at everything, but I don't have admin access at my current company.

      What do I think about the stability of the solution?

      Our product is doing very well. We had one production issue in the last three months, which is pretty good considering how large our customers base is.

      We launched our product in April or May. We had two or three issues in the first month that I think had to do with the whole DevOps theme; and how it was configured and set up. We are working really hard on the DevOps side, but we have some work ahead of us. We’re not there yet. But we haven’t had any real software problems.

      What do I think about the scalability of the solution?

      We're able to scale as much as we need right now.

      How was the initial setup?

      The initial setup was complex. We have a lot of different internal and external integrations.

      Which other solutions did I evaluate?

      I wasn’t there when they selected it. However, I will say that having had the scaled agile framework, I'm a little disappointed at what it looks like in comparison to something like AgileCraft.

      I think that they have some work to do on the scaled agile framework side. I don't know if they're doing it because I'm not in those discussions. 

      I haven't really looked at any other vendors. Someone just sent me a link to AgileCraft. That's the only reason I mentioned them, and I don't know if it works. I just saw the “marchitecture” stuff.

      What other advice do I have?

      I fully support CA Agile Central as a product. I would guess that I also support their scaled agile framework Implementation of it, if you go in with your eyes open and have honest discussions with the CA Agile Central implementers.

      We do technical support and even more than that. We do what I call operational monitoring. We have an operations team on one of our products; on the other product, we don't. We're the operations team.

      We actually just instituted a new process that we're implementing. We go out and check each of our environments every day. We are always deploying to QA, and always have something in our user acceptance testing area and in our production area. We look at all three of those environments. Any problems we see, we immediately investigate.

      I think that's how we've been able to prevent some of the problems we were having. At least the development team is doing that. The operations team has their own methodology.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558054
      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.
      it_user558417
      Information Technology Program Manager at a insurance company with 1,001-5,000 employees
      Real User
      Gives us a lot of visibility as to what features are getting released and when.

      What is most valuable?

      For us, the most valuable feature was writing all the stories. We found features such as figuring out what stories are going to get into which sprint and organizing the backlog and dependencies, to be useful to us.

      How has it helped my organization?

      In terms of improving the organization functions, it gives us a lot of visibility as to what features are getting released and when. It also helps us to track across the organization in a much better fashion. In my opinion, visibility is the biggest benefit that we have received from implementing CA Agile Central.

      What needs improvement?

      We would probably like to see a more robust dependency management system.

      What do I think about the stability of the solution?

      We have not experienced any issues. So far, things have been working fine for us.

      What do I think about the scalability of the solution?

      We have started a little slow. There are just a couple of teams that are using CA Agile Central, so we've not really scaled it up for multiple teams across the organization. However, within our group there are 3 or 4 teams that are using CA Agile Central right now.

      How are customer service and technical support?

      We've not used them so far. Thankfully, we didn’t need to use them.

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

      We were not using any other solution prior to this. Since our organization was moving to agile, we evaluated a few products and CA Agile Central seemed to be a good option that would fit all of our needs; so that's how we decided to go with it.

      How was the initial setup?

      Not me personally but there was somebody in my team that was involved in the initial setup. We did not encounter a lot of issues or challenges.

      Of course, we had to pull some experts from CA as well just to get their ideas on how we're supposed to set it up, how things work and what are the best practices to follow and so on.

      Other than that, the first couple of iterations/sprints we had to learn and tweak a little bit as part of retrospectives. Otherwise, it has been okay.

      Which other solutions did I evaluate?

      Initially, we looked at a couple of vendors, namely Pivotal Tracker.

      What other advice do I have?

      You need to clearly know what you want or how you want to implement and use the product. Once you have clarity then you can figure out how you want to setup the solution and go from there.

      For us, the user interface was the most important criteria while choosing a vendor. We found it to be more intuitive than the others. We also felt that it can probably scale up to the needs of what we have within the organization, in terms of integrating with the rest of the ecosystem.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558003
      Application Developer at a healthcare company with 10,001+ employees
      Vendor
      Flexible way to document Agile requirements. Collaborative approach to log, store, and track projects.

      What is most valuable?

      Agile Central has really helped us document our Agile requirements. It's really strong in terms of being flexible and how it's set up, getting a team organized quickly and easily. In our particular organization, we're responsible for maintaining the tool portion of it. We are not so much involved in driving the development of the individual applications, so from a maintenance perspective, we kind of admin the CA tool. Agile Central is what you'd consider an Agile management tool. It's a way of logging and storing your requirements, defects, test cases and things like that in a collaborative and Agile fashion. Everybody can go directly into one tool, see what's going on, and track their respective status.

      How has it helped my organization?

      The biggest benefit that we've found has to do with the ease of use. We can get into the data and actually report out of it. Historically, we'd gather requirements in Word documents and things like that, so moving to a tool where you've got easy access to get to the data was a big win for us. The reporting in the tool is pretty good at the team level. It struggles a little more in a big organization. We are trying to look at things across all of the teams, trying to do reporting across the whole tool, so it's a little less good there, but overall it’s pretty nice.

      What needs improvement?

      In the next version I'd like to see more of a focus on reporting at that overall level. I want to find a way to do analytics on what's going on within the tool, how many people are using it, and not so much detailed reporting on individual teams. I want to see how the organization is doing as a whole as they use the tool.

      As an example, one of the metrics that we'd like to be able to see has to do with this idea of teams that are meeting their commitments when it comes to deliverables. So when they come in to start a sprint, we'd like to be able to say "By the time the schedule ended, you hit this many of your stories, or features." And we'd like to do that, not necessarily for a specific team, but on the whole tool overall. We want to be able to compare between teams, and say "What is this team doing that's better, what is this team doing that's not." I think they could really do some work on the overall analytics. There are parts of the UI that could use a little bit of work, as they are older. It would have to do with changing the analytics and a little bit of the performance.

      What do I think about the stability of the solution?

      Stability has actually been really good. We use the cloud service, and while it does go down occasionally, they're on it and it comes back up right away. No major complaints there.

      What do I think about the scalability of the solution?

      In terms of scalability, we're a pretty big project, with thousands of teams out there, so sometimes we feel like we're pushing the tool to its limits. We start to see slow-downs in response time, and things like that, but it continues to function, for the most part. We'll see as it continues to grow. It usually shows slow-downs in the UI, or particularly in the web service interfaces, that are trying to fetch out data for large projects with thousands and thousands of features. Things can be slow because it's a lot of data to move.

      How is customer service and technical support?

      We do use technical support. We are engaged with support and we have several open tickets. The technical support has actually been pretty good. They're definitely responsive. Some of the problems that we run into are a little more difficult to solve, so the response time's not always there, but for the most part, it's good.

      What other advice do I have?

      I would definitely tell them to make sure that they plan out what it is that they're trying to accomplish with the tool. Making sure that they get a good structure set up, and if they are trying to manage multiple teams, try to establish early on what those teams will look like in terms of size and what they will be doing.

      One of the pain points that we see in having so many teams, is that every team has its own slightly different thing that they're doing in it. This is great from a tool perspective that it is supported, but from a metrics and reporting point of view, that makes things difficult because not all teams are doing the same thing.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558441
      Lean Agile Coach with SPC4 at a financial services firm with 1,001-5,000 employees
      Vendor
      Everything is in one place, correlated and related in the right way and at the right level.

      What is most valuable?

      I think what’s great is the ability for teams to really plan at the team level. CA Agile Central does this very well without much overhead. This allows our teams to really focus on the work, as opposed to the administration of the tool. I think at the team level, that's the most valuable.

      At the portfolio level, what’s most valuable is being able to manage the visions, the features, and the releases; it’s very easy, simple, and straightforward to do. I think there's good value, as well, by bringing together the business vision statements and what IT is thinking in terms of delivery, and what's possible in terms of capacity. The objects within the system are integrated well enough to allow for really smooth end-to-end planning.

      How has it helped my organization?

      It has improved the organization's functions by eliminating time wasted waiting for someone to have a prioritized list on their laptop or on some SharePoint site that to which we then have to get access. All of this is simplified and we're not wasting time looking for information. Everything is right in one place, correlated, and related in the right way, and at the right level that allows for planning, execution, and tracking afterwards.

      We have pockets of really good Agile maturity in the company and some pockets where more maturity is still necessary. I think the bank as a whole is still maturing in terms of agility, and it's ability to adapt to change. I would describe it as just pockets at this point, but growing very, very quickly.

      We use Agile for coaching as well. We try to coach to a few things. One of them is, of course, business value; to say, "hey, focus on delivering high business value first". So again, we are able to take advantage of the prioritized lists at all levels within the tool.

      This applies to transparency also; making data visible at all levels and to anybody who is a stakeholder or part of the team. The information is right there, and everybody has the same exact view given the access that they are granted.

      We work on predictability also. You're able to see the level of velocity that each team and each release has very quickly. You don't have to go and search for data. When talking about improvement, it's more of a process that we coach. But, enabling those types of conversations around continuous improvement based on accessible, real data from the system is invaluable.

      We're focused on multiple areas. We are trying to get teams to think about the system as a whole and not just their small areas. We're trying to get end-to-end visibility of how efficient we are at doing our work. That's where we coach.

      What needs improvement?

      We have submitted lots of ideas to the Ideas portal, such as milestones. We would like to make sure that that's a first class citizen, if you will. Make it a little bit more robust regarding our API plans. Reporting I think is a big one too, especially at the bank.

      We base a lot of decisions on real data. So if we're not able to get that real data in a very simple way and be able to slice and dice it, then we aren't as effective as we could be at making those decisions quickly. I'd like to see a reporting interface that is easy to use, based on report templates that we can take advantage of.

      Lastly, the Insights module within the tool was great when it came out, yet very few people harness it's power today. I think it could be more integrated into their reporting interface, if it's possible. It would really drive true insight right into the data that we are creating around our work.

      What do I think about the stability of the solution?

      I think the CA Agile Central is pretty stable. I've used it for over 6 years and it's fairly stable. We use it on the SaaS model. The website says 90% up time, which is fantastic. No real major down times that we've seen.

      What do I think about the scalability of the solution?

      We use Agile Central at scale already. The tool is being used across the entire bank and across the world. At last count, we had 7,000 or 8,000 people using it across multiple teams in multiple organizations and these are active licenses. I believe we are already using it at scale in a very real way to deliver value.

      How are customer service and technical support?

      We have worked with technical support when we have questions of defects. They are very responsive. They approach their work with an open mind or open transparent setup, where they're sharing the latest information and where things stand in terms of questions, or defects, or enhancements, if you will. Overall, we have no complaints at all, from my perspective at least.

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

      I don't believe there was a previous solution in place for Agile teams. Some teams were using Atlassian JIRA and then some are still using version one, but that was in parallel and not a replacement.

      How was the initial setup?

      I was not part of the initial set up, but I have been a subscription administrator and I'm aware of what goes into it. It's not overly difficult. I think working with the CA setup team, makes it very easy.

      What other advice do I have?

      When selecting a vendor, the ability to integrate with other internal tools is first. I also look at the stability of the brand and extensibility in being able to extend out. Of course, meeting our minimum needs is a given, such as being able to track and report on data. I want to know how robust those items are. I think most products provide those types of functions, it's just how robust they are and how high a grade they have in terms of being able to deliver that functionality. That is what differentiates vendors.

      My advice to others is to start right away. Learn as much as you can. The tool itself is not going to be your impediment or your longest pole in the tent. It’s going to take a long time to figure out what your internal culture and processes are, and the tool is only there to help you reflect what you are producing. So start early.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558090
      Architecture Managment at a comms service provider with 10,001+ employees
      Vendor
      Controlling requirements through the change request lifecycle is valuable.

      What is most valuable?

      Being able to control the requirements through the change request lifecycle is one of the most valuable features.

      How has it helped my organization?

      It optimizes the time to market of the requirements.

      What needs improvement?

      There should be different ways to decide on the requirements, not only by using a flow chart. There should be more than one way; maybe with use cases or another more graphical way to represent the business requirements.

      I wish there was a way to maintain the documentation, the knowledge management of the development team; and to keep a live version.

      What do I think about the stability of the solution?

      The stability is very good. There are no crashes.

      What do I think about the scalability of the solution?

      The scalability is very good. We are planning to complete the whole lifecycle of development activities.

      How is customer service and technical support?

      We use technical support a lot. We have our partner, and we use support with them. Technical support is excellent.

      Which other solutions did I evaluate?

      We considered IBM Rational.

      We have a lot of requirements. We have lot of business areas that continuously places demands on the IT group. We need strong tools that help us keep correctly the requirements in the lifecycle. It's important. It's not enough to do things better. You need to have a better tools. We have a lot of delays that we want to mitigate. We don't have a good time to market. Agile management helps us.

      Technical support, knowledge, and productivity are the most important factors when we chose CA as a vendor.

      What other advice do I have?

      Make sure that everybody in the company and team know the importance of the change.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558495
      Manager of Applications and Development at a retailer with 1,001-5,000 employees
      Vendor
      Forces us to plan our work and enables us to get software builds to our customers more efficiently.

      What is most valuable?

      With Agile Central, we are able to map out our work and time chunks for our sprints. It forces us to plan our work and enables us to get software builds to our customers more efficiently and quickly.

      How has it helped my organization?

      It has helped us to become Agile. It has helped us to really get our products in front of the customer faster. It's changing the culture of how we build software.

      When you look at the old waterfall methods, we weren't adapting to change fast enough. We weren't able to rapidly deploy what we were building. By the time we would build something, there would be changes that came down the line. We didn't react to it fast enough. This allows us to react faster, and to build better products. We're learning more and more every day, and using their coaching.

      What needs improvement?

      An Agile Central mobile app is long overdue. At the end of this conference, I want to look at my burn down charts. I want to look at how my teams are doing, and trying to look at the full website on a phone. It's a terrible user experience. We need a mobile application for Agile Central.

      It’s a great tool other than that. It's been fantastic. Developers love it. My managers love it. It's been great.

      What do I think about the stability of the solution?

      Stability has been very good. Every now and then, there is something. Ironically, it was down a little bit on Monday at the start of this conference, but we typically never have an issue with Agile Central being down.

      What do I think about the scalability of the solution?

      It's very scalable.

      How was the initial setup?

      Initial setup was straightforward. It was easy.

      Which other solutions did I evaluate?

      We're a long-time CA customer. We actually bought Rally before CA purchased them, so we were already a Rally customer when CA bought them. We were also already a CA customer for other products, so it really worked out well for us. We weren't upset at all over that acquisition.

      We compared Rally vs JIRA, but we felt that Rally was the better tool.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558555
      Staff Program Manager at a tech vendor with 51-200 employees
      Vendor
      We can link user stories and tasks to features and initiatives. It should integrate more seamlessly with other tools we use.

      What is most valuable?

      I like that you can link user stories and tasks to the features and the initiatives. This allows us to see how much were investing in people and effort. Mainly, I like the simplicity of it.

      We can very easily run a report that clearly shows the amount of effort we’re investing in initiatives and features. It is very straightforward.

      How has it helped my organization?

      It brought transparency and clarity to our work. We can see from one place everything the engineering team is working on, in a very simple way using a very simple interface.

      What needs improvement?

      I would like to see improvements in these areas:

      • Integration with Git is not very good. It should integrate more seamlessly with the other tools that we use.
      • The ability to inexpensively add custom reports.
      • Ability to easily add features, such as saving views, that we need to add to these reports.
      • Ability to specify required fields per project and not per workspace.
      • Some competitors offer much more flexibility.

      JIRA, for example, has much more flexibility in terms of defining your own states, your own workflows, and even when you're in the same work space. Whereas, with Agile Center, you have to decide whether share a workspace with other teams; then you must all comply with the same configuration. For us this is a problem, because many business units are sharing the same workspace even though they have different processes and different flows. So you can either all agree on the same one or move to your own. But in that case, you lose the transparency of everybody being in the same workspace, which is part of the value and core reason why we want to use the tool.

      What do I think about the stability of the solution?

      We have had issues with custom reports that were dependent on an internal Agile Center API, but they crashed often. These are now fixed, and other than these, it's been okay.

      How are customer service and technical support?

      Technical support is very responsive we were happy with them.

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

      The solution we had just didn't work and required too much time from the engineering team, which I was highly against.

      How was the initial setup?

      Initial setup was pretty straight forward.

      Which other solutions did I evaluate?

      Agile Center was already used in my company by other business units, so it was supported internally. Also, we heard that technical support was good. Since are heavily invested in Bugzilla for bug tracking, integration with Bugzilla was a plus.

      We are not expert at Agile. We use a different tool for each development model; Eternity WaterFall and Agile. I think that that's one of the advantages.

      What other advice do I have?

      In a vendor, we look for good support by people that have a lot of product knowledge. We don’t want to have to wait a long time before new features and customer feedback are integrated into the next release.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558303
      Agile Coach at a insurance company with 1,001-5,000 employees
      Vendor
      Provides transparency through backlogs. We have to use another tool for live updates.

      What is most valuable?

      The features I like are the backlogs and the transparency through those backlogs.

      How has it helped my organization?

      We have a lot of product owners (POs) and teams that work on the common backlogs, so we need the transparency in these backlogs. We get the transparency between the teams and the departments.

      What needs improvement?

      We have teams that are not collocated, so the team tool for managing and showing tasks and work has to support this.

      We use a tool that automatically updates all active users screens as
      one user updates a task or other work.

      This is helping with issues we have seen in Agile Central when more than
      one person is working on the same issue, to do a missing update of what needs to be done or started.

      I would like to see live updates. Live updates would help us because we have off-shore teams. We're actually using another tool right now because Agile Central does not support it. We're using two tools.

      I would like to see some management views on the workflow. The workflow is not lightweight. It's pretty big.

      What do I think about the stability of the solution?

      We did not have any issues with stability. Sometimes it's slow, but we have not had any issues.

      What do I think about the scalability of the solution?

      We have not had any scalability issues. We have scaled it to some degree, four or five teams, but that's just a fraction of where we're going.

      How are customer service and technical support?

      I have used technical support for minor issues and they were good.

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

      We were not previously using a common solution.

      We decided to invest in a new solution because of the Agile transformation in our company. We needed a tool for that.

      How was the initial setup?

      I was involved in the roll-out and it was straightforward.

      Which other solutions did I evaluate?

      We were looking at JIRA and other options that I cannot remember right now. It was six or seven years ago.

      The most important criteria when we selected the vendor was the functionality of the cross-transparency between backlogs. That was the main reason we chose this solution.

      What other advice do I have?

      Start small.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558585
      Project Manager at Syntel
      MSP
      We use the dashboards to allocate and track team workload.

      What is most valuable?

      We use the dashboards to allocate and track team workload. It allows us to concentrate on deliverables rather than spending more time managing.

      How has it helped my organization?

      I have a team of about ten people. Like me, all our team leaders have difficulty managing their workload. They are spending at least half an hour a day to share their updates with team leadership and this costs us down the line. With Agile Central, everybody knows what their tasks are and the current status. This allows team members and leadership to focus on the current work deliverable rather than managing their work.

      What needs improvement?

      There are a couple of accelerators in the market that allow teams to manage meetings and notes, particularly stand-up call notes. Integrating these with Agile Central will be more powerful than manually explicitly adding it and generating reports. The capability to manage stand-up call minutes will inspire this to happen.

      What do I think about the stability of the solution?

      It's very stable. We have been using it for quite a long time. We have not seen any issues.

      What do I think about the scalability of the solution?

      We try to make the most use of the API as much as we’re able, such as for automation updates. But we see a limited use of this regarding the dashboard. Aside from that, this a very good, powerful system.

      How are customer service and technical support?

      I would rate technical support 7 out of 10. It has definitely exceeded our expectations especially regarding the integration of additional marketing tools. In these cases, we need the technical support team and they promptly answer us. They help us through the process in case there are any issues and help us determine whether an issue is an application or outside issue.

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

      Originally we were using JIRA and a couple of other products but scalability and technical support were a big challenge. These were issues that kept us from upgrading as fast as we wanted to deliver. Agile Central is more stable and a proven product. CA technical support is much better and they help us progress with more integrations, helping with more with manual interventions.

      How was the initial setup?

      I was not involved in the initial setup. I was in a separate team that does not configure Agile Central. We are the end users.

      Which other solutions did I evaluate?

      JIRA was one of the options, but scalability had been a big challenge. They also had limited support. There were open source projects available, but they require a lot of investment to build from scratch and make use of the basic features that are available. In the long run it would take too much effort for us to take it forward. Whereas with an existing product like Agile Central, it’s easy to just start using it.

      What other advice do I have?

      Agile Central allows us to more effectively plan our sprints. As a sprint progresses, we learn more about what works and what doesn’t. We can then apply that learning directly into the next sprint. When we have perfected our system, we will be able to create things like burn down charts so we can colorize what happened and analyze more clearly our process with little manual analysis necessary.

      One of our major criteria for a vendor is whether the product will help us be more productive. We want to know their track record. The market is marching towards CDCA. If we have parts of features already coded, how that can be transformed to this new paradigm is a key area.

      Disclosure: IT Central Station 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.
      it_user558642
      Senior Software Engineer at a manufacturing company with 1,001-5,000 employees
      Vendor
      The Attrition view shows current tasks and user stories for the current trend. Some dashboards, views and the reporting features could be better.

      What is most valuable?

      One of my favorite features is the Iteration view. I am responsible for many tasks and I use the Iteration view to view current tasks and user stories for the current trend. I sort by owner and I determine which tasks I own and what progress I am making. So to me, personally, I think that's the most valuable feature from Agile Central.

      I like the way the dashboard is set up. I can customize it, so if it is too cluttered, I can change the view that I want and it gets saved based on my login. I encourage CA to keep playing around with the views by changing it every once in a while so that users are not afraid to change.

      How has it helped my organization?

      We were using the Waterfall methodology, but we moved Agile about four years ago. Agile Central makes the transition easier and we don't have to think twice about how to implement this or keep track of features and user stories. We know we can go to a web page to track features and break them down into user stories. Agile Central has helped make our transition more efficient.

      Where I work, there are some teams that don't practice Agile. My team started practicing about four years ago. We customized our processes, changed it around and made modifications to it. We are at a stage where we like our process. We are not afraid to make changes so I wouldn't say we follow 100% strict Agile. We started with what we considered an Agile practice and then made changes to it.

      What needs improvement?

      I would like CA to play around with some of the dashboards, some views and reporting features. I know they roll out new reports every once in a while. I don't know what I'm missing, so show me what I'm missing.

      Agile Central does do defect tracking, but not all of our teams use it. Some teams use other tools like HPE’s BPM, and a few other tools. We would like to move to Agile Central since that's where we track features and where we do project management. We would like to do defect tracking in Agile Central as well.

      Something else that CA could improve in Agile Central is the notification system. The other tools we use have pretty good notifications systems with email notifications and the ability to opt in and out of specific notifications. What Agile Central is lacking is more ways to customize notifications and the ability to opt in and out of notifications; this would help with defect tracking as well. And when status changes, I would like to receive a notification. I know it's partially supported, but it's not really straightforward to opt in and opt out.

      What do I think about the stability of the solution?

      Regarding stability, we have noticed there have been a few bugs with the website. My organization is a part of the beta program, so every time there is a beta we are one of the first ones to get it. I really like being able to optionally enable it whenever I want. We have found bugs, which is the point of a beta program.

      But, in actual production, we have seen several minor bugs. For example, when you drag and drop an object, it wouldn't do the right thing. Apart from that, nothing major. It's been pretty great.

      What do I think about the scalability of the solution?

      I have not encountered any scalability issues.

      How is customer service and technical support?

      Any time we have a problem, we use the "Leave Feedback" link on the website and they're usually prompt about getting back to us. They have been pretty helpful. Although I'm not involved with it, I know some of the administrators who are and I've heard good things about technical support from them.

      How was the initial setup?

      I was not involved with the initial setup.

      Which other solutions did I evaluate?

      I wasn't involved with choosing which tool to use, but I know other platforms were evaluated, including some open source tools like Trello. In the end they went with Agile Central.

      What other advice do I have?

      Don't be afraid to change things. It's something that I try to follow, so that's something I would give that advise to others as well. People will not like new views and changes initially, but once they get used to it, they will like it. It's similar to what Facebook does. They make very subtle changes and they force it on you and initially, you don’t like the changes. But, then once you use it for a few days you find that it works out.

      Most important to me when choosing a vendor is good technical support and customer service. This is very helpful when learning a new tool. If I have questions, I want someone to be available at the other end, to be ready to answer my questions. I want them to show me how this tool is going to work for my specific use case. That's the biggest thing I look for in a vendor.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user558471
      Senior Associate QA L2 at a tech services company with 1,001-5,000 employees
      Consultant
      Effective user story, test case, and defect management.

      What is most valuable?

      It is a very good tool is well suited for Agile methodology, and lends itself to user story management. With the introduction of test case management and defect management, it has really boomed and it is at par with some of the existing systems, apps, test management tools such as HP ALM. I really like Agile Central.

      How has it helped my organization?

      It is a single platform that your Agile team can talk about. If you talk about a user story management, then you can talk about it as well. If you want to do test case management, you have all the QA team and developers who can work on it. It's a single tool that works with all team members in a scrum team. Before any communication, you don't want to go on another systems, but rather use a single system; a one-stop solution that solves it for you.

      We wanted to have a hub, a faster time to market, high quality, and we wanted to move from Waterfall to Agile. I’m an intermediate user. We use this tool for coaching. In terms of best practices, we have certain guidelines that you need to follow. For instance, with Agile maturity, you should have your acceptance criteria selected when you have user stories and the test case results present. You can then attach your proof of testing. This tool supports these best practices.

      What needs improvement?

      You should have the ability to run various automation tools, irrespective of their organizations. Some of the teams are using HP products, or other products, such as open source producst. If your tool can run those products, that would be great. If you are able to run those tools from Agile Central, then it would make sense and be a good improvement.

      What do I think about the stability of the solution?

      It is pretty stable and it's fast also, compared to other products, like HP ALM. It's fast and performs well.

      What do I think about the scalability of the solution?

      Scalability is good. I have not faced any issues so far.

      How is customer service and technical support?

      We have a team which connects directly with Rally. You have a help feature where you can raise requests and they can be solved. We have support available from CA.

      What other advice do I have?

      I would say a thumbs up to the solution. It's pretty good and you should leverage it and try to use it. CA Agile Central gives you flexibility performing custom quoting on top of the solution. This makes it interesting and you can achieve many things with this tool.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      ITCS user
      Agile Coach at a pharma/biotech company with 10,001+ employees
      Vendor
      The information can be viewed and customized easily. The defect-management cycle needs work so that the functionality is all the way through.

      What is most valuable?

      We use it at the enterprise level, from the leadership to managers to teams, and everyone can use the same software easily.

      It's very user friendly and intuitive as the information can be viewed and customized easily.

      How has it helped my organization?

      It's the first software that allows everyone to use the same software that is actually user friendly.

      What needs improvement?

      An improvement would be if at the leadership level, they want to view certain teams, it’s easy to break down. For example, if a portfolio is 60 teams, as a director, I can filter and easily see only my teams and the stats I want.

      Also, the defect-management cycle needs work. It's already there, but the functionality isn't all the way through.

      It could offer more functionality and spread those functionalities to individual users in a way they can understand. That would make it more intuitive, but I understand that doing so is a challenge.

      For how long have I used the solution?

      We've been using it for over five years.

      What do I think about the stability of the solution?

      We haven’t had any stability issues.

      What do I think about the scalability of the solution?

      It’s meant for scaling and that’s the top functionality.

      How are customer service and technical support?

      They were great. Never any issues.

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

      It was already in place when I joined.

      How was the initial setup?

      I've performed installations in other organizations, and it was very intuitive.

      Which other solutions did I evaluate?

      We also looked at products that have good scalability because of the size of our enterprise.

      What other advice do I have?

      My advice would be to use it. As with any tool it has advantages and disadvantages.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user354006
      Team Lead at a pharma/biotech company with 1,001-5,000 employees
      Vendor
      It supports the SAFe toolkit so that you can create artifacts and define a whole bunch of teams. I'd like to see more maturity around Kanban metrics.

      What is most valuable?

      The linkages between artifacts, going from epic to feature, from feature to user story is very native and works very well. The in-built support for scrum, so having good parts on the side and the tasks go across works. We can't do that with Trello. We can do that with LeanKit.

      I think as for scrum adherence, it's very mature because I think it started as a scrum tool, and you can kind of tell that. The support for scale works very nicely.

      How has it helped my organization?

      It supports the SAFe toolkit so that you can create artifacts and define a whole bunch of teams. So you have a project pull-down, you have all the teams, and then program layer, and then the portfolio layers, so you've got the features live at the program. There's a top layer and a middle layer and then the bottom layer. It supports it very well.

      What needs improvement?

      Being a Kanban team inside of SAFe, some of the fields that you have to fill out are a little awkward, because then you can't use the views the way you want to. You have to assign it to all the SAFe people, and that might not be a Rally thing, only a SAFe thing.

      I think you can kind of tell that they started from scrum so the Kanban support kind of feels like an afterthought. I'd like to see more maturity around Kanban metrics. So, here's your cycle time, here's your lead time. But I'd like to know why was my lead time that. I want to drill in. I want more ability to drill into the data with analytics.

      What was my experience with deployment of the solution?

      Deployment hasn't been an issue.

      What do I think about the stability of the solution?

      I haven't noticed any crashing or poor performance. It's pretty solid.

      What do I think about the scalability of the solution?

      It's scaled fine for us.

      How are customer service and technical support?

      I've not used it, so I don't have an informed opinion.

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

      We've used Physical, we've used Trello, we've used Gyro, we've used LeanKit, and we landed on Rally.

      How was the initial setup?

      I think I was very involved in LeanKit and less so involved on the Rally side.

      What other advice do I have?

      Sign up for the demo and play around with it, as painful as it is to try to maintain both tools at the same time. If you have a tool and you want to try a different tool, you almost have to actually use it. You can play around with it, you can look at the demos, and you can look at the documentation, but until you actually use it, you're not going to see where maybe the pain points are.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user353874
      Associate Portfolio Manager at a healthcare company with 1,001-5,000 employees
      Vendor
      Everyone is more aligned and has a better understanding of all of the work that is happening, not just pieces of it.

      Valuable Features

      The most valuable features are the team-level interactions tracking of stories, features, and sprint. We do all of our budget tracking with it and CA PPM, and then our teams are working through Rally, so for me it's really easy to go in there and be able to see what is going on. I can see where things are assigned and where I should be worried about risks. For example, I can very easily see that a team has 10 stories on a feature and all of them are assigned future sprints, so I feel good about that.

      It's also a very simple tool to use. I find it easy to go up and down the hierarchies -- going from initiative to element features all the way down to a story level. I think it navigates pretty well.

      Then reporting is probably the other thing that I like about it. It's got a good reporting engine with it.

      Lots of customizability. I know we created a few of our own reports and then a lot of the out-of-the-box reports are pretty useful as well.

      Improvements to My Organization

      I think it got everyone aligned. I would say that's probably the most helpful thing, whereas before that I think that teams were just managing backlogs of spreadsheets or whatever they had or whatever they were doing beforehand. I'm not quite sure. I came in right after we started implementing it so I didn't really see what was there beforehand. I do know that just from when I first started to today, everyone is more aligned and has a better understanding of all of the work that is happening, not just pieces of it. It has an API that connects it with CA PPM.

      I know you connect CA PPM to other agile tools as well, not just routers. I know a lot of people are hoping for that and a portfolio RPM are kind of pieces of it, but I don't think it's quite there yet. I would like to see it be a little more integrated going forward.

      Room for Improvement

      The portfolio side of it needs improving, especially integration into CA PPM. It would be nice to hopefully see some of those have a little bit more connections.

      I know we do a lot of high level planning and it seems like there are a lot of duplicate features back and forth, and it's kind of like, pick one or the other at this point. It would be nice if they talked a little bit more. For example, we'd really like a better integration with Rally.

      Stability Issues

      I don't use it daily, but there seems to be no stability issues.

      Scalability Issues

      We ran into some problems with archiving some old stuff but we created a separate tree and that's where we put all the archive stuff. It's still there, it's still accessible but it's not messing with the reports of your enterprise.

      Customer Service and Technical Support

      I've just used our internal technical support.

      Initial Setup

      I wasn't involved in the setup.

      Other Advice

      Make sure you understand your processes and just know that it's not the tool. It's more about the process and how you work with it right. I know we did our last upgrade with Clarity and we didn't have our processes all the way defined. We started implementing things in the tool only to find they broke later, so we didn't have that process defined. Make sure you understand what you need before you start.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user352929
      Software Engineer II with 1,001-5,000 employees
      Vendor
      We're able to track all the users' codices, track all the features, track the capacity so that we could plan, and find out as a team what the capacity is to deliver in a two-week sprint.

      Improvements to My Organization

      When we started to go to the agile model from the waterfall one, it was a big challenge for us. We had couple of folks move from Paypal to us, and they gave us a success story in a meeting. When they were looking at tools, they came across Rally, and it was introduced to us by the CA team. We had a couple of training sessions on Rally.

      The immediate impact of that was when we started using Rally, we didn't even know that we could do agile. But because of Rally, we were able to track all the users' codices, track all the features, track the capacity so that we could plan, and find out as a team what the capacity is as a team to deliver in a two-week sprint.

      As an application developer, I can speak only based on what the developer and app teams can do, and this has helped a lot. We were trying to go strictly agile, and I think Rally is helping us big time.

      Room for Improvement

      When we started using Rally, we used the user interface pretty often. It was very informative and everyone was comfortable with it. But there were challenges with product backlog and how to track the capacity planning. Everyday you needed to update the status. There were a couple of questions about, what is the capacity of every developer or a QA engineer for this sprint.

      Stability Issues

      It has been stable for us.

      Scalability Issues

      As far as I know, there are 16-17 people using it, and since I'm relatively new with the company, I'm not sure what the plans are in terms of scaling its use.

      Customer Service and Technical Support

      I haven't used Rally technical support yet, but we have a 1-year subscription.

      Initial Setup

      It was straightforward. We didn't have to do a lot. We just went to Rally 101 training, and there was some agile coach for us on site. She trained us on how to use the Rally tool to update our social studies tasks.

      Other Advice

      I would say Rally is the way to go.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user352881
      Senior IT Project Manager at a comms service provider with 1,001-5,000 employees
      Vendor
      It helps us track our development life cycle for our development teams. The reporting functionalities need improvement.

      Valuable Features

      It has most benefited me because as a release manager, it helps me know and mitigate the risk going into production so I can reach out to the different teams. I can, at anytime, pull up a report to show me where the status of a candidate for release is and I can reach out to those teams. Based on the report, we can then decide whether we need to allocate more resources to ensure we're able to release on a certain date.

      Improvements to My Organization

      It helps us track our development life cycle for our development teams. They can keep track of the progress of their user stories and features, from the intake process all the way through deployment and into production. This can be done in tandem with test results, and we have a substantial team with various applications.

      Room for Improvement

      The reporting functionalities need improvement. Also, there's too much lag, but they're fixing that.

      Scalability Issues

      We're at 13,000-plus companies. We have lots of applications, lots of different teams with upstream and downstream dependencies. Different teams have different maturity levels in terms of how they are using Rally. Some are just getting on board, and some have been using it for a long time. So we're trying to consolidate that.

      Customer Service and Technical Support

      The technical support with Rally is going pretty well.

      Pricing, Setup Cost and Licensing

      I can't even give you off the top of my head how many licenses we have with them, but it's user-based licensing and we have quite a few of them.

      Other Advice

      I think it's a great tracking tool. There are similar tools out there, but for us it's convenient, it's intuitive.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      it_user351489
      Principal Software Architect at a aerospace/defense firm with 1,001-5,000 employees
      Vendor
      It integrates with Rally so we don't have to use and maintain our infrastructure, but while it's stable and doesn't crash, at times the performance is slow.

      What is most valuable?

      It provides overall functionality in project management and release tracking all in one tool. Those are our main things. Additionally, it provides integration with JIRA and ALM. The Rally guys came in and said they would integrate, and that’s a great feature. We don’t have to use our infrastructure, so maintenance of the system is avoided.

      What needs improvement?

      The UI had some issues, but I attended sessions at CA World 2015 and they updated this. But they still need to improve performance.

      What do I think about the stability of the solution?

      It is stable, but at times the performance is slow. It doesn’t crash, but it's slow.

      Also, because it’s on the CA network, we have API connectivity to Rally. However, our server proxy cannot talk to the Rally systems. Rally has a fix for that, which is working for now, but we need a long term solution.

      What do I think about the scalability of the solution?

      We have 800-1200 users. I haven’t seen any issues so far. Rally was installed three months ago and the transition is going well.

      How are customer service and technical support?

      The response times are good and the support is very good. I deal with a few guys, so when I email them I get a quick response.

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

      Our VP was given a presentation on project management, defect management, and release tracking all in one tool, which excited him. Then we were given a demonstration, and the fact that our existing tool didn’t do those things made Agile Management an easy choice.

      How was the initial setup?

      Set up of the software is easy but the integration is complex. If you are only using it as a tool, it is good, but the integration is not so straightforward.

      What other advice do I have?

      If you tell me you are using VersionOne, you would get more for your money with similar costs from CA Agile Management. So more value, that’s number one because being with a bigger company means you get more value with the community. If you are not using any tool, then you should start using a tool, and this is a good start.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      Buyer's Guide
      Download our free Application Lifecycle Management (ALM) Suites Report and find out what your peers are saying about Broadcom, Atlassian, Microsoft, and more!