METHODOLOGY PRINCIPLES

Any plan we develop should have the following attributes.  The various
phases should mirror these attributes, emphasizing the attributes most
relevant to that phase.

Widely applicable

The methodology should be usable by large and small projects: projects
developed over days, weeks, months, and years; single programmer
projects as well as multiple-team projects; and new releases as well
as original development.

Self-selecting

A good methodology will offer multiple paths to achieve the same
process goals.  Teams should be able to choose the path most useful to
their specific projects.  Parallel actions where possible should be
encouraged.  The methodology must not be viewed as a replacement for
management and common sense.

Formal/Explicit

Development teams should formally adapt and explicitly describe
methods to fulfill the requirements of each phase.  This should
promote good communications inside and outside the team

Goal oriented

The methodology should focus on goals not techniques, strategy not
tactics.  It should briefly describe what each phase requires and
promotes.

Interactive/Evolutionary

The methodology should promote re-evaluation of project goals and
strategies.  The methodology itself should be easily modifiable taking
into account past successes and failures and new circumstances.

Customer-driven

The methodology should allow teams to focus on the business needs of
the customers.  The methodology should let the team focus on the
project, not on the method.

Team supported

Teams need to support the methodology and should require its use.  The
major benefits of using a methodology must derive from the methodology
itself, not from external "payoffs."  The team should expect
management support for the method but individual commitment within the
team is more important.

Applicable to a wide variety of project management approaches

A methodology should be separate from project management.  The
methodology should not specify who should do what, when it should be
done, how long it should take, or what management approval and review
should take place.