Change Management

Articles

Applying Agile SCM to Databases

Many applications have database components, and these components evolve in the same environment as your code and other development artifacts. This article explores some of the issues around applying version management to database development in an agile environment. The article raises more questions than it answers, and we hope that it starts a dialogue about this important, yet often neglected topic.

Strategic Weakness: SCM Implementation Risks

The best way to make a project succeed is to communicate effectively. When all levels of the project share the goals, vision, constraints, and plan, everyone on the team can pull as hard and as creatively as possible in the right direction. Failing to share the goals and vision underlying a software configuration management (SCM) implementation can cause it to fail.

Austin Hastings
Continuous Staging: Scaling Continuous Integration to Multiple Component Teams

This month we will discuss some of the difficulties encountered when attempting continuous integration for multiple component teams working together to develop a large system. We describe the concept of a staging area to help coordinate the teams and stabilize the interdependencies between built versions of components.

A Target Approach for who should Manage Change

The activity of managing change is known as Change Management.  Managing change is typically very challenging and may occur at many levels within a workplace.  A key when implementing a change management process is truly understanding what should be managed and by whom.  For the sake of argument, I will refer to the group that manages the change as the Change Control Board (CCB).  However, there are other names used to represent this group (e.g., Configuration Control Board, Governance Board, etc.).  It is important to understand that while I use the phrase "manage or control the change", a CCB may not really control the change as much as acknowledge the change and apply impact analysis for the change in order to determine the best deployment guidance for the change.

Mario  Moreira's picture Mario Moreira
Anti-Patterns of Change Control

Change control is a configuration management process used to manage changes to important baselines like requirements and production. Change control may be considered a critical practice in that it often can be used to manage critical items within a project lifecycle, an application lifecycle, or the organization. It can be challenging to implement change control effectively. Often the reason why is because there is an anti-pattern (poor unworkable solution) in place.

 

Mario  Moreira's picture Mario Moreira
Best Practices of Agile SCM

There is a good amount of training, discussion and many articles concerning software configuration management (SCM) standards that tell us to implement configuration identification, status accounting, routine auditing, etc. All of this information is good and very important because it helps us understand the overall objectives. Rarely, though, do you find real tangible approaches for "how" to actually implement solutions that accomplish the objectives. This article will discuss a typical SCM Implementation engagement focusing on some practical best practices in order to achieve the objectives of the many CM standards out there. These best practices won't apply to all situations.

Golden Patterns and Symmetries in Concurrent Development

Patterns have provided a means of capturing recurring themes in software development and have been successful utilized to describe a number of software configuration management (SCM) practices [1, 2]. This article explores a higher-order pattern in concurrent development - more subtle and potentially powerful because of its applicability at a number of different levels of granularity.

Louis Taborda
Variation Management in Software Product Lines

Configuration management for a software product line is a multi-dimensional problem. In addition to the conventional configuration management problem of managing software variation over time, software product lines introduce the additional problem of managing variation among the different products within the application domain space of the product line. Thus we have a configuration management problem in both time and space.

Charles Krueger
The Risk of Regression

“But it was just a tiny little change! How could we have known it would cause such big problems?” Regression (going backward) is a fact of life in software systems. Even though something worked before, there is no guarantee that it will work after the latest "minor" change. Yes, modular design and sound system architecture can limit the likelihood of unintended effects, but they won't eliminate them all together.

Alan S. Koch
P-P Matrix for panoramic view of Process Compliance

‘It is easy to get success but the challenge is to stay on with it,' the commonly referred quote for personal development, when seen from a business perspective it explains the need for holding on to successes in business and thereon driving growth . In other words it calls for standardization and a smooth flow of activities for running the business.

Balaji OS's picture Balaji OS

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.