I like the discussion and note-taking capabilities. It's great to keep everything connected to the story itself. A lot of times, tracking changes across features or Epics that change from TI to PI can be tricky, especially with prefixes or how you phrase things. Continuity can be lost. 

That's why we use a common prefix for all things related to digital transformation, like "digital-," so we can easily search and find all relevant user stories. It's a kind of grouping mechanism, even though there might not be a dedicated field for it, like tags.

I wouldn't single out any specific feature in Rally Software as I find the entire solution quite useful for us. About five years ago, we found a feature that gave us the team's speed or velocity, which was helpful at the time. However, it is no longer relevant, and we do not use it anymore. Currently, we find resource scheduling, user stories, and strength to be the most valuable features of the solution.

When it comes to the valuable features of Rally Software, it excels at burn-down charts, burn-up charts, and road mapping once it's set up. I particularly appreciated the new feature for releases and road mapping, which worked exceptionally well. 

What I like most about Rally Software, in terms of using it for the agile process, is that it's clear, useful, and user-friendly. I also like that it has every field you can use for the Scrum process.

Another valuable feature of Rally Software is the project tree. That's a lovely software functionality because it lets you better understand the parent and child. The project tree makes that very clear.

I also like the backlog page that shows you the backlogs, and then I can move each log from the backlog page to the screen. You don't have this feature in Microsoft Azure DevOps, so in Microsoft Azure DevOps, you have to create a lot of queries to understand the backlog status. In Rally Software, you don't have to do that.

When Rally Software updated its version and added new functionality, it didn't impact the project I was working on, so that's another pro of the solution. On-premises, every time you update the server or the version, it's a nightmare.

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.

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.

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.

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.

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

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.

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.

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.

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

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.

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.

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.

• 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.

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.

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.

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.

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.

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

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.

We use all of the features. It's been a great solution so far.

It's very user-friendly.

We are able to implement PI planning for safety.

We use the roadmap features, and we're getting better at using dates to use the roadmap so that we can see if we're on target for work. 

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.

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.

As a requirements engineer, most valuable is user story writing/editing/reviewing with peers.

The most valuable feature of this solution is the Kanban board. The team board that you can see, and enables you to capture the working agreements as well as the date and stage. Because that feature is not available in Jira, I found it useful. In terms of metrics, Rally assists you with capture, allowing you to better understand cycle time and lead time metrics. Those are the features of Rally that I really enjoy.

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.

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.

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.

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.

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.

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. 
 

The most valuable features of Rally Software are the executive dashboards, ease of use, and many other features. They have encapsulated everything that a GI can do, such as monitoring, maintaining, and then releasing. It's continuous integration and development. 

The product has excellent customizable reports. There are some custom lists that are deployed in the recent version as well, which have proven to be useful to our organization.

The solution is very stable. We haven't had any performance issues in that regard.

We have all the features we need. It's a good product in that sense.

The pricing, for the most part, is reasonable.

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.

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.

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.

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.

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.

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.

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.

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.

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.

• 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.

• 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.

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.

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.

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.

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.

It is easier to:

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

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.

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.

• Portfolio management

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.

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.

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

• 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

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.

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.

We use the dashboards to allocate and track team workload. It allows us to concentrate on deliverables rather than spending more time managing.

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.

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. 

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. 

Defect management is most valuable, since I am on the QA side. It's a very good tracker.

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.

Being able to control the requirements through the change request lifecycle is one of the most valuable features.

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.

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.

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

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.

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.

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.)

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

• Requirements management
• Development team planning
• Tracking progress against plans
• Linking strategy to execution

Portfolio management is a valuable feature.

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.

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. 

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.

The valuable features are:

• Tracking progress and other parameters.
• Allowing a better overall picture of activities.
• Facilitating the interaction between team members and teams.

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.

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 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.

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.

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.

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.

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

• 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

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.

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.

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

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.

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. 

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

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

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.

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

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

The features I like are the backlogs and the transparency through those backlogs.

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.

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.

Plan, Quality, Track [Iteration status, burnout charts, etc.]: All these menu features are highly valuable.