President and CEO of Neuma Technology, Joe Farah is a regular contributor to the CM Journal. Prior to cofounding Neuma in 1990, he was a director of software at Mitel. In the 1970s, Joe developed the Program Library System (PLS), still heavily used by Nortel (Bell-Northern Research), where he worked at the time. He's been a software developer since the late 1960s.
Joe Farah investigates whether or not software configuration management (SCM) follows the core principles of CM. The big difference in software shops and hardware shops is the level of automation in which the tools are responsible for ensuring the core processes reach “done.”
Joe Farah writes about the importance of software configuration (SCM) metrics. Software metrics help us build better software, and SCM metrics help us to better manage the built software. The metrics give you a better handle on what is really going on in your product development environment.
Joe Farah explores whether or not open source software configuration management (SCM) tools are causing SCM to regress. CM professionals need to do a better job of looking at what’s out there in the market before jumping ship to an open source solution.
CM is a lot like the space industry. But instead of Atlas, Delta, and whatever else is used to launch spacecraft, we have ClearCase, Perforce, and many other tools. Joe Farah explains that in order to advance CM, we need to know how to create a new CM infrastructure that goes beyond these tools.
Thirty-five years later and where are we in regards to software configuration management? Joe Farah takes us back to the late 1970s and compares the past with the present. If you look at a typical shop today, progress has actually gone backwards.
Joe Farah explains to what degree should SCM professionals be scripting experts. While high-level scripting for SCM professionals is great, you might need to rethink your technology so your CM team can do real work.
You have your hardware and your software configuration management departments managing the same product. Although their goals are the same, they often clash, but that doesn't mean you should separate them. Joe Farah explains how to properly maintain a single CM team.