|
The end of 2008 presents us with a very weak economy. We hear the words "economic crisis", "gloomy outlook", "recession", and "economic decline" in the news again and again. We are also seeing small to massive layoffs in a number of sectors and IT is certainly not immune. The question for those CM'ers in light of this economic downturn is how do I adjust my Configuration Management (CM) planning for the coming year when budgets are being slashed and projects are being cancelled?
Consolidate the Work Non-discretionary work is the core work that must continue to keep the company afloat or work that your company cannot live without. In the case of CM, an example of non-discretionary work is to maintain the code repositories and continue the builds and releases. While this is not a definitive list, it is important for you to identify what your non-discretionary list of work includes and be ready to explain the importance. We have to be cautious here because I have seen a few cases where companies think they no longer need CM at all (e.g., they consider it discretionary). This can be disastrous in the long run. However, the key takeaway is that there will be varying levels of CM understanding by your Senior Management so do not be surprised if they think they can cut something that may be critical to the integrity of CM. Be ready to explain the importance of what you believe to be the non-discretionary parts of CM within the company. Discretionary work is the work that improves the service or capability of the organization but would not impact the core running of the company if it did not occur. In the case of CM, this could be work to create a CM coop environment, to automate processes, and to introduce new CM tools. While this is not a definitive list, it is important for you to identify what your discretionary work list includes. As you list both the non-discretionary and the discretionary work, it is important to list the skills needed to complete the work. This will be important as you consider the staff needed to perform the work. Typically there is a need for more skilled resources to complete discretionary work since this typically involves designing, architecting, and scripting improvements and establishing new processes while non-discretionary work typically involves utilizing and repeating the processes already in place. Prioritize the Work
Rank the People CM Managers or folks who lead CM teams have to make the hard decision to rank order their staff based on their skills and experience. A good way to start this process is establish a skills matrix listing the various skills that are needed for CM work and indicate the level of experience the people have. A simple example of a skills matrix is:
As you review your skills matrix, you may also include another field (or column) and that is the cost of the resource. Unfortunately during a downturn in the economy, cost is a factor. However, I have seen in some cases where the reduction is more a factor of a headcount number than the cost of the headcount. If cost is the driving factor, then including the cost of the resource on this matrix is important. If the driving factor is number of headcount, then while it still may be a good idea to include the cost of the resource, the skills become more of a deciding factor. Within this framework, a senior person does not necessarily have precedence over a mid-level or junior person. This is because as you consider moving forward with less staff, it is important to align the staff with the work ahead. As an example, if you have to halt all discretionary work, then not as many senior skills are needed. Another example using the matrix above, Employee B appears to have better overall skills than Employee C. However, if the discretionary work of Makefile improvements takes a high priority, then Employee C with better Makefile skills may be preferred over Employee B. Advocate for CM Summary Mario Moreira is a Columnist for the CM Journal, a writer for the Agile Journal, a Technologist and Architecture, an Author, and has worked in the SCM field since 1986 and in the Agile field since 1998. He has experience with numerous SCM technologies and processes and has implemented SCM on over 100 applications/products, which include establishing global SCM infrastructures. He is a certified ScrumMaster in the Agile arena having implemented Scrum and XP practices. He holds an MA in Mass Communication with an emphasis on communication technologies. Mario also brings years of Project Management, Software Quality Assurance, Requirement Management, facilitation, and team building skills and experience. Mario is the author of the SCM book entitled, “Software Configuration Management Implementation Roadmap”. It can be found at www.wiley.com, www.wileyeurope.com, and www.amazon.com (search for Mario Moreira). It includes step-by-step guidance for implementing SCM at the organization, application, and project level with labor-saving templates on CD.
Set as favorite
Bookmark
Email this
Hits: 4952 Trackback(0)Comments (0)
|
||||||||||||||||
| Last Updated on Thursday, 23 July 2009 10:50 |


The end of 2008 presents us with a very weak economy. We hear the words "economic crisis", "gloomy outlook", "recession", and "economic decline" in the news again and again. We are also seeing small to massive layoffs in a number of sectors and IT is certainly not immune. The question for those CM'ers in light of this economic downturn is how do I adjust my Configuration Management (CM) planning for the coming year when budgets are being slashed and projects are being cancelled?

