The world of work is constantly changing. Agile work processes in particular are becoming increasingly popular. Even large companies are trying to introduce agile working methods. For many, the Scaled Agile Framework (SAFe) is the right solution for their agile teams. However, implementing SAFe with all its features such as providing reports, visualizing dependencies and automated documentation is not always easy in reality. Many companies spend a lot of time and money searching for the right…
N/A
Rally Software
Score7.7 out of 10
N/A
Rally Software headquartered in Boulder, Colorado developed the Rally agile software development / ALM platform which was acquired by CA Technologies and rebranded as CA Agile Central. After CA's acquisition by Broadcom the software was once again rebranded as Rally.
Agile Hive is used for our value train within a SAFe setup. Every quarter we organize a so-called Product Increment (PI) Planning, where we plan all Features and Enablers in Agile Hive. Based on the priority of the Product Manager all teams plan their Features and Enablers accordingly to the sprints that are determined by the Release Train Engineer and set up in Agile Hive. The teams then create User Stories and estimate them and based on their sprint velocity (defined in Agile Hive) Product Owners can see how many Features and Enablers are realistic in one quarter (Product Increment). Further, dependencies across teams can be defined and made visible in Agile Hive, so that the plan is feasible. Without Agile Hive it would be hard or impossible to plan across several teams within a value train and to manage all dependencies. Additionally, with Agile Hive the plan is more realistic, so what can be achieved within one quarter in product development.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Rally Software is well suited for large Agile or scrum teams who do sprints and it helps managing sprints and backlogs. It is well suited for organizations who want visibility into work being done and progress. Suitable for tracking is user stories, defects and release planning. Works well with CI CD too. It would not be suitable for small teams or startups. For teams that don't use agile. Teams who want lightweight tools like Jira. Companies with a limited budget.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
There are dashboards that provide friendly and useful metrics at the team, program and portfolio levels which help get an easy and quick visual representation of what's going on.
Story management made easier, It offers a quick way of quickly entering a number of user stories without losing the overview, by just typing the title and selecting a few attributes directly in the overview screen.
Sprint management is seamless in CA Agile Central . It allows you to drag stories from the backlog to the sprints and back again. When a story is dragged into an sprint, it automatically checks the velocity for that sprint and indicates how many more story points can be chipped in. No more manual checking needed by scrum master with respect to allocation and team velocity.
Though CA Agile Central has many inbuilt apps, but it also has an App-SDK that allows you to build free app extensions using JavaScript and HTML. So, as per their needs, teams can customize & build various apps & dashboards.
Dashboard is an awesome feature which allows you to select and drag panels with all kinds of graphical information about the current sprints and releases.
It offers tremendous support for scaled Agile & almost all scaling frameworks are supported specifically tuned to SAFe .
CA Agile Central includes several applications but it also integrates well with Jira, Confluence, Jenkins, Eclipse, Subversion, IBM, HP, Salesforce.com and many other products to allow users to organize projects to their specifications. So you can still use Jira at a team level & CA Agile Central at the program & portfolio level for efficient tracking & management.
The custom tags are very helpful in segregating the user stories based on the project needs. Even though it's a very small feature, it is very effective ( you will realize why specifically if you are using Jira).
CA Central Agile enables agile delivery with ease and provides comprehensive features to track time-boxes, Work In Progress items of the forecast increments.
Backlog management is hassle free since you can either drag and drop your user stories to the desired position on the backlog, or change a setting and manually enter priorities as a number.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
User management is pretty basic and could be better. For example more filters and reports and more ability to do mass updates.
The report generator is very, very basic and is not WYSIWYG. It has limited filters to generate reports. Often a Scrum master will need to export data to Excel or a tool like Crystal Reports to get enhanced reporting capability.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available
The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.
I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.
They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.
I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial
Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
it helped organizing many of the processes management use to communicate tasks with engineers, and provided detailed charts on the speed/blockage during any iteration
with time Rally became the main tool we used to track and report tasks/defects in our projects, but frequent service outages made it very hard to continue consider as a reliable solution
too much features is good, but for engineers a few features (User Stories section, iterations, defects, and Kanban boards) are necessary and the rest is just noise
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
