Ch4 project management process


Published on

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ch4 project management process

  1. 1. SE423 SPICH-4 ISO29110:Project ManagementprocessKittitouch Suteeca
  2. 2. Outline PM. process Overview PM. Process objectives
  3. 3. ISO/IEC 29110
  4. 4. 01020304050601990 1992 1994 1996 1998 2000 2002 2004 2006Size of Software ProjectKLOC of Windows source code since 1992-2006
  5. 5. Customer needsHigh QualityOn timeCheapCompleteexpectationBetter QualityFasterCheaperOverexpectationToday Future
  6. 6. Why Project Fail
  7. 7. 1994 1996 1998 2000 2002 2004 2006 2008succeed 16% 27% 26% 28% 34% 29% 35% 32%cancelled 31% 40% 28% 23% 15% 18% 19% 24%Hasproblem(finished)53% 33% 46% 49% 51% 53% 46% 44%Problem in Software projectRef. Standish Report 1995, 1997, 1999, 2001,2003, 2005, 2007, and 2009
  8. 8.  Late.(Fail) Incomplete customer expectation. Low quality, reliability. Over budget. …Problem in Softwareproject<Classic>
  9. 9. Project Management (PM)ProcessThe purpose of the Project Managementprocess is to establish and carry out in asystematic way the tasks of the softwareimplementation project, which allowscomplying with the project’s objectives inthe expected quality, time and costs.
  10. 10. ISO/IEC29110PROJECTMANAGEMENTPM.O1 PM.O5 PM.O6PM.O2 PM.O3 PM.O4 PM.O7TaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskTaskWPWPWPWPWP
  11. 11. Project Management processPM.1 Project PlanningPM.2 Project Plan ExecutionPM.3 Project Assessment and ControlPM.4 Project Closure
  12. 12. PM.Objective1.The Project Plan for the execution of theproject is developed according to theStatement of Work and reviewed andaccepted by the Customer. The tasks andresources necessary to complete the workare sized and estimated.
  13. 13. PM.01 Documentation Statement of Work Document for communicate between customerand manufacturer (Software company) withagreements such as.. Product description Scope Objectives Deliverables#Other name Proposal, Term of Reference: TOR,Quotation
  14. 14. Planning is to know Project characteristics Product Characteristics the process and activities their sequences and components.
  15. 15.  Project Plan The collection of plans that describe theactivities to be performed for the project. It governs the management of the activitiesperformed by the engineering group for aproject.PM.O1 Documentation
  16. 16. Resource of Project (4M+1E)MaterialMan(People)MachineMethodEnvironmentMaterialManEnvironmentMachineMethod ProductService
  17. 17. Includes: Product Description Scope Objectives Deliverables Tasks, including verification, validation and reviews withCustomer and Work Team, to assure the quality of workproducts. Tasks may be represented as a WorkBreakdown Structure (WBS). Relationship and Dependence of the Tasks Estimated Duration of tasks Resources (humans, materials, equipment and tools)including the required training, and the schedule whenthe resources are needed.Project Plan
  18. 18.  Composition of Work Team Schedule of the Project Tasks, the expected start andcompletion date, for each task. Estimated Effort and Cost Identification of Project Risks Version Control Strategy Delivery InstructionsProject Plan(cont.)
  19. 19. PM.Objective 2.Progress of the project is monitored againstthe Project Plan and recorded in theProgress Status Record. Corrections toremediate problems and deviations fromthe plan are taken when project targets arenot achieved. Closure of the project isperformed to get the Customeracceptance documented in theAcceptance Record.
  20. 20. How to measure project?ProjectdurationDuration ineach tasktaskSize of projectPlanActual duration
  21. 21. Revision 3.305 PSP Basic Measurement24Project monitoringProject progressPlanActualtimeActual progress
  22. 22. “Record of any deviations ” Why?Plan WorkPlan WorkPlan WorkPostmortemPlan WorkPostmortem
  23. 23. PM.Objective 3.The Change Requests are addressedthrough their reception and analysis.Changes to software requirements areevaluated for cost, schedule and technicalimpact.
  24. 24. PM.Objective 4.Review meetings with the Work Team andthe Customer are held. Agreements areregistered and tracked.(Meeting record)
  25. 25. PM.Objective 5.Risks are identified as they develop andduring the conduct of the project.
  26. 26. PM.Objective 6.A software Version Control Strategy isdeveloped. Items of Software Configurationare identified, defined and baselined.Modifications and releases of the items arecontrolled and made available to theCustomer and Work Team. The storage,handling and delivery of the items arecontrolled.
  27. 27. PM.Objective 7.Software Quality Assurance is performed toprovide assurance that work products andprocesses comply with the Project Plan andRequirements Specification. Note: The implementation of the Software QualityAssurance process is through the performance of theverifications, validations and review tasks performed inProject Management and Software Implementationprocesses.
  28. 28. Summary of PM. PM.O1.>>Plan vs. Proposal (Statement ofwork). PM.O2>>Progress monitoring vs. Plan andsolving problem. PM.O3>>Changing PM.O4>>meeting and communication PM.O5>>Avoid Risks PM.O6>>Configuration management PM.O7>> QA. In Project.
  29. 29. ReferencesISO/IEC29110 part 3,5.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.