Rally Software has been viewed as a go-to application lifecycle management (ALM) software for organizations looking to adopt Agile development methods into their project portfolio management practice. Its out-of-the-box support of the Scaled Agile Framework (SAFe) made this solution particularly attractive for organizations looking to use Rally as a foundation and centralized platform to scale Agile and coordinate work across the organization and up into the business.
Source: Rally Software at SoftwareReviews, accessed April 16, 2020
However, Rally Software has gone through significant changes that can make prospective customers wonder its future viability:
At the time of Rally’s acquisition by CA, Rally appeared to be a good compliment to CA’s comprehensive portfolio of development, testing and deployment solutions. Even though Rally may not currently have the extensive third-party and community marketplaces as its Atlassian Jira and Microsoft Azure DevOps competitors, it made strides to extend its out-of-the-box integrations with many of today’s popular tools.
Broadcom still sees value in maintaining and enhancing its Rally product despite losing the prominent position it once held. The most recent Rally On-Premises Version 2.0 release saw a number of changes to its UI, architecture, and connectors in addition to new features and fixes. This release builds upon a recent update made in late 2019. Some notable enhancements include:
However, there remains a feature disparity between its On-Premise v2.0 version and its SaaS offering.
Rally Software can help organizations bring Agile practices into their project and portfolio management practices. The added benefit of a vast Broadcom portfolio of development, testing, and deployment tools makes Rally an enticing option. Unfortunately, having and supporting a diverse portfolio (built through CA Technologies, Broadcom, and Broadcom Limited acquisitions) has its own unique set of challenges.
Rally remains considerable a player in the ALM space. However, it appears to be slowly losing ground to its competitors in a constantly changing marketplace.
Source: Application Lifecycle Management Category at SoftwareReviews, accessed April 16, 2020
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.