Chapter 5 Project management. Project management : Is Organizing , planning and scheduling software projects. Topics covered. Management activities Project planning Project scheduling Risk management. Software project management.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
each project is different from previous others, even the manager who have a long experience may find it difficult to solve he problem in new software project, Because of rapid technological change in computer .
Lessons learned or experienced may not be transfer to new project.
It is difficult to put standards for software project’s managers, the ob of manager varies depending on the product being developed and organization.
Most managers have these responsibilities:
Continuous activity(planning is iterative process) from initial concept through the system delivery.Plans must be regularly changedas new information becomes available, itevolves as the better information becomes available. . Various types of plans may be developed to support the main software project plan that is concerned with: schedule plan budget planquality planvalidation planconfiguration planmaintenance planstaffplan
Most plans should include the following sections:
Activity networkfor example, if T8 is delayed 2 weeks, it will not affect the completion date because it does not lie on critical path.The critical path is: T1 T3 T9 T11T12The minimum days required to complete project is : 8+ 15+ 15+7+10 =55 day
5.4 Risk managementRisk management is concerned with identifying risks and drawing upplans to minimize their effect on a project.What are the top ten risks for this project? For each of the risk, what is the chance that risk will become a problemand what is the impact if it does?
e.g. Loss of an experienced designer
e.g. the failure of a purchased component.
All risk types are overlap : if an experienced programmer leave the project (project risk) replacement with new one with less experience will result in programming errors (product risk)
Six types of risks that can be found: