Version Control

Ben Weatherall addresses what happens when large teams shrink to the extent that they are considered small. There are several situations where this commonly happens—for example, when a team has been raided by other teams, when the majority of the work has been accomplished and a large team is no longer needed, or when the corporate situation is such that downsizing occurs.

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.

Personality accounts for a lot. You can tell a great deal about how someone is going to handle a situation by understanding their personality. In fact, if you get really good at this game you can sometimes predict what they are going to do. Some people just can’t manage to the see the big picture, and that is often evident in how they approach their work, whether tactical project or a strategic product. If you want to be able to work with different personalities then you need to understand what motivates them to act, or in some cases, fail to act.

Companies that develop multiple products often struggle with how to ensure they all work together as a solution and struggle with how to get the deliverables from various products together into a working release. Project managers and product managers have other priorities to handle. So who handles a release that wrangles together multiple project deliverables from multiple products that define a solution or complex release? The answer is the Release Manager.