can’t just say “I want an Active Development Line” and change the codeline policy appropriately.
Putting it All Together
If you read this far you may be thinking “ Codeline Policy , and build issues, are SCM, but isn’t testing QA?” In a sense that is correct, but the fact that they are separated into two different groups is an organizational, and perhaps historical, artifact. In Extreme Programming teams developers write tests, and use version control, in addition to coding. There is a role for testing experts, ideally with that role fully integrated into the team, either as someone who helps customers write acceptance tests or as someone on the development team who helps developers with their testing technique. Likewise, there is a role for software configuration management in an agile project, and indeed, all projects would benefit by a more integrated view of SCM.
In addition to abstract benefits of understanding the global value of SCM solutions, implementing SCM processes with this in mind will make it easier for the entire team to embrace the SCM and appreciate the value that it adds.
Often we focus on our particular discipline and lose track of the goal of a software project: To build software that serves a customer’s needs. Testing, SCM, as well as coding should be part of every developer’s toolkit. Some will know more than others about a given discipline, but the disciplines need to work together well.
Acknowledgements: Ron Jeffries provided input into this article. To learn more about Extreme Programming visit www.xprogramming.com.