Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$81.85
per month 10 users
Rally Software
Score 7.0 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.
N/A
Pricing
Atlassian Jira
Rally Software
Editions & Modules
Standard
$8.15
per month per user (minimum 10)
Premium
$16
per month per user (minimum 10)
Data Center
$44,000
per year 500 users
Enterprise
Contact Sales
per year
No answers on this topic
Offerings
Pricing Offerings
Atlassian Jira
Rally Software
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Atlassian Jira
Rally Software
Considered Both Products
Atlassian Jira
Verified User
Engineer
Chose Atlassian Jira
Jira is simple, easy to understand, has less learning curve, highly descriptive features. All these features make it easy to work and manage and track our day-to-day work for better progress. All these features make Jira give an upper hand over other tools.
Verified User
Manager
Chose Atlassian Jira
Jira is the "default" do-everything software project management platform. It literally does everything, but consequently does nothing particularly well. That said, it is robust enough to compete with enterprise heavyweights like Rally, and (usually) easy and light enough to …
Jira Software is considered perfect when it comes to handling a software team which might need an advanced agile functionality as well as structured workflow wherein Trello could be quick in terms of capturing or sharing the ideas or lists or to-do's. Jira has a better UI and …
I personally use Trello to keep track of personal stuff and used it as a task management tool for very small development teams/projects, but Jira is a million miles ahead of it regarding a number of options and customizations. I also used Rally on a previous company and …
Previously I have used TFS and Rally. JIRA is very simple to use and has lots of features compared to these two and other tools available in the market. The ability to integrate other tools is much easier in JIRA. It is also robust, scalable and has a good number of add-ons to …
Though with JIRA you need to buy a lot of plugins but it is still cheaper than HP ALM or HPE Octane which is very costly. HP QC is a fully functional software lifecycle tool and probably strongest in its test management capabilities. But in Agile we don't need that extensive …
JIRA was already in place; there wasn't a good reason to switch to something else. We just needed to work on refining our processes and clean up the existing structure so that we could make progress on our SDLC while getting our MVP out the door. If you are really starting …
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, …
Overall, Rally Software is a better and more powerful tool than Jira for the same exact purposes. Jira cannot function as a requirements repository so it needs plugins or separate tools to do the same thing. There is no space or option to see all defects or user stories or …
Scaled Agile Framework (SAFe) & through Test Management were two critical factors that lead to selection of CA Agile Central (formerly Rally).
Executives want to maintain trace-ability & detailed test management options like we get in ALM along with SAFe implementation support. …
Verified User
Team Lead
Chose Rally Software
It was a close race between Jama, JIRA and Rally. We decided to go for Jama as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
We used CA Agile Central (formerly Rally) before but recently switched to JIRA. I used JIRA before Rally too, and I think it was easier to manage defects in JIRA. Also, I think JIRA is better for teams and companies that want to implement agile/scrum life cycles. It's easier to …
We started exploring new tools, and found better adaptation of our team toward JIRA. JIRA provided engineers with simpler interfaces and more reliable service, even though less unnecessary features. Also the managers found in JIRA better ability to eliminate noise and focus on …
I've also evaluated the following agile solutions: ActiveCollab, Agile Bench, Agilo for Scrum, Atlassian JIRA, Pivotal Tracker, SpringGround, Targetprocess. Telerik Teamprocess, VersionOne, ZebraPlan etc. If it’s time to transition to software that’s specific to your Agile …
Atlassian Jira is one of the most commonly used tools in the IT industry so most times people have previous experience with it. Atlassian Jira is really well suited for teams to visualize their work in progress and plan. We have a general way of working though that if a task is less than an hour of work we don't create a Atlassian Jira story, because the process of creating a story and getting it into progress can take more time than it's worth for someone who doesn't use Atlassian Jira as often.
Rally is well suited to help outline the specific tasks of a project, create timelines, indicate progress/status of tasks and provide views of team members' workloads. My team used it for our weekly stand up meetings in order to update one another on our progress, and our manager used it as a way to determine who had capacity for additional tasks. It facilitated our transition to a more agile work environment and we used it to implement 2 week "sprints".
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.
The level of permissions is only there at the top level, many times, a just lower ranked person is stuck because one the admins have right to give certain permissions, there could be a permission management system more robust and customisable.
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.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
I use Atlassian Jira on a regular basis and my day to day task include creating. new tasks and subtask after that implementation of Atlassian Jira ticket. it helps us to have time log which is very convenient and also we have options to set the estimates as well to the ticket
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 have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.
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.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
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
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
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
Jira was selected because it is used by all of our clients and has become the accepted standard in the type of work that we do. The other tools are great in their own right and would better suit a more insular way of working, where a business conducts all work internally, but Jira seems to lend itself better to collaboration across a wide field of disciplines and multiple businesses working together.
It was a close race between Jama, JIRA and Rally. We decided to go for Jama as a requirements management tool and use Rally for Agile projects. The cost was another factor that made us select Rally.
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