I work with Tech Mahindra, where there are different practices and competencies that focus on various tools and platforms such as Microsoft, CRM, and ERP. We manage our own practices and collaborate on projects as needed. My team specifically focuses on user interface development and provides experience design inputs for SAP projects when they arise, helping to shape the customer journey for those applications. For custom development, we handle it end-to-end.
We use Rally Software to plan our development work. We have quarterly PI meetings, which involve team members from across the globe. The tool helps us manage product integration, set dependencies, track issues, identify risks, and coordinate handovers between teams. We also use it for planning, coordination, execution, and signing off on deliverables and demos.
Dev Ops Engineer at a insurance company with 5,001-10,000 employees
Real User
Dec 22, 2023
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.
Agile Delivery Transformation at Transparent Change
Real User
Apr 19, 2023
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.
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.
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.
Implementation Consultant at a healthcare company with 201-500 employees
Consultant
May 3, 2021
It is used to track any enhancements or new integrations. We have integrations from mainframe systems to RESTful services. We also have a few SOAP integrations. Essentially, we use the feature level of Rally to document what the interface is and then the engineers make the user stories within the feature to represent the tasks that they need to do to complete the interface, which includes everything from making the design document to the activities that they do in IIB, such as deploying the code to production. Our version has probably been updated within the last three months.
Scrum Master for a Big International Bank in Belgium at a financial services firm with 5,001-10,000 employees
Real User
Jan 8, 2019
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.
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...
I work with Tech Mahindra, where there are different practices and competencies that focus on various tools and platforms such as Microsoft, CRM, and ERP. We manage our own practices and collaborate on projects as needed. My team specifically focuses on user interface development and provides experience design inputs for SAP projects when they arise, helping to shape the customer journey for those applications. For custom development, we handle it end-to-end.
We use Rally Software to plan our development work. We have quarterly PI meetings, which involve team members from across the globe. The tool helps us manage product integration, set dependencies, track issues, identify risks, and coordinate handovers between teams. We also use it for planning, coordination, execution, and signing off on deliverables and demos.
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.
We are using Rally Software in our company for agile development. We also use it for software development using agile methodology.
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.
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.
We primarily use the solution to scale agile and for safety.
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.
It is used to track any enhancements or new integrations. We have integrations from mainframe systems to RESTful services. We also have a few SOAP integrations. Essentially, we use the feature level of Rally to document what the interface is and then the engineers make the user stories within the feature to represent the tasks that they need to do to complete the interface, which includes everything from making the design document to the activities that they do in IIB, such as deploying the code to production. Our version has probably been updated within the last three months.
We primarily use this solution for agile project management. We use it to work on some of the challenges we have, including test management.
It's mainly about test cases and automation of data. I, as a test automation architect, collect all that data and show the metrics.
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.
Execution of software development.
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.
CA Agile Central is used for the lifecycle of Initiatives, Features, and User Stories, Defects: from concept through delivery