Discover PerformanceHP Software's community for IT leaders // July 2012
ALM shortens release cycles—if developers are on board
For application lifecycle management to really work, you must bring suspicious developers into the fold and let them use their preferred tools.
Application lifecycle management aims to align all application teams to the process of planning, developing and testing software applications for a good reason: It works. It increases control, visibility and predictability throughout the process. It also enables change management, risk-based prioritization and communication across disparate teams.
But developers are often resistant to participating in ALM. And without their cooperation, ALM cannot deliver all of its promised benefits. That’s why application lifecycle management must evolve to adapt to the people that enterprises need to use it.
Why developers need ALM
Most enterprises haven’t bothered trying to standardize across a single platform for ALM because they know developers want to use the best-of-breed tools of their choice. But while that approach helps developers do their jobs, it also causes problems.
As an example, suppose that in a global company, Team A uses Java, Eclipse tools, and agile processes, while Team B uses Microsoft Visual Studio and waterfall processes. In the absence of a comprehensive ALM system, Team A and Team B cannot keep up to date on each other’s activities. Stakeholders on Team A may not be aware of the identification of a software defect or the changes made in response to it by Team B. Disjointed communications and a lack of traceability lead to lost productivity, project delays and costly rework later in the application development process. Developers can’t properly communicate without ALM.
Why ALM needs developers
Most ALM solutions can connect business analysts, testers and project managers on a single unified platform. But that’s not enough to make a project successful. ALM won’t give a comprehensive view of the application’s lifecycle if it doesn’t capture the most up-to-date development work as well. In other words, it won’t work.
What’s needed is an end-to-end solution that provides a common application management platform that all project stakeholders share and that allows development teams to use their tools of choice. By introducing lightweight processes and tools that enable developers to work in their familiar environment, it’s finally possible to bring the development team into the ALM fold.
ALM of the future
An ALM solution that addresses developers’ needs would integrate with their tools of choice. It would let them quickly assess the current state of any application, including:
- The business goal. Why is the new content or new code being checked in? What functionality is it supposed to deliver?
- The motivation. Is it aimed to fix a defect, or is it a derivative of a new requirement or a new user story?
- Traceability. Which build does the content belong to? Which requirement or defect?
- Release progress. How does this content contribute to the progress of the release or the iteration? How does the new piece of code help the team achieve its goals for the release?
- Risk assessment. How stable is this code? Does it have areas that are fragile that need further attention by the testing team?
- Governance. How can we ensure that developers are spending their time in alignment with business priorities?
This kind of context-driven coding can help developers better understand where their work fits in the bigger picture. In addition, context-driven reporting—in which the ALM system is automatically updated as the developer codes—can tell the rest of the team what’s happening. Tasks should be presented in the development environment in a way that frees developers from the need to report progress, update status and add a description of their work. Integration between the developer’s environment and the ALM system enables this kind of context.
The next phase of ALM must deliver capabilities that can serve the needs of the business and get developers involved. That’s the only way to realize the full promise of ALM: control, visibility, predictability and less risk.
Read the full white paper, "Shorten Release Cycles." And for more information on application lifecycle management, see HP’s ALM portal.
HP CEO Meg Whitman discusses how connected intelligence will drive IT operations, application development, IT security, marketing, compliance—and the bottom line. Register now.
Fast-growing mobility can drive difficult IT choices. Learn how to engage users, partners, and customers with your solutions.
HP Software’s Paul Muller hosts a weekly video digging into the hottest IT issues. Check out the latest episode.
In response to the shifts in technology seen in mobile and Big Data—along with the shifts in methodologies like Agile—the pace of application development has changed, causing the need for total traceability in your requirements to become even more evident.
Dev Center 20/20
How will we organize development centers for the apps that will power our enterprises?
Introduction to Enterprise 20/20
What will a successful enterprise look like in the future?
Challenges and opportunities for the CIO of the future.
Welcome to a new reality of split-second decisions and marketing by the numbers.
IT Operations 20/20
How can you achieve the data center of the future?
What the workforce of 2020 can expect from IT, and what IT can expect from the workforce.
Preparing today for tomorrow’s threats.
Looking toward the era when everyone — and everything — is connected.
Data Center 20/20
The innovation and revenue engine of the enterprise.