Integration of Application Lifecycle Management

For almost a decade, major software vendors have been marketing the concept of Application Lifecycle Management as a way to coordinate software development activities, and the result has been mixed. According to Forrester, three quarters of software and services decision makers at American and European enterprises are aware of this emerging discipline.
Nearly 29 percent of IT shops are using ALM, and only 23 percent are not aware of it. Of the companies that are not using ALM, almost 60 percent are either interested in using it or are in the process of starting a pilot in the next 12 months. However, despite strong awareness and interest, Forrester also found that the understanding level of ALM is low and the vendor offerings have been slow to hit the market.

Trending Articles

The Monty Python Project Manager: And Now for Something Completely Different

by William Craig Forgrave

The Monty Python project manager is a model for the new generation of creative collaboration leadership. The author looks at four movies that encapsulate the project management process and discovers lessons on how to generate ideas that are completely different, motivate teams on a quest to deliver the holy project grail, inspire them in times of adversity to look on the bright side of project life, and find true rewards and meaning in their work.

Topic Teasers Vol. 44: Don't Hire Heroes!

by Barbee Davis, MA, PHR, PMP, PMI-ACP

Question: Finally, we have convinced human resources that our agile team lead and our ScrumMaster need to be involved in hiring new team members. But now that we have the authority, we really don’t know what to look for in a good hire. How do we use this new power to our best advantage in choosing a fresh agile colleague?
A. Be careful what you ask for. Only human resource certified people are qualified to choose new employees for an organization. Revoke your participation rights in this process or you will be blamed when this new hire fails.
B. It’s not only the questions you ask, but what you do with the answers that will empower you to choose the best addition to your team. Create a good list of questions and know how to interpret what you hear.
C. Your product owner is the person on the management team and is more experienced in what makes a good agile team member. Ask him to sit in on candidate interviews and then defer to his superior judgment when making the final choice.
D. The person you hire must fit into the team, so assemble the entire team and have all of them work with you to interview potential candidates. Once they have agreed on a choice, they will be forced to work with the new person successfully since they have been part of the hiring decision.
Pick your answer then Test Your Knowledge!

Why 'EPMO' Does Not Mean 'Strategic PMO'

by Andy Jordan

EPMOs have become much more popular in the last few years, but organizations aren’t always seeing the benefits that they expected--why? Are you dealing with some kind of Frankenstein’s monster bolted together with the “good” parts of individual approaches?

Old Wine in New Bottle or a Useful Approach
An application lifecycle is the continuum of activities required to support an enterprise application from its initial inception through its deployment and system optimization. According to Butler Group, a European IT research company, the management of an application lifecycle as opposed to its development is more effective and concerns much broader issues than those of project processes and methodology. It covers a variety of software lifecycle activities including project management, project tracking, development processes, configuration management, quality control, IT governance, IT portfolio management and release management.

ALM coordinates lifecycle activities so that all efforts are directed at delivering applications that meet business needs, but it does not guarantee successful software delivery. A development effort can still fail even if all individual lifecycle activities were completed without errors.

Forrester defines ALM as:

The coordination of development lifecycle activities, including requirements, modeling, development, build, and testing, through: 1) enforcement of processes that span these activities; 2) management of relationships between development artifacts used or produced by these activities; and 3) reporting on progress of the development effort as a whole.

March Toward Integration

Over the years, ALM has emerged as a discipline and a product category. It is gaining recognition and adoption not only because of the push from vendors and analysts, but also due to its benefits. ALM significantly improves project success rates, improves the quality of software delivered, reduces development time and makes software development more visible to higher business management.
Even though there are significant benefits of the management of application development as an end-to-end business process, there are many barriers to adoption of this perspective.
For quite some time, IT shops have been using a variety of tools and products to manage and support different phases of software lifecycle, but integration between them is lacking.  For example, development efforts and coordination could be reduced if the development specs are automatically updated when new requirements are added; it would be useful if--when a software module is checked in--the appropriate plan to test it is generated automatically. Similarly, the next version of software would be produced better if the performance data of a previous application is automatically fed into its planning. This lack of integration is a major reason that adoption of ALM is slow.
As ALM is gaining acceptance, its commercial potential is increasing and more vendors are trying to fill the market gap by providing solutions for it. Many vendors like Borland, IBM, Microsoft, Serena, Telelogic etc. are rolling out products that inter-relate many lifecycle phases and make application development a repeatable business process. These solutions allow development teams to define and execute consistent lifecycle processes. They provide real-time visibility into the application portfolio, enabling management to make investment decisions and determine the status of projects. They provide quick and easy access to all lifecycle information and enhance the communication between various teams.
Today’s ALM solutions have gradually evolved through accumulation of individual tools rather than through a focused design. One reason for this accretion is that products and tools automating and supporting lifecycle phases were introduced when needed without a master plan for a complete ALM solution. Once these tools demonstrated their usefulness to development teams, then a new demand arose for interaction amongst them. The business opportunity became obvious, and vendors started to put together an effective solution by integrating these tools.
Forrester calls today’s solutions to be ALM 1.0. Their major characteristic is that there is a single tool for each role. These tools may not be uniform and vary by company, business units, teams and individuals. They have redundant features in areas like workflow, collaboration, reporting, analytics and security, which maintain functional silos eliminating cross-lifecycle transparency. They have micro-processes (workflows in quality management tools) embedded in each practitioner tools and macro-processes (connectors between two tools), embedded in tool integrations that increase the effort spent in building and maintaining synchronizations.
More on the Horizon: ALM 2.0
Despite many inherent limitations in today’s ALM solutions, the market for them is growing. Forrester estimates that enterprises spend more than $5 billion on new licenses for ALM tools ever year. This is bound to go up as vendors graduate to ALM 2.0 from a collection of lifecycle tools to a platform for coordination of development activities.
Industry experts say that the newer versions of ALM solutions will offer tools assembled out of plug-ins, and customers will pay for only the features that they need. Common services like collaboration, workflow, security, reporting and analytics will be available across tools and built into the platform. ALM 2.0 will be repository neutral with no need to migrate old assets unlike today’s solutions, which require the use of the same vendor’s SCM solution for storage of all lifecycle assets. The new generation of solutions will use open integration standards, allowing for deeper integration with third part tools. They will have processes as versionable assets and share common components.
There is no vendor who is providing these features today, but many are working toward it. Butler Group thinks that product offerings from Borland, Compuware, IBM and Telelogic are a cut above the competition. Microsoft, Mercury and Serena also offer products with strong functionality and performance. Most of these solutions are proprietary, which improves integration between tools by the same vendor but not with competing vendors. On the one hand, it improves the operations and support for ALM solutions. But on the other hand, it increases users’ dependence upon one vendor. Still, there is no doubt that the market for ALM solutions is fragmented, but emerging and more exciting products will be offered that will enable IT teams deliver faster-to-market, high quality software products.


"A lie gets halfway around the world before the truth has a chance to get its pants on. "

- Winston Churchill