Mechanism for Project Management
Al-Abdullatif Information Technology Like most software companies is looking to satisfy her clients. Although there are many factors that bear on customer satisfaction, there is no doubt that delivering the product on time with the required level of quality is the main factor. In order to achieve this, was to be existence of an effective methodology for project management to achieve the required objective, which is customer satisfaction.
And based on this contract has been signed with the Centre for Assessment Software Engineering (SECC)which is a government agency designed to support software development and raised the level of local industry to make them able to compete in global markets
And we have been able to get on the second level of quality model (CMMI II) as an initial stage and we are in the direction of access at the third level and it would be easy to progress from Level II to Level III and will not require further adjustments to the company’s methodology for project management where we have applied in advance in cooperation with the Assessment Centre Software Engineering (SECC) SPIG model to improve the production process , which includes most of the processes and practices of the third level of quality model (CMMI III).
The following are simplified explanation of the methodology for project management from project initiation through to delivery and final closure of the project: -
1- The project initiation
The project will start by an assignment from senior manager to project manager.PM performs his activities during project lifecycle according to AIT standards.
2- Customer requirements gathering
According to a predefined requirement elicitation plan, analyst identifies customer requirements.
3- Supporting activities
The project manager selects members of the team to be responsible for the supporting activities and the authorized persons plan to perform these activities
Configuration Management
- According to a predefined CM plan, CC (configuration controller) creates a detailed structure of the project, determines access writes according to the levels of security required, mange backups and recovery during project lifecycle
Peer Review
- According to a predefined PR plan, work products are peer reviewed during project lifecycle. Peer reviews goals are to detect and remove defects from work products early
Measurement
- According to a predefined measurements plan, measures are collected and analyzed resulting in decisions to improve performance.
Quality Assurance
- According to a predefined QA plan QA engineer perform audit on project’s activities to help the management ensures that these activities are complying with the organization’s applicable processes and standards.
4- Estimation of the project
The project manager estimates the project in terms of time and cost. We have various estimation methods. Based on project nature, PM selects the best method suits the project.
5- Risk Management
All probable related project risks are determined to be monitored and controlled during project lifecycle.
6- Finalize project plan
At this stage, PM reviews all project supporting plans to assure the consistence among them, take senior manager approval and staff commitments on plan.
7- Analysis of customer requirements
The purpose of the analysis procedure is to further understand the requirements to resolve conflicts and inconsistencies (if any) and to ensure that they meet the required quality attributes and reflect the customer needs.
8- Preparation of the system & acceptance tests
System&acceptance tests are a set of tests designed to run on the final system in the user environment.
9- System design
The purpose of this procedure is to develop a general perception of the system being implemented by creating the ERD entity which illustrates the flow of processes in the system and the relationships among them
10- Integration test preparation
Integration tests are a stage of software testing in which units and individual program are combined and tested as a group. These types of testing are performed after unit test cases execution and before system&acceptance test cases execution.
11- Programming and coding
The purpose of this procedure is to transfer the detailed design into programming code according to AIT standards.
12- Unit test preparation
Unit test is a procedure used to verify the authenticity of the work of a particular module. In which each part of the program is isolated to show that the individual parts work correctly as a first step to implement the integration test cases and procedures. The implementation of this type of testing by developers and not by end-users
13- Testing execution
Test cases and procedures with all levels (unit, integration, system and acceptance) are executed according to predefined test plans; defects are recorded, analyzed, prioritized, delegated to developers and tracked to closure
14- Deliver to customer
Delivery to the customer is the procedure of the compilation of the executable code and any documents related to final products or components of other software
These activities will include a range of activities and procedures in support of software products which are:-
1- Customer related meeting and reports:-
- Periodic meetings are conducted to give customer insight to the project activities being implemented and let him follow up the project progress.
2- Scope control:-
- Identify changes required and analyze its impact on project scope, project size, effort, schedule and then evaluate the change to make the go/no-go decision (approve/reject)
15 - Project closure
- Dentify lessons learnt from the project which are collected through the tracking reports prepared during project cycle
- Conduct a meeting with project team to analyze the project data (measurements) and explain the project experiences and lessons learned
- Propose necessary amendments on the production process to increase business productivity of the project team