Project Planning In Project Management

Chapter 2

Project Management

2.1 Project Planning

2.2 Project Scheduling

2.3 Risk Management

2.4 Estimation

2.0. PROJECT MANAGEMENT:

2.1 PROJECT PLANNING:

Project Planning is concerned with identifying and measuring the activities, milestones and deliverables produced by the project. Project planning includes many task and resources as follows:

• Staff organization.

• Risk identification, analysis, and accurate planning.

• Estimating some of the basic attributes of the project like cost, duration and efforts. The effectiveness of the subsequent planning activities is based on the accuracy of these estimations.

• Miscellaneous plans like quality assurance plan, configuration management plan, etc. 2.1.1 Project Development

In this system, Chief Programmer team structure is used because in the organization, a senior engineer provides the technical leadership and is designated as the chief programmer. The chief programmer partitions the task into small activities and assigns them to the team members. He also verifies and integrates the products developed by different team members and they work under the constant supervision of the chief programmer. For this system reporting entity represents myself and the role of chief programmer is played by my internal guide.

2.2 PROJECT SCHEDULING

The scheduling is the peak of a planning activity, a primary component of software project management. When combined with estimation methods and risk analysis, scheduling establishes a roadmap for project management. The characteristics of the project are used to adapt an appropriate task set for doing

so in order to make our system stable and give its 100% performance we must have identify those risks, analyze their occurrences and effects on our system and must prevent them to occur

2.3.1 Risk Identification Risk identification is a first systematic attempt to specify risks to project plan, scheduling resources, project development. It may be carried out as a team process using brainstorming approach.

Technology risk: Technical risks concern implementation, potential design, interfacing, testing, and maintenance problems.

Database Corruptness Garbage Collection

People Risks: These risks are concerns with the team and its members who are taking part in developing the system.

Leaking an important data Failure of the administration Lack of knowledge Lack of clear product vision. Technical staff conflict. Poor communication between people. Tools Risks: These are more concerned with tools used to develop the system

Tools containing