Rally Software Primary Use Case
LH
Lee Hanna
Dev Ops Engineer at a insurance company with 5,001-10,000 employees
We use it for our backlog and tasks within Scrum and Kanban. We use it based on epics, features, and user initiatives at various levels.
Our group is at a lower level, which focuses on features under epics and uses user stories further down. We try to break things down as much as possible, but legacy code sometimes requires estimations. Breaking down user stories is the hardest part. While Rally tracks sprints well with good note-taking, we have challenges.
Our team is a hybrid. We handle operational updates like server tasks, not strictly following scrum patterns but carrying tickets over sprints. There's no easy switch between Scrum and Kanban, so we adapt.
We also handle production issues, supporting developers and DevOps in their tools. It's customer-focused and keeps things running smoothly. That's primarily how we use the board.
View full review »Regarding my use of Rally Software, it was originally called RallyDev when I started using it in 2006. However, it was later acquired by CA and renamed Rally CA. One of our use cases for Rally CA was to support our business process automation (BPA) efforts and move everything to the cloud. When we first started using Rally Software, they did not have capabilities and strategic initiatives set up, and their features and ethics had disappeared. However, we soon discovered that their strategic initiatives were now referred to as Epics, and the capabilities module had replaced the features. Additionally, they had always had users.
Unfortunately, this breakdown did not translate well to the team I took over for, and I had to restructure all of the releases and tie them to function to ensure that we could use billing codes in the capabilities. We also had to create governance settings reports to catch errors and warn us about missing features or capabilities. This was important because it was easy to lose a step with Rally CA, and we needed to stay on top of things. As a result, we developed a workflow governance system that alerted us to any issues or discrepancies in our work. For instance, if we put the projected end date before the projected start date or if we had stories without capabilities, we would receive warnings.
View full review »I used Rally Software for the agile process in software and mechanical products. My previous company produced software for a machine, and I embedded the software.
View full review »Buyer's Guide
Rally Software
March 2024
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.
SD
Shreenivas Dharwadkar
Sr Engineering Manager - Design Engineering at Baker Hughes
We are using Rally Software in our company for agile development. We also use it for software development using agile methodology.
View full review »Rally Software is typically used for dealing with all the scrum and agile principles and work orders. It keeps track of whatever workers do in the application development lifecycle before release.
View full review »We primarily use the solution to scale agile and for safety.
View full review »Buyer's Guide
Rally Software
March 2024
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.