This post is the first in a series of six that will take you through the bpost iHRM (integrated human resource management) program. With this series we want to provide some context on the program itself and highlight our contributions and approach on business architecture and project scoping.
Does the term "rewrite" scare the bejeezus out of you? Good. It should. A rewrite is not something to be taken lightly and should be your very last resort. There are less painful routes you can take, but what if there really is no valid alternative to "The Big R"?
In the end, Application Lifecycle Management helps you to transform business ideas in an efficient and predictable way. You, as an IT department, will be able to deliver what the business needs. Moreover, you will be able to do this on time and within the estimated budget. The ALM maturity assessment discussed in my previous post results in a clear overview of the current maturity level (per discipline) and a phased plan to increase the maturity of you ALM processes. In this post we will discuss the possible benefits of executing an ALM maturity increase plan (by using a concrete customer case).
In my previous post I have shown a number of possible pain patterns that you can experience if the maturity of your ALM processes is not adequate. In this post we will discuss a method that can be used to assess these processes and increase the ALM maturity in the areas where this is needed.
The actual goal of Application Lifecycle Management (ALM) is to transform a business idea into working software as efficiently as possible. The requirements need to be aligned with development to build applications that drive business objectives.
Your ALM processes should be managed as actual business processes because they create the predictability that the business is requesting.
In reality they are still considered to be an IT internal concern.
Do you recognize any of the following pain patterns?