METHODOLOGY
It is a well-documented belief that the failure to develop and document good requirements specifications is the major cause of project failure. By utilizing baseline management rules of project management, we are attempting to get a leg up on the success of this effort, beginning with our development methodology.
As illustrated in the following diagram, our model is based on the "waterfall" lifecycle model, with a strong emphasis on communication, which is represented by each arrow.
This diagram is intended to show our understanding that every step forward may involve moving backwards for testing, changes and analysis, and that by completely understanding the specifications of a project up front it becomes possible to mitigate backward effort.
From a process prospective, the project management ownership is clearly defined in a kick-off meeting where the team outlines the following:
- roles and responsibilities for key project personnel
- project monitoring and review process
- escalation procedures
- changement management process
- frequency and reporting methodology for project status meetings
info@webtraverse.com
 |
|
|
|
