For a long time, (a really long time) the term Application Life-cycle Management (ALM) has bothered me. Why, because what we typically call ALM tools are tools that govern the development and delivery of a software project and that is only part of the life-cycle of an application. To really be ALM you would need to talk about the portfolio of apps (APM) and the management of those assets from cradle to production to (a place more should probably get to sooner) the digital grave.
During AADI we held a roundtable on ALM Practices and had a fairly quick conversation on this topic. The nut of the conversation is that no-one in IT uses the term ALM. Either SDLC (software development life-cycle) or more specific terms: requirements management, project management, defect management, etc. are used. There is a slowly emerging convergence of APM and PPM tools with ALM and a convergence between ALM and Release Management in DevOps that at some point may deliver a real “ALM” suite or solution set but the reality at this point is we probably should modify our terminology to say ADLM. I would love to get your input either here or tweet me @metamurph
Read Complimentary Relevant Research
100 Data and Analytics Predictions Through 2021
Over the next few years, data and analytics programs will become even more mission-critical throughout the business and across industries....
View Relevant Webinars
Digital Business Architecture: From Strategy to Guiding Execution
New techniques have emerged to help CIOs and EA practitioners leverage business architecture to guide investment and execution decisions,...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.