Conventional development methods move sequentially through the six phases of development.
The disadvantages of this sequential approach are:

• When one phase is active, little or no activity happens in the other phases, resulting in delays.
• Earlier phases do not use information gained in later phases until the start of the next development project, leading to substandard software solutions.
• Developers may rush through or completely skip entire phases (such as needs gathering, design, and/or evaluation).

The McWest Method groups the six phases into two sub-cycles.
The ANALYSIS sub-cycle answers the question "What needs must the software meet?", involves Problem Statement, Needs Gathering, and Evaluation.  The PRODUCTION sub-cycle produces the software, involves Design, Implementation, and Testing.  These two sub-cycles are:

• Coordinated:  The design phase of PRODUCTION meets needs identified during ANALYSIS.  The Evaluation phase of ANALYSIS validates that the implemented software solves the business problem.
• Iterative:  A sub-cycle completes many revolutions during the project.  Each ANALYSIS iteration gathers increasingly specific needs.  Early PRODUCTION iterations produce the architecture (partitioning, data structures, processes and development tools), later iterations specify and implement the software.
• Concurrent:  Both sub-cycles can be active at the same time.  This accelerates software development.  PRODUCTION starts with a list of general needs and ANALYSIS validates the software from early prototype through finished product.

The McWest Method is:

• more effective than traditional methods.  As needs are identified, they are immediately prioritized in light of the business problem.  Prototype implementation and testing give rapid feedback on the feasibility of specifications.
• compatible with both structured and object-oriented methods.
• client-focused.  McWest provides written guidelines (including examples) and mentoring for all aspects of the McWest method.