`

Name: Harsh agarwal Subject: Project Management Division B Roll no: 105 MBA in E & FB

TOPIC: Software for online registration of students with private schools affiliated to CBSE boards.

Preface
Scope This is the Project Management Plan for the Online Registration of students for Government school

1 Overview
1.1 Project Summary

1.1.1 Purpose, scope and objectives The objective of the project is to develop a software to streamline registration processes for students registering for admission in various private schools and allow ease of access to information for Institute personnel and Professors. The final product to be delivered to the client is a web-based application written in visual basic with a back end MS Access database. Ease of access to information Workflow capability between CBSE board and Private schools. Web based application Web based reporting capability Functional and Technical Documentation Training

1.1.2 Assumptions and Constraints Assumptions and Constraints upon which the project is based are as follows: All necessary funding will be made available for the entire life of the project All resources both internally and externally which are identified up front and through out the entire project will be dedicated 100% for the life of the project on an as and when required basis. Interfaces to other systems and/or products will be established at the beginning of the project and access to resources who are subject matter experts for those interfaces will be identified and dedicated on an as and when required basis for the life of the project All necessary hardware/software will be purchased through a master standing offer to expedite purchasing for the purposes of this project and implementation of this hardware and software will be done in conjunction with technical experts for both external and internal interfaces where necessary.

1.1.3 Project Deliverables Registration System Source Code Software/Hardware Technical / Functional Specifications Documentation:

Responsibility Project manager will be responsible for ensuring that all key deliverables are met within time, cost and performance constraints of the project and that she will adhere to proper quality control mechanisms and standards. The project manager must work closely with the line managers to ensure that all assigned resources are effectively and efficiently utilised and that the project is properly resourcd with both internal and external resources. In addition, the project manager is responsible for: 1. All formal communication between the functional and technical areas. 2. Preparation of the project plan with sign-off between the functional and technical areas. 3. Preparation of all project data items 4. Regular status reports and updates to executives 5. Ensure that all employees and functional managers are kept informed and up-to-date as to what their responsibilities are in relation to the project 6. Budget tracking actual against estimated. 7. Maintenance of the project plan that dynamically shows the projects time, cost and performance and resource commitment. 1.1.4 Authority To ensure that this project meets its objectives, PM( Project manager) is authorised t manage the project and issue directives in accordance with the policies and procedures of the CBSE board. The project managers authority also includes: 1. Direct access to the client on all matters 2. Control and distribution of all funding associated Project including procurement as the project authority. 3. To revise the project plan as needed and with client approval 4. To monitor the time, cost and performance activities and ensure that all problems are promptly identified, reported and solved.

2 Project Organisation
This structure applies throughout development. Generalrelationships will vary with the Project Team: Titles and Structure organisation, but the roles will remain the same. In particular, leadership and accountability must lie with the project manager, working in close collaboration with the System Manager. A successful project is always managed by an individual, not committee

Project Steering Committee Committee

2.1 Roles and Responsibilities

2.1.1 Project Team: Roles and Responsibilities System Project Manager Manager 2.1.1.1 Project Steering Committee: Made up of the IS manager and representatives of users affected by the project (middle management or higher) System Management Membership is about 5 people & Development Team Approves the preliminary analysis report, architecture report, Implementation Team project deliverables implementation report and all other Approves the project plan and the release plan Monitors project evolution through regular project reviews Approves major changes (in content, schedules, etc.) requested by the project manager and approved by the system manager 2.1.1.2 System Manager: The management level user most directly concerned with the system being developed Reports to the project steering committee TableHeads the system management and implementation team 4-1 ROCIT Team Structure Chooses the user members of the system management and implementation team Assigns the user personnel needed to support the development team in the preparation of functional specifications and other work Reviews the preliminary analysis report, the architecture report and the implementation report. Approves the functional specifications and the definition of data elements Approves user guides Approves the project plan and the release plans

Settles differences that may arise between users and analysts working on the project Approves any change of plan with regard to system contents Sets priorities for change requests affecting the schedule and may refer this to the project steering committee Co-ordinates the activities connected with system management and implementation i.e. training, conversion site preparation, etc.

2.1.1.3 Project Manager: A very experienced systems analyst with good management skills Reports to the project steering committee Heads the development team Builds the development team Co-ordinates the development, activities, and may participate in some of them i.e. preliminary analysis Prepares the project plan and release plans and submits them to the project steering committee for approval Approves the group plans Prepares the project reviews and presents them to the project steering committee Conducts progress reviews with the group leaders Conducts change management meetings Conducts meetings dealing with outstanding issues Notifies the system manager of variances from plan and submits recommendations for corrective action

3 Managerial Process Plans

3.1 Start-up Plan

3.1.1 Estimation Plan Total cost for Requirements, Detail design, VB Coding/Access dB development, Testing, Documentation: Rs. 348000. Hardware/software: Rs. 25,0000 (Rs. 20,0000 for server and Rs. 5,0000 for software) Total cost: Rs. 373,0000 Schedule for Requirements, Detail design, VB Coding/Access dB development, Testing,

METHODS USED: EVALUATION DONE USING THE INDUSTRY CALCULATION OF FUNCTIONS POINTS PER MONTH BASIS Confidence level: High. Used industry average. Cost and schedule could vary on a plus or minus 10% 3.1.2 Staffing Plan 18 employees 3 for the entire length, 15 on and off during the project Project Managers: 1 VB coders: 5 Experienced in Visual Basic and web database publishing level. Software Engineers: 3 Duration 4 months Technical Writers: 5 Duration 1 month Gophers: 2. Duration: 7 months 3.2 Work Plan The project will start on the first working day of September 2012. It will last for 7.125 months and should be completed by late March 2013. 3.2.1 Work Activities

Web Based software (WBS) -Life Cycle section

MANAGEMENT Scope Definition Establish requirements for project Identify current resources available Identify current materials available (if any) Modify requirements to meet project goal Planning Plan the effort required to complete system Plan work schedules Plan tasks Assign tasks to personnel Plan duties Assign duties to personnel Plan costs based on established requirements

Execution and Control Implement plan to meet objectives Monitor progress on a regular basis Control tasks and work schedules through the WBS Alter work schedule when need arises

Investigate and resolve problems Report progress to management and stakeholders regularly

Review and Evaluation Ensure products and plans are evaluated Access evaluation results and summarize Produce documentation on the complete project process Closure TECHNICAL Situation Survey Define current manual system Document work flow List current inputs and outputs Define mission critical tasks Determine when project is complete Check for completeness through system and user acceptance testing Obtain client signoff on final product

Study of Existing Systems Analysis of current paper system Analysis of current Hardware/Software

Definition of Specific Objectives Purchase of new Hardware/Software Design Access Database Design Web Page Design Visual Basic 6 controller program Pseudo Code (Procedures for business rules implementation) New High speed lines for uploads and downloads Inputting information (Old Records to bring the database up to date) Testing (Modules and Scripts)

Evaluation of Alternatives Analyze possible alternatives (Different Languages, More Robust database)

Implementation of Solution

Installation (New Hardware/Software)

Delivery of Solution Training Staff Documentation

3.2 Risk Management Plan The purpose of the Risk Management Plan is to identify, analyse and rank risk Factors. Once factors have been identified the these will be analysed for impact and consequences and ranked accordingly plans will be put in place for contingencies and tracking and control measures will be put in place. Risk management is an ongoing task, as influencing conditions a rarely stagnant during the course of the project. 3.2.1 Risk Identification For the Project we have identified two main areas of risk The loss of key personnel, this could involve personnel being recruited to another employer or project, or the long-term illness of an individual. Funding could be withdrawn form the project due to other priorities within the Institute. 3.2.1 Risk Analysis The risks will be analysed according to the ternary Level Model of risk. Loss of key personnel - Loss of key personal would prove to difficult to replace during the course of the project. This would severely effect the project schedule due to the small size of the team, loss of more than one member could put the whole project at risk. Given current market conditions for IT resources the likelihood of being recruited has diminished, but still cant be ignored. The Impact of this risk is ranked as High while the likelihood is rated as Moderate. Giving an overall Severity rating of (h-m) or High risk. Withdrawal of Funding - This would prove to be catastrophic to the project forcing cancellation of the project or at the very least suspension of the project until funding could be restored. The project falls into an area that is favourable to the current environment within the Federal Government as the project aligns well with Government On-Line (GOL) initiatives. This severity of this risk is evaluated as Moderate (h-l) 3.2.2 Risk Planning The highest risk to the project is the loss of a key member of the project team. Team members should be advised as to their critical role in the project's success and should be committed to the success of the project. Keeping the objective clear in everyone mind will be priority.

3.2.3 Risk Tracking The Project Manager will be responsible for Monitoring the level of likelihood that funding for the project could be cancelled, on a weekly basis prior to the weekly Status he will rate the risk on a scale of 1 to 5 where 1 is unlikely and 5 is highly likely. This value will be tracked over the life of the project. 3.2.4 Risk Control If it becomes apparent that the factors that effect the loss of team members are on the rise, steps should be taken to ensure that team members remain committed to the project. If team members are being lured away form the project steps should be in place to make sure transition will be as smooth as possible In the event that the indicator for funding is showing a tendency to rise the Project Manager will take action to work with the project sponsor to promote the project to executive staff, through presentation, formal and informal meetings. Careful attention must be given to detail how the project aligns to current Government objectives. 3.3 Infrastructure Plan Hardware OS - Network: Server - Compaq Proliant 550XN Pentium III Xeon 550 MHz, 1GB RAM, 5 9gig drives (3 RAID 5 configured for dB, web site 1 System drive, 1 mirror system drive) Win2k server, IIS, MS Access 2000 Workstation Dell Optiplex GX1, 866 MGz, 128MB RAM, 20GB HD, Win2K workstation, MS Access 2000, MSVB, Netscape (latest), IE (latest), MS Project 2000, Cold Fusion (latest) Network: Use of the PWGSC LAN/WAN facility Policies procedures and standards will follow those used by PWGSC and Institute. Facilities: 10 Offices with room for 15 workstation. Server will be located in the Institute (PWGSC) LAN room with UPS and AC commodities. Maintenance of the server will be done by PWGSC support staff.

3.4

Reviews and Audits

Controlled Items Reviews and Audits will be used on this project to ensure Quality Control and to track the teams progress against the schedule in the development of the applications. The following documents are to be used in conjunction with the Defect Resolution Plan: Technical Process Plan Quality Assurance Plan Schedule Control Plan Estimation Plan

Risk Management Plan

Reviews and Audit Activities Reviews and Audit will be used to track the Team Members progress to: Ensure that project stays on schedule and within budget. Assess the overall status of the project. Ensure that the Projects Quality Assurance standards are being adhered to. Reviews and Audit will be used by the Program Manager to ensure that the overall status of the project follows the schedule and it will also be used for Risk Management to help in prevent potential problems form occurring.