05-10-2012, 05:43 PM
Project Management Plan For Job Portal System
Project Management.doc (Size: 143.5 KB / Downloads: 38)
Project Purpose, Goals and Objectives
The Job Portal Project Plan will provide a definition of the project, including the project’s goals and objectives. Additionally, the Plan will serve as an agreement between the following parties: Project Sponsor, Steering Committee, Project Manager, Project Team, and other personnel associated with and/or affected by the project.
Scope
The CMMI is a model for improving and appraising the performance of development organizations. It stands for “Capability Maturity Model Integration”. It is published and developed by the Software Engineering Institute in Pittsburgh, PA. The CMMI is best known for its five levels of organizational maturity namely initial, managed process, defined process, and quantitatively managed process and optimizing process. Each level represents a coherent set of best practices organizations are expected to implement as they become better at what they do.
CMMI methodology at Level 5 (optimizing process) of requires that an organization assess its performance against certain parameters and use this information for process improvement. This applies to university programs as well as to the software development organizations.
For Computer Science there is a nationally nor med test developed by the Educational Testing Service, which will provide comparative national results. Dr. Martin had suggested that the Computer Information Systems (CIS) program at Jacksonville State University needs something similar to this. The test would have to be based on multiple-choice type questions and cover the entire course curriculum. It would have subparts covering the main areas of CIS to allow for more specific evaluation of the curriculum. The department also feels the need for a locally written test in Computer Science that has a similar sub area structure. The objective of the new system will be to provide an efficient way to grade and report results for the MCIS MFAT.
Evolution of the Plan
The preliminary drafts of the Software Project Management Plan will be submitted to my advisor for approval. For configuration management, configuration management plan. Every team member will review the plan every time the product requirements specification or certain other major project artifacts are updated, or when project constraints or resources change.
Control Plan
Requirements Control Plan
When changes are to be made in the requirements after the SRS has been released, the changes shall be brought to the attention of the committee and discussed. Any changes that are to be made will be with the prior approval of the committee and only if feasible and permissible within the constraints of the project mentioned in previous section and resources in terms of knowledge and skill of the developer required. Once the changes have been made to the SRS document, an updated version of the SRS shall be released and circulated to the committee. However, no changes shall be made to the requirements once the SDD is completed.
Reporting Plan
The updated SPMP will be circulated as mentioned in schedule section . Each of preliminary versions of all the documents and updates and status reports will be sent and discussed with the advisor and upon approval the approved document will be circulated to the other members of the committee. The report on the status of the project will be sent to the members of the committee at the beginning of the second semester of Studio.
Risk Management Plan
Risk # 1 “Deficiency in the knowledge and understanding of the problem and its solution” indicates that the developer does not have the complete understanding of the problem. This will affect the quality of the project in terms of requirements of the product and their fulfillment, which is not desirable. Building a prototype for the project model and doing an extensive literature search can overcome this. This will help the developer in delivering an efficient and quality product.
Risk # 2 “Lack of Skills and knowledge of tools needed for statistical analysis”, which means that the developer does not have knowledge about the tools and knowledge of working on statistical analysis. In this case, the developer is expected to update his / her knowledge of tools available for this purpose and decide the one that will be used in the project and master it. The developer may consult the faculty and other members of the committee especially, Dr. Jane Case for this purpose.