I’ve been struggling with the phrase, “application lifecycle management” (ALM), for some time now. The term has been used to describe processes, tools and practices, but what exactly does it mean? Colleen Frye helps clarify with a 3-part series of stories that she’s written for SearchSoftwareQuality.com.
She starts by describing roles and responsibilities in an ALM-focused organization. As seen with agile methodologies, the focus is shifting towards increased communication and collaboration throughout the entire lifecycle. “While some of the lines between jobs are blurring, ALM is really about knocking down the walls between silos,” writes Frye.
In Changing industry roles in ALM-focused organizations, Frye continues the exploration of ALM roles and how those may differ from traditional environments. The changing roles of project manager, business analyst, architects, QA and test are discussed as well as examining a new role, that of an ALM specialist.
In the last of the series, How ALM development tools impact team work, Frye talks about some of the characteristics of ALM tools. Tool integration is a common theme as well as more automation of reporting and project status. However, again, emphasis is primarily on tools that allow for collaboration, communication and the breaking down of silos.