For last few years or so, I have seen significant improvement in the field of configuration management. Globally many organizations realize its importance and take maximum advantage by adopting best practices and standards to accelerate their business performance. ‘Configuration Management’ plays an important role in any lifecycle of a project and directly impacts the company’s business.

Talking about a software project, I am of the view that whether a project is small or large, it can never be successful unless the application is properly managed, controlled and administered else it will become problematic to handle. This is because change in an application is always inevitable and must be properly managed by means of its type, revision history information, accessibility to the user and other parameters. As the development passes through different phases of a software life cycle, the need to control the system changes becoming more demanding and critical for stakeholders.

Today most companies rely on CM tools for managing their software changes especially in terms of source code level and perhaps they are quite successful maintaining and preserving the changes. Here again selection of the right CM tool is critical for organizations. Ideally the tool should be able to facilitate users working by in different ways such as providing integration support, build automation, parallel development and other parameters. This will help the development team in accomplishing their tasks quickly and effectively with more reliability. Availability of open source version controlling tools are easily available in wide range that can facilitate all major requirements for both small & large enterprises, so I think cost should not be prevent users from adopting CM tools. Indeed tools have made life easier for software development teams and created a sense of comfort for organizational stability.

Establishing corporate standards to define a common usage model will often be the deciding factor in whether or not your tools deployment will be a success.

One of the other ways of implementing a configuration management system is by means of using ‘Process’. The processes should define, although flexible so that it does not create a burden for the users. Process should never cover up all the basic requirements like revision history information, file current version, date modification, etc. Some tools are so complex that they can be difficult to navigate with a considerable amount of training. This approach will at least provide some sort of tracking to small teams working on small size of application but in each case tracking is mandatory and cannot be tolerated.

I think ideally the most effective and productive method of implementing SCM is the combination of both CM tools and processes. Effective processes will make a big difference to a user by providing a smooth flow of data, auto-generated emails, rich reports, reverse and forward tracking, code traceability, track deviation and many others. This means that your users will get a lot more work done.

Conclusion
There are lots to think about when you implement CM tools and process. Make sure that you remember to set a corporate standard and help your team achieve success!

TrackBack URI for this entry

Comments (3)

Subscribe to this comment's feed

Muhammad Saqib Khan said:

... Akmal: Yes, you are right and for beginning or introducing SCM in an organization, it is always better to pick up small parts or modules first and apply the best practices of CM. Slowly and gradually introducing new tools, improving working style and adopting uniform culture will really encourage CM implementation group to plan & finalize their strategy for accepting SCM importance & benefits in an organization.

report abuse vote down vote up

January 19, 2011
Votes: +0

Akmal Hussain said:

... Configuration Management is something where one can not replicate the same what he did earlier. Every time if there is different environment so there is different ways to implement as well. I agree with Muhammad Saqib Khan that it must be the combination of both but where I differ is the basic items. like other kind of implementation configuration Management is also require phases and for initial phase it is required to capture small things to show the benefits of configuration Management which will also improve the acceptability of development and other team members for later phases.

report abuse vote down vote up

December 30, 2010
Votes: +1

waseem shahzad bokhari said:

... Appreciating. Well , "Significant improvement" will definitely impart a Good change all over the IT Community.Article is comprehensively capturing the CM Approach at Corporate Standard.There is real need to concentrate on Process and Tools as well.Moreover there is OPEN DISCUSSION required at methodologies and technical level.I bet through mutual interactions and knowledge sharing ; "Significant improvement" is not far apart. Cheers

report abuse vote down vote up

December 14, 2010
Votes: +1