| CM Crossroads provides original content, articles and regular columns from industry thought leaders, analysts and software providers on a wide variety of configuration management and application lifecycle management topics. Below you will find links directly to our columns and articles or you may use the search box to scan for a particular topic or writer.
Subscribe to the RSS Feed 
|
 |
|
|
Written by Bob Aiello
|
|
 Small Teams require a different level of process than big teams – or do they? Is there really any difference between implementing SCM for small teams versus big teams? I have implemented SCM for some pretty large teams with 30+ plus developers in large organizations of 700+ developers. I have also worked on very small teams with just 2 or 3 developers. I like working on small teams because I usually get to do more - from the release management to testing to helping to debug the code. In some cases, I have found it very difficult to implement SCM in smaller teams, where there can be some pretty difficult challenges. You should never underestimate the difficulties you may encounter including resistance to change that you can encounter when you are working with a smaller team. Read on if you would like to be prepared for the challenges ahead in implementing SCM essentials for small teams.
|
|
|
Written by CMC Media Staff
|
Each month the CM Journal provides original content articles and regular columns from industry thought leaders and software providers on a wide variety of configuration management and application lifecycle management topics.
.
 Get the Feed
|
SCM Essentials for Small Teams
Volume 7 - Number 11 - November 2009
 Small Teams need Software Configuration Management every bit as much as big teams do. But it is also true that working in a small team brings its own unique rewards and challenges. Small Teams also create big systems that can have a major impact. I have seen large organizations that operated as a set of groups of small teams - each with their own culture and operating mode. This week our CM Crossroads writers give you the information that you need to be effective in small teams.
Ben Weatherall takes the lead with the first of a four part series on Small Teams and SCM. While Joe Farah gives us the Next Generation of CM for Small Businesses. Of course I don't want to miss the fun so you'll find my own trench level experiences with Small Teams described in Behaviorally Speaking. We also look back at Mario Moreira's article on Applying CM to Agile Teams and Pablo Santos Luaces also weighs in on three core pillars on SCM Essentials for Small Teams. Our own Chayim Kirshen wraps up this month’s theme with his great article on SCM Essentials For Small Teams.
I am pleased to announce that we have a new featured column starting this month on Implementing Industry Standards. My colleague and mentor, James W. Moore, who is the IEEE Computer Society's Vice-President for Professional Activities and a member of its Board of Governors gets us off to a great start with his three part series on implementing standards. James Moore is one of the most knowledgeable people in the standards community and someone that I go to for help in navigating the complexity of the standards world. We are very privileged to have him for this new featured column.
Bob Aiello
Editor in Chief
CM Crossroads
raiello@acm.org
|
|
Behaviorally Speaking – SCM Essentials for Small Teams
by Bob Aiello
Small Teams require a different level of process than big teams – or do they? Is there really any difference between implementing SCM for small teams versus big teams? I have implemented SCM for some pretty large teams with 30+ plus developers in large organizations of 700+ developers. I have also worked on very small teams with just 2 or 3 developers. I like working on small teams because I usually get to do more - from the release management to testing to helping to debug the code. In some cases, I have found it very difficult to implement SCM in smaller teams, where there can be some pretty difficult challenges. You should never underestimate the difficulties you may encounter including resistance to change that you can encounter when you are working with a smaller team. Read on if you would like to be prepared for the challenges ahead in implementing SCM essentials for small teams.
Read More >> |
|
|
|
|
Small Teams and SCM
by Ben Weatherall
This is the first of a four part series on Small Teams and SCM. The parts are (1) Small Standalone Teams, (2) Small Teams in a Large Organization, (3) When Small Teams Grow and (4) When Large Teams Shrink. All of these leverage an earlier article, Small Team Essentials: An SCM Perspective, previously published in the July, 2008 CM Journal.
Read More >> |
|
|
|
|
ISO/IEC/IEEE 12207 and 15288: The Entry-Level Standards for Process Definition - Part 1
by James W. Moore
In 2008, the 12207 standard for software life cycle processes and the 15288 standard for system life cycle processes were revised in an effort that finally harmonized system and software processes as well as bringing the respective IEEE and ISO/IEC standards into complete agreement. Some users mistakenly believe that these standards are targeted only to large organizations able to make a substantial investment in a complete suite of software and systems processes. However, these standards are also the best entry point for beginning users who desire guidance on as few as a single process. This three-part article will explain how entry-level users can apply the two standards.
Read More >> |
|
 |
CM: THE NEXT GENERATION of SCM Essentials for Small Business
by Joe Farah
Exactly how big is an organization supposed to be before CM must take an active part in the development team? The answer is simple. CM, properly adopted, gives an advantage to the small business that is necessary for it to compete. It doesn't really matter what size your company is, you still have to successfully develop, build, distribute and track your software. The fact that you're in a small business means you have less resources to do so. This is why CM is so crucial to small business.
Read More >> |
|
|
|
|
 |
Applying CM to Agile Teams
by Mario Moreira
A variety of Agile methods and practices have now been around for a solid 10 years and existed for at least another 10 years prior. Configuration Management (CM) for Agile development has now been discussed since the turn of the century. So what are the core principles of CM and how can CM help Agile teams?
Read More >> |
|
|
|
|
 |
SCM Essentials For Small Teams
by Chayim Kirshen
Small teams and small organizations tend to think of SCM as revision control, and software construction.SCM tools are reduced to the ability to check in and check out code. Teams rarely use the extended features and best practices of revision control systems, so let's review how more efficient revision control can help small teams.
Read More >>
|
 |
SCM Essentials for Small Teams
by Pablo Santos Luaces
Very small teams think that SCM (Software Configuration Management) is not for them. Even the name sounds like a big thing: CM, configuration management. "Why should I care?" They say.
Small teams code, and that's actually a very good thing. But they normally refuse to use the bare minimum to work, the three core pillars as I usually refer to: version control, task tracking and testing.
Read More >>
|
|
|
|
|
|
|
|
Written by Joe Farah
|
 Exactly how big is an organization supposed to be before CM must take an active part in the development team? The answer is simple. CM, properly adopted, gives an advantage to the small business that is necessary for it to compete. It doesn't really matter what size your company is, you still have to successfully develop, build, distribute and track your software. The fact that you're in a small business means you have less resources to do so. This is why CM is so crucial to small business.
|
|
Written by James W. Moore
|
 In 2008, the 12207 standard for software life cycle processes and the 15288 standard for system life cycle processes were revised in an effort that finally harmonized system and software processes as well as bringing the respective IEEE and ISO/IEC standards into complete agreement. Some users mistakenly believe that these standards are targeted only to large organizations able to make a substantial investment in a complete suite of software and systems processes. However, these standards are also the best entry point for beginning users who desire guidance on as few as a single process. This three-part article will explain how entry-level users can apply the two standards.
|
|
Written by Ben Weatherall
|
 This is the first of a four part series on Small Teams and SCM. The parts are (1) Small Standalone Teams, (2) Small Teams in a Large Organization, (3) When Small Teams Grow and (4) When Large Teams Shrink. All of these leverage an earlier article, Small Team Essentials: An SCM Perspective, previously published in the July, 2008 CM Journal.
|
|
Written by Bob Aiello
|
 Maven is a popular build framework that is used by many technology professionals to manage large scale java application development. The Apache Maven website (http://maven.apache.org) states that "Maven is a software project management and comprehension tool". Maven builds are based upon a project object model (POM) which is coded in XML. Maven is used to manage a project's build, reporting and documentation from a central place. I have worked with both Maven 1.0.2 and the very popular Maven 2. For this article I used Maven 2.2.1 on RHEL 5.3.
|
|
Written by Ben Weatherall
|
|
 As an industry, SCM is conservative – we hold the corporate jewels in our hands and we are reluctant to let either processes, procedures or personnel have a chance to mess them up. In fact, when they do get messed up we tend to lose our jobs. Then along came Agile and the need to support it while maintaining both technical and professional integrity.
|
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 1 of 114 |
Articles
