|
|
Complete control over all phases of the project life cycle, following
the best practices of the Project Management Institute. |
|
|
Identification of all risks associated with the project, together with
probability of each risk occurring and impact to the project if it
occurs. Development of a risk mitigation strategy for each
identified risk. |
|
|
The
use of best-practice methods for gathering business requirements
and business rules (including interviews, requirements meetings and
brainstorming). |
|
|
Correct assessment and analysis of business requirements
and business rules. The use of business process flows, use
cases, scenario flows in documenting requirements, with the goal of
obtaining 100% consensus from the Business owners before development
starts. |
|
|
A realistic project
plan defining project scope, goals, tasks to be accomplished, timelines, resources
required, and a projected ending date. (Well-defined timelines for design,
analysis, prototyping, development, system testing, user acceptance, implementation and
post-implementation phases). |
|
|
Thorough definition of
system architecture to be used to accomplish project goals. |
|
|
Thorough data analysis
of existing databases and/or complete data modeling. |
|
|
Complete system design
delineating all processes and data elements, and/or graphical object model. |
|
|
Gradual completion of
all phases of the project, with full accountability for work produced at all levels. |
|
|
Control over "scope creep". A well-established Change
Control process designed to handle proposed changes to the requirements. |
|
|
The
use of Earned Value methods for keeping the project on-time and within
budget. |
|
|
Thorough system
testing of all parts of the system, using all possible scenarios. |
