PROJECT MANAGEMENT. Project Management involves: ►Planning. (The well planned project refers to the high management.) ►Monitoring. (Monitoring here refers to the definition of time limits and tasks etc.) ►Control of people. (It means the coordination among the people and solution of conflicts among people of the project.) ►Process. (Process refers to the particulae way to manage or refer to the specific process model.) ►Event. (All events and work tasks are also involved in Project Management.)   Effective Project Management   Effective Project Management focuses on the following four points.   ►The People. ►The Product. ►The Process. ►The Project.   ►The People. The People in effective project management are organized to perform the effective software engineering. People in the project management involves: ♦Stakeholders. ♦Team Leaders. ♦Software Team.   ♦Stakeholder.   Stakeholders defines the business issues that have significant influence on “Project”. Stake holders can be categorized in the following states.   ♦Senior Managers. ♦Project Managers. ♦Practitioners. ♦Customers. ♦End Users.   ♦Team Leaders.   Team leader supports the “MOI” leadership model.   ♦MOI   MOI refers to:   M-Motivation. O-Organization. I-Ideas and Innovations.   Team leader must have the following characteristics. i.e.   ♦Problem Solution Capability. ♦Managerial Ability. ♦Achievement. ♦Influence and Team building.   ♦Software Team.   A best software team is built when the following factors are considered:   ♦Difficulty of problem to be solved. ♦Degree of Moralization. ♦Time limits. ♦Degree of socialibility required. ♦Size of resultant program ♦Required quality and reliability. ♦Rigidity of the delivery date.   ♦Team Toxity.   Software Team may suffer from Team Toxic due to the following reasons.   ♦Fast and mad work atmosphere. ♦High frustration. ♦Fragmented or poorly coordinated software process. ♦Unclear definition of rules. ♦Continuous or repeated exposures to failure.   ►The Product.   The product involves: ►Scope. ►Informaton Objectives. ►Function and performance. ►Constraints and limitations. ►Problem definition.   ►Scope. Scope refers to the basic functions of the product.   ►Information Objectives. It includes: ♦Visible objects requirements as ‘Input’. ♦Visible objects products as ‘Output’.   ►Function and performance. Functions are performed to transform input data to output.   ►Constraints and limitations. It includes: ♦Product cost. ♦Product size. ♦Memory. ♦Problem decomposition. Decomposition is applied into two areas:   ♦Functionality. ♦Process.   ►The Process.   The process framework activities are applicable to all software projects. Project management selects the process model on the following basis:   ►The Customers of the product. ►Characteristics of the project. ►Environment of work area.   ►The Product and Process Melding.   Product and Process are meld into with Planning. Each function to be engineered by software team must pass the set of framework activities.   ►Process Decompositon.   Once Process Decomposition is selected, then process framework is adopted. In Process Decomposition , it is analyzed that how to accomplish a framework activity e.g. Communication activity, Planning activity etc.   ►For Simple Project.   ♦For Simple Project., it includes: ♦List of clarification objects. ♦Formal meeting. ♦Scope of document development. ♦Review of scope. ♦Modification of scope, if requires.   ►For Complex Projects.   ♦For Compex Projects, it includes: ♦Customer requirement review. ♦List of clarification objects. ♦Research for solution. ♦Agenda for formal meeting. ♦Conduct meeting. ♦Mini specification ♦Review of Mini specification. ♦Scope of document development. ♦Review of scope. ♦Modification of scope, if requires.     ►The Project.   For successful and improves Project Management, we should consider the following factors in mind:   ►Start on right foot. ►Maintain Momentum. ►Track Progress. ►Make smart decisions. ►Conduct and postmortem analysis.   ►Start on right foot. It means to work hard to understand the problem, in an efficient manner.   ►Maintain Momentum. It means that team should emphasize on Quality in every task, it performs.   ►Track Progress. Progress is tracked as the work product is produced.   ►Make smart decisions. It includes:   ♦‘Keep it smile’ rule. ♦Usage of existing software components. ♦Identify and avoid ‘Risks’.   ►Conduct and postmortem analysis. It refers the collection and analysis of software project metrics and taking feedback from the team members and customers.   Dangerous Facters.   The following factors can lead the software project to have risks and problems:   ♦Misunderstanding between software team and Customer. ♦Avoiding best practices. ♦Unskilled team members. ♦Loosing sponsorship. ♦Poorly defined scope. ♦The choosen technology changes. ♦Business needs changes. ♦Deadlines are unrealistic.