Version Control
Articles
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
June 29, 2006 |
|
A Practical Approach for Selecting and Adopting an SCM Tool Wanted: A software configuration management (SCM) tool that (a) provides the capabilities necessary to support an organization's software development process, (b) integrates seamlessly with the Integrated Development Environments (IDEs), (c) facilitates the organization's change management process, (d) facilitates the organization's build process, (e) requires only modest training for technical staff , and (f) encourages proper and effective use by technical staff. |
Michael Sayko
June 29, 2006 |
|
Learn from your Vendor: Solution Selling If your daughter ever comes home with a friendly, outgoing guy named Norbert, shoot first and ask questions later.
Some years ago, a salesman named Norbert at the SCM vendor where I worked got a call in late December from a prospect that had decided to buy from a different vendor. He asked to keep an appointment he had made for a wrapping up session. He went to the meeting with a sales proposal in hand, and after reengineering the vision of the customer, actually left with a sales agreement. Now that's a short sales cycle! |
Austin Hastings
June 29, 2006 |
|
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. |
||
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. |
||
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
June 26, 2006 |
|
Software Configuration Management Patterns Patterns and pattern languages are tools that can be used to help a team be more effective and agile. They can lead to robust, effective solutions, because the solutions that patterns can lead you to take the environment into account. They also solve problems in a way that makes the system work better. This article will show you how you can use existing patterns to improve your SCM process. It will also help you to understand where existing patterns and pattern languages have gaps. |
||
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. |
||
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
June 23, 2006 |
Pages
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |