|
We believe that the only measure of a successful project is on-time and in-budget delivery of a quality product. Our Customer must be able to hold us accountable throughout the project, and at any point in the project, know what progress has been made and which milestones have been achieved. We believe that to manage Customers expectations the scope of a project must be well defined, deliverables previewed and the customer well informed. This requires a comprehensive project plan, clearly defined roles and responsibilities, quantifiable deliverables, good communication and cooperation.
Approach
A project plan forms the basis of all of our work. Project plans are structured in such a manner that different views are available to different levels of personnel in the project team. Higher-level views emphasize summary tasks, milestones and costs. Lower level views emphasize specific activities, resource assignment and estimated effort. Milestones form the basis of accountability and provide the customer with an easy point of reference for both progress and billing.
The scope of the project is reviewed and finalized during the project initiation to ensure that all parties clearly understand what will be included. The project plan is then finalized and a project base line defined in accordance with applicable Industry/ SSIPL standards (ISO 9001, ANSI, IEEE, DOE, Etc).
The project manager and an on-going assessment made as to impact on milestones track project progress against plan. Adjustments, where necessary, are made for internal challenges and delays, and the customer immediately informed of circumstances that might impact the timeliness of the project. The deliverables are previewed with the customer at the beginning of each major task to ensure that the deliverable meets their expectations.
A weekly status meeting is held with the customer and is attended by the Project Principal and / or Remote Project Manager. Status of all milestones and activities are reviewed, and activities for the next week previewed, Issues resolved, decisions and action items documented.
Communication
All communication will be via e-mail and/or hardcopy. The following documents will serve as standard forms for communication:
- Scope Definition/Impact Analysis
- Project Plan
- Project Design
- Meeting Agenda
- Status Report
- Meeting Minutes
We believe that a consistent, Quality Product is delivered by creating a technical work environment that promotes efficiency, has well defined procedures and standards, control changes, documents activities and leave a clear audit trial. We believe in automating those processes, which are labor intensive or error prone. We believe a good design is one that is simple, effective, easy to maintain and flexible enough to facilitate future changes.
Approach
Depending upon the size and scope, each project will be divided into four stages.
The Requirement Workshop- In these stages the Project Managers sits down with the client and in a series of workshops and develops the requirements. At the end of this stage, the requirement document is submitted to and approved by the client.
The Project Design- In this stage, the requirements are developed into detailed design specifications and may involve the active participation of the client, depending on the type of the project. The output of this stage is the project design and the technical plan, which are approved by the client.
The Development and Quality Assurance- These two phases are combined into one, as a quality assurance is implemented into every stage of development. At every stage in the object life cycle, it is reviewed by the team members and finally promoted to the user testing stage.
User Testing And Approval- After development, the objects are moved to the user test environment where they are tested and approved by the users.
Project Implementation And Project Approval- The approved object are promoted to production environment and after they have run successfully on production and the client having expressed his satisfaction, the project is signed off.
|