Where does the acronym ALM (Application Lifecycle Management) come from?


I became interested today in where this ALM term comes from.  It is involved a lot with what Microsoft does on the Team Foundation Server (TFS) front and frankly, I’ve thought it to be just another marketing term for Software Engineering.  BUT, I wanted to investigate and dig deeper….

The best I can tell, the acronym ALM comes from PLM or Product Lifecycle Management.  The Wikipedia article on PLM has a good history of the term and how it came to be used at Chrysler in the mid 1980’s.  They basically started centralizing all designs, documentation, etc. of the Jeep Cherokee into one database to manage its creation.  Sounds a lot like ALM to me today.

It also makes sense that the term would come from manufacturing.  This article from 2002 talks about the transition in the manufacturing industry from Computer-Aided Design (CAD) tools to a more holistic approach of PLM.  There was also a boon of Computer Aided Software Engineering (CASE) tools in the 1980’s.  CAD leads to PLM.  CASE leads to ALM.  We both went from individual tools that did design, requirements, etc. and integrated them into one tool or system.  That seems to be the evolution.

The borrowing from manufacturing also makes sense as so much of Software Process comes from that industry. Kanban, Lean, CMMI, and on and on.  Deming, one of the greats in manufacturing process, is cited often in software process literature.

So there it is, ALM comes from PLM which all originated in the auto industry with the Jeep Cherokee.  Who would of thunk it? 🙂

Outline of MSDN Application Lifecycle Management Library for Visual Studio 2010


The navigation of MSDN is very bad currently and I get easily lost in all the content.  But the content is great!  So I’ve created a cheat sheet for myself that you might find handy too.  It is a four level deep outline of all the MSDN content under “Development Tools and Languages”->”Visual Studio 2010″->”Visual Studio Application Lifecycle Management”.  The table of contents is two levels deep and the actual document goes four levels deep.  Hope this helps!

MSDN Library – Visual Studio 2010 – ALM – 4 Level Deep Outline

MSF for CMMI Process Improvement 5 – Process Guidance in Word format


Well people loved the MSF for Agile Word doc that I posted so much, I thought I’d go ahead and post my Word doc of the CMMI process also.

I think the CMMI process gets a bad wrap because, well, it has the CMMI name in it. CMMI has become synomous with heavyweight, formal processes that developers hate, but this process is still iterative and lightweight. Plus it provides you with rich Work Items such as Change Requests (an almost necessary evil). So give it a go too, you never know… it might fit better than the Agile template!
MSF for CMMI Process Improvement v5 – Process Guidance

Updated it on 12/13/2010

MSF for CMMI Process Improvement v5 – Process Guidance