software project planning and management
Download as PPTX, PDF0 likes1 view
explaination about software project planning
software project planning and management
- 2. Definition A Software Project planning is the complete methodology of programming advancement from requirement gathering to testing and support, completed by the execution procedures, in a specified period to achieve intended software product.
- 3. Objectives of project planning The Objectives of project planning are listed below : It defines the roles and responsibilities of the project management team members. It ensures that the project management team works according to the business objectives. It checks feasibility of the schedule and user requirements. It determines project constraints.
- 4. Principles Of Software Project planning Planning is necessary: Planning should be done before a project begins. For effective planning, objectives and schedules should be clear and understandable. Risk analysis: Before starting the project, senior management and the project management team should consider the risks that may affect the project. Tracking of project plan: Once the project plan is prepared, it should be tracked and modified accordingly. Meet quality standards and produce quality deliverables: The project plan should identify processes by which the project management team can ensure quality in software. Based on the process selected for ensuring quality, the time and cost for the project is estimated.
- 5. Issues In Software Project planning Issues with Time Management 1. Determining short time 2. Wastage of time by team 3. Wastage of time by manager 4. Wastage of time due to incident Issues with Finance Management 1. Short budget 2. Late payment from customer 3. Improper use of budget
- 6. Issues in software project planning Issues with man power 1. Poor induction 2. Untrained personnel 3. Lack of trust among team member 4. Mentally unconfident teams Issues with Management itself 1. Lack of interest 2. Mentally not clear about project 3. Manager himself not expert
- 7. Issues In project planning Software Requirements: Changing, Missing or Unclear: A project plan is based on requirements. It goes without saying that if you change your requirements or identify missing requirements during the project, the project scope will be impacted.
- 8. Activities in Software project planning Project planning process comprises several activities, which are essential for carrying out a project systematically. These activities refer to the series of tasks performed over a period of time for developing the software. These activities include estimation of time, effort, and resources required and risks associated with the project.
- 9. Activities in software project planning
- 10. Software project planning Activities Project planning process consists of the following activities : Identification of project requirements: Before starting a project, it is essential to identify the project requirements as identification of project requirements helps in performing the activities in a systematic manner. These requirements comprise information such as project scope, data and functionality required in the software, and roles of the project management team members. Identification of cost estimates: Along with the estimation of effort and time, it is necessary to estimate the cost that is to be incurred on a project. The cost estimation includes the cost of hardware, network connections, and the cost required for the maintenance of hardware components. In addition, cost is estimated for the individuals involved in the project.
- 11. Software project planning activities Identification of risks: Risks are unexpected events that have an adverse effect on the project. Software project involves several risks (like technical risks and business risks) that affect the project schedule and increase the cost of the project. Identifying risks before a project begins helps in understanding their probable extent of impact on the project. Identification of critical success factors: For making a project successful, critical success factors are followed. These factors refer to the conditions that ensure greater chances of success of a project. Generally, these factors include support from management, appropriate budget, appropriate schedule, and skilled software engineers.
- 12. Software project planning activities Preparation of project charter: A project charter provides a brief description of the project scope, quality, time, cost, and resource constraints as described during project planning. It is prepared by the management for approval from the sponsor of the project. Preparation of project plan: A project plan provides information about the resources that are available for the project, individuals involved in the project, and the schedule according to which the project is to be carried out. Commencement of the project: Once the project planning is complete and resources are assigned to team members, the software project commences.
- 13. Master Scheduling This master schedule represents a summary-level project schedule the purpose of which is to identify all of the major deliverables for the project as well as all individual work. It contains definitions and dates for every milestone of the project. Inside the project master schedule is the allocation of the time required to achieve every objective and the documentation and illustration of the relationships between all activities.
- 14. Components of Master Schedule The master schedule depends on the adequate construction of the master project plan and the detailed work schedules for the project to enable it to accurately determine the accurate time each milestone will be completed and each deliverable will be produced. Components are: 1. Master Project plan 2. Detailed work schedule
- 15. Master project plan Formulation of a reliable and accurate master schedule cannot begin until a master project plan is in place. The project master plan is primarily intended for the project team and includes: Project scope and work statement. Project organization, resources, and training requirements. Technical details of every significant project activity. This includes the work breakdown structure (WBS) that is essential for the formulation of the detailed work schedules required by the project master schedule.
- 16. Detailed work schedule The creation of the master project schedule is a process that is formed from the bottom up. That means that the work schedules from each team member and element must be defined before they can be included in the master schedule. This also means that the those who will actually do the work should be involved in estimating the schedule for each task. This not only improves the accuracy of the master schedule as a whole, but it helps to assure the support of every member of the team.
- 17. Thanks