Project Management Plan

For

Job Portal System

Version 1.0 draft 1

Prepared by KRISHANTH R

SoftTech Services and Consultancies

16/7/2012

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page ii

Table of Contents
Project Management Plan.................................................................................................................i For........................................................................................................................................................i Job Portal System...............................................................................................................................i 1. Overview..........................................................................................................................................1 Braude, Eric J., Software Engineering: An Object Oriented Perspective. Wiley, 2001............3 Case Study: SPMP for Encounter video game ref: http://www.wiley.com/college/braude......3 IEEE Document Standards published in IEEE Standards Collection. 2001 edition. ...........3 Major field test administered by the ETS: http://www.ets.org/hea/mft/index.html..................3 Martin, Dr. Dennis S., Documentation Standards. Jacksonville State University, 2003: http://mcis.jsu.edu/faculty/dmartin/cs521.html..............................................................................3 Pressman, Roger S., Software Engineering: A Practitioners Approach. McGraw-Hill, 2001. 3 2. Project Organization......................................................................................................................4 3. Managerial Process Plans..............................................................................................................4 4. Technical Process Plans.................................................................................................................6

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 1

1. Overview
1.1. Project Purpose, Goals and Objectives

The Job Portal Project Plan will provide a definition of the project, including the projects 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.

The Project Plan defines the following:

Project purpose Business and project goals and objectives Scope and expectations Roles and responsibilities Assumptions and constraints Project management approach Ground rules for the project Project budget Project timeline The conceptual design of new technology

Project goals and objectives:

Ensure that end users have input into the design process. Accomplish project business goals and objectives within defined budget and time parameters. Minimize impact to standard business operations within the affected units. Craft a favorable and secure agreement between the Department and the selected vendor.

1.2.

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.

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 2

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. This project proposes a system for use on a Personal Computer using a Visual Interface and the Microsoft Access database management system. Major functions that will be provided by the system include: logging into the system, importing answer keys and student test answers, grading tests, generating a report of test results and printing reports upon demand. The MCIS department will use the Major Field Achievement Test to gauge the overall performance of its students in the computer field. This project will deliver a working system that provides results of such tests not only for evaluating the student but also for using such information by the department for its improvement. A project like this is an excellent opportunity for the author to have a real world experience while testing and implementing the knowledge that was gained during the Masters program and especially undergoing the Software Engineering courses. It would be worthwhile to use the experience that the author had gained experience working on databases. The MCIS Department can assess its performance and use this information for its process improvement as one of the steps necessary for accreditation of the program.

1.3.

Project Deliverables

The list of project deliverables is: Project Management Plan Software Requirements Specification Software Design Description Software Quality Assurance Plan (including the Software Verification and Validation Plan and the Test Design Document) Working System with an Access Database Final Studio Document

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 3

1.4.

References
Braude, Eric J., Software Engineering: An Object Oriented Perspective. Wiley, 2001. Case Study: SPMP for Encounter video game ref: http://www.wiley.com/college/braude. IEEE Document Standards published in IEEE Standards Collection. 2001 edition. Major field test administered by the ETS: http://www.ets.org/hea/mft/index.html Martin, Dr. Dennis S., Documentation Standards. Jacksonville State University, 2003: http://mcis.jsu.edu/faculty/dmartin/cs521.html Pressman, Roger S., Software Engineering: A Practitioners Approach. McGrawHill, 2001.

1.5.

Definitions and Acronyms

Term Description Computer Information Systems program within the MCIS Dept Capability Maturity Model Integration Computer Science program within the MCIS Dept Educational Testing Services Also a program within the MCIS Dept Mathematical, Computing and Information Sciences Department Major Field Achievement Test Relational Database Management System. Software Configuration Management Plan Software Design Document Software Quality Assurance Plan Software Requirement Specification. A person, group or organization with a stake in the outcome of an application that is being developed. To be decided

CIS CMMI CS ETS Mathematics MCIS MFAT RDBMS SCMP SDD SQAP SRS Stakeholder TDB / tbd

1.6.

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.

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 4

2. Project Organization
2.1. External Interfaces

There are no external interfaces for this project as this project is developed for lab purposes. The one external interface would be my advisor who guides me in this project.

2.2.

Internal Structure

No internal structure as the project is developed by a single person.

2.3.

Roles and Responsibilities

The software developer is responsible for all documentation to be developed and for all work to be done.

3. Managerial Process Plans

3.1.
3.1.1

Start-Up Plans
Resource Acquisition Plan Development resources: The software and hardware tools required to execute the project are one computer with windows operating system with network connectivity. Software IDE used is visual studio 2010 with Microsoft SQL and a web server. Test resources: the software and hardware tools required to test the software and integrated products are Rational Rose Enterprise Edition Test Suite. Product resources: memory, disk, and other resources required by the final product are a CD or a flash drive to copy the final product. A web server to host the website.

3.2.
3.2.1

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.

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 5

3.2.2

Schedule Control Plan

If the work scheduled in previous section is gets behind, the developer is ready to spend extra time on the project in between and after the schedules and also during July to October to make up for the lost time and deliver the final project on time. Figure 1: Schedule Item Software Project Management Plan (this document) Software Requirements Specifications Software Design Document Software Quality Assurance and Verification & Validation Plan Studio I Presentation Updated SPMP Database Software Testing Description System Integration Final Studio Paper 3.2.3 None. 3.2.4 Communication, Tracking, and Reporting Plan Budget Control Plan Due date July 17, 2012 July 27, 2012 August 18, 2012 September 05, 2012 September 15, 2012 September 20, 2012 October 08, 2012 October 18, 2012 November 22, 2012 November 25, 2012

The updated SPMP will be circulated as mentioned in schedule of previous 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 saved for future purpose.

Type of Communication Status Report Schedule and Effort Tracking Report Project Review Risk Mitigation Status

Communication Schedule every Friday weekly

Typical Communication Who Initiates Recipient Mechanism team meeting Project Manager Project Team email Project Manager Program Manager

monthly face to face Project Manager Project Team as mitigation email responsible Project Manager actions are team member completed Requirement as changes are email and change CCB Chair affected Project Changes approved control tool Participants Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved. Supplier at project life cycle videoconference Program Project Manager, Management gates Manager Program Manager, Review Subcontract Manager

Project Management Plan for Job Portal System

Page 6

3.2.5

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.

3.3.

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.

3.4.

Project Close-Out Plan

All the details about the post-mortem debriefings, report on the lessons learnt, project objectives and the milestones achieved would be mentioned as part of the final studio paper at the end of the august. At the end of the October the developer will provide the committee with electronic version of the project code and documentation for future reference and maintenance purposes.

4. Technical Process Plans

4.1. Process Model

The MFAT grading system for MCIS will be implemented and executed using the Waterfall Model and prototyping.

4.2.

Methods, Tools, and Techniques

Refer to previous section (process model) for a description of the process. This process is described in [Braude] Software Engineering: An Object Oriented Perspective. This project adapts the system for use on a Personal Computer using a Visual Interface that would be built using Visual Studio 2010, .net technology and Microsoft SQL as its database management system. The tool for the statistical analysis is undecided at this point of time and would be mentioned in the updated version of this document.
Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.

Project Management Plan for Job Portal System

Page 7

4.3.

Configuration Management Plan

All the project deliverables are to be considered as configuration items. The configuration item as well as its file would be named after the document like SRS, SDD and followed by the version number. For example, all the preliminary versions that are submitted to the advisor for review would be named with the abbreviation followed by 0.1, 0.2. After the advisor approves the basic SPMP, this baseline document will be version 1.0 and is distributed to the committee members and stakeholders. Informal updates with the advisor will be numbered with 1.1, 1.2, etc. and the next full distribution to the committee would be version 2.0, etc.

4.4.

Quality Assurance Plan

A Software Quality Assurance Plan will be developed following recommended departmental standards.

4.5.

Documentation Plan

The IEEE standards would be followed for all documentation purposes. All the documents would be discussed and reviewed with advisor before their baseline versions are issued and distributed to the members of the committee on the due dates mentioned in schedule section for delivery dates.

4.6.

Infrastructure Plan

The hardware resources are two 333MHz Pentium computers running Windows 95 / 98 / 2000 Operating System. Each of these computers should have at least 128 MB RAM and a minimum of 4 GB of disk space.

4.7.

Product Acceptance plan

The committee will test the final product / application for acceptance.

4.8.

Process Improvement Plan

None, this is a single software development experience and the lessons learned will be included in the final studio document. Revision History Name Krishanth Date Initial draft Reason for Changes Version 1.0 draft 1

Copyright 2010 by SoftTech Services and Consultancies. All Rights Reserved.