PROJECT MANAGEMENT SERVICES

Open Web Applications Services follows strict project management methods. Our experienced project managers make sure that we fully meet the goals and objectives of the open source solution that we offer to our customers. At Open Web Applications we know that successful projects are based on: 

• Strong understanding of our customer’s needs
• Careful planning and budgeting
• Clear and  transparent communication
• Quantifiable scope, time, cost, and quality goals

Open Web Applications Services employs an iterative process to project management that is conducive to customer feedback at every phase of the project. Our experienced managers will perform the following activities during each of the five phases of the project:

(1) Project initiation

1. Interview all key participants from our customer side and / or third party sides.
   1. Form a domain specific knowledge base.
   2. Gather requirements.
   3. Advocate the project to the customer management team.
2. Requirement Analysis
   1. In-depth study and a gap analysis of the customer’s requirements
   2. Create a functional specifications (FS) document.
3. Obtain customer approval of functional specifications.
4.  Architecture and Design. Based on the approved functional specifications an architecture and design (AD) document will be created. This document will specify all the software and hardware components and their interactions. This document also shows how all software and hardware components integrate in to the customer's existing information technolgy infrastructure. Obtain customer's approval of the architectural document.

(2) Project Planning

1. Together with the customer establish a procurement strategy for all software and hardware components of the project.
2. Analyze labor and materials requirements and produce a project budget (PB) document.
3. Perform risk analysis, look at the worst and best case scenarios.
4. Create a project plan (PP) that contains
   1. Clear and realistic time lines and interdependencies
   2. Well defined and quantifiable milestones
   3. Go / no go criteria specifically related to scope and quality
5. Obtain customer approval for both the project budget and the project plan.

(3) Project Execution

This phase includes activities such as:

1. Prototyping.
   1. Allows the customer to get a fill on how the end solution is going to look like.
   2. Modify the FS, and AD documents based on customer’s input.
2. System Integration. Stage all software and hardware components of the project.
3. Customizations. The open source applications will be modified to meet all needs specified in the FS document. We develop software based on the Agile Development principles. For more information please visit our Custom Software Services section.
4. Data Migration.
5. Testing.
   1. Create test documents and communicate them to the customer.
   2. Perform tests at each stage. Present test results to the customer.
6. Training.
   1. Create training documents.
   2. Train customer’s personnel.

(4) Project Monitoring

1. Establish timely ant transparent communication with all parties involved in the projects
2. Make sure that all goals from the project budget and project plan documents are met.
3. Conduct periodic review meetings with all parties involved.
4. Take timely actions to solve all problems that may occur during the project.

(5) Project Closing

1. System Integration. Integrate the open source solution with the customer's existing information technlogy infrastructure. For more information please visit our System Integration Services section.
2. Together with the customer create final acceptance test (FAT) documentation.
3. Together with the customer perform the final acceptance test. Create a final acceptance test results (FATR) document.
4. Obtain customer’s approval on final acceptance test results.
5. Projects Ends.