Methodology Design Principles I

by Jim Highsmith

Over the past 10 years, the word "methodology" has become associated with ponderous, heavyweight, rigorous, process-, and documentation- centric processes for delivering software. While this has become the perception, a methodology can -- and should -- be much simpler. Rather than be known for its elements -- process, roles, tools, practices -- a methodology should simply be described as "a framework to assist people in working together." People, not a methodology, develop software. However, when the numbers of people attempting to work together exceed a small group, a common basis for understanding can be helpful. But methodologists, like most specialists, tend to go overboard. Keeping a methodology simple and flexible is key to success.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Methodology Design Principles I 25 October 2001