alm

Bob Aiello explains that ALM and ITIL provide considerable guidance that can help you implement a comprehensive software and systems development lifecycle. Your organization would benefit from implementing these best practices, especially if you need to meet regulatory requirements or perhaps pass an internal audit once in a while.

Leslie Sachs discusses the key people skills essential to appreciating how and which personality factors most impact one's ability to successfully implement core build and release management practices.

This month’s topic is a paradigm shift that requires that we move from focusing narrowly on the CM function to the much broader Application Lifecycle Management (ALM) view. I know people who cannot make this shift. From a personality perspective, these folks have great difficulty seeing the big picture and the more comprehensive lifecycle view required by ALM. There are good reasons for these problems, and in this article we’ll examine the personality challenges inherent in shifting from CM into ALM.

Agile and ALM are two terms that you don’t often see side by side. To most developers, agile means team interaction, customer collaboration, dynamism, and responsiveness to change. In contrast, ALM seems to imply the opposite of agile, with echoes of rigid procedures, inflexibility, and top-down process control. But are the agile and ALM approaches as contradictory as they first appear to be?