1 / 10

Project Management

Project Management. Software management is distinct and often more difficult from other engineering managements mainly because: Software product is intangible There are no standard software processes Large software projects are usually different from previous projects. Management Activities.

tevin
Download Presentation

Project Management

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Management • Software management is distinct and often more difficult from other engineering managements mainly because: • Software product is intangible • There are no standard software processes • Large software projects are usually different from previous projects

  2. Management Activities Most managers do some or all of the following regularly at all times: • Proposal writing • Project planning and scheduling • Project costing • Project monitoring and reviews • Personnel selection and evaluation • Report writing and presentation

  3. Project planning • Effective management depends on planning the progress of the project in detail and allow for deviations • Project plan evolves as project progresses and better information becomes available • Project Constraints, milestones and deliverables must be identified clearly and timely

  4. Project planning process Establish project constraints Make initial assessment of the project parameters Define project Milestones and deliverables While (project has not been completed or cancelled) Loop Draw up project schedule Initial activities according to schedule Wait (for a while)  review project progress Revise estimate of project parameters  update project plan Renegotiate project constraints and deliverables If (problem arise) Then Initiate technical review and possible revision End loop

  5. Project Plan Sections: • Introduction (objective, constraints time, budget) • Project Organization (People, teams, roles) • Risk Analysis • Hardware & Software resource requirements • Work breakdown (tasks, milestones, deliverables) • Project schedule (time estimates per task, people allocation, task dependencies, milestone dates) • Monitoring and reporting mechanism (reports)

  6. Milestones and Deliverables TASKS (ACTIVITIES) Feasibility Study Requirements Analysis Prototype Development Design Study Requirements Specification Feasibility Report User Requirements Evaluation Report Architectural Design System Requirements MILESTONES

  7. Task Durations and Dependencies

  8. Activity Network T4, 11 days T1, 5 days M3, 5/1/03 T2, 9 days M2, 4/3/03 Start Finish T7, 12 days T5, 7 days M1, 2/20/03 T3, 21 days T6, 15 days

  9. Activity Bar (Gantt) Chart 1/20 1/27 2/3 2/10 2/17 2/24 3/3 3/10 Start T1 On time: T4 Allowed delay: T8 M1 T2 M2 T7 T6 T9 M3 M4 M5 T5 Finish T3 T10

  10. Risk Management Stages for managing risks: • Risk Identification (project, product, business, technology) • Risk Analysis (likelihood and consequences, low/medium/high) • Risk Planning (avoiding, minimizing risk effects, contingency planning) • Risk Monitoring (constant assessment, mitigation i.e. reduce risk severity)

More Related