Ch4 project management process
Download as PPTX, PDF2 likes1,428 views
The document discusses ISO 29110 project management processes. It describes the 7 key objectives of project management: 1) developing a project plan based on customer requirements, 2) monitoring project progress against the plan and addressing deviations, 3) managing change requests and evaluating their impact, 4) holding review meetings with stakeholders, 5) identifying and managing risks, 6) implementing version control of project items, and 7) performing quality assurance to ensure compliance with the plan and requirements. Project monitoring involves comparing actual progress to the project plan and addressing any problems in meeting targets.
Ch4 project management process
- 1. SE423 SPI CH-4 ISO29110: Project Management process Kittitouch Suteeca
- 2. Outline PM. process Overview PM. Process objectives
- 4. 0 10 20 30 40 50 60 1990 1992 1994 1996 1998 2000 2002 2004 2006 Size of Software Project KLOC of Windows source code since 1992-2006
- 5. Customer needs High Quality On time Cheap Complete expectation Better Quality Faster Cheaper Over expectation Today Future
- 7. 1994 1996 1998 2000 2002 2004 2006 2008 succeed 16% 27% 26% 28% 34% 29% 35% 32% cancelled 31% 40% 28% 23% 15% 18% 19% 24% Has problem (finished) 53% 33% 46% 49% 51% 53% 46% 44% Problem in Software project Ref. Standish Report 1995, 1997, 1999, 2001, 2003, 2005, 2007, and 2009
- 8. Late.(Fail) Incomplete customer expectation. Low quality, reliability. Over budget. … Problem in Software project<Classic>
- 9. Project Management (PM) Process The purpose of the Project Management process is to establish and carry out in a systematic way the tasks of the software implementation project, which allows complying with the project’s objectives in the expected quality, time and costs.
- 10. ISO/IEC29110 PROJECT MANAGEMENT PM.O1 PM.O5 PM.O6PM.O2 PM.O3 PM.O4 PM.O7 Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task Task TaskTask Task WP WP WP WP WP
- 11. Project Management process PM.1 Project Planning PM.2 Project Plan Execution PM.3 Project Assessment and Control PM.4 Project Closure
- 13. PM.Objective1. The Project Plan for the execution of the project is developed according to the Statement of Work and reviewed and accepted by the Customer. The tasks and resources necessary to complete the work are sized and estimated.
- 15. PM.01 Documentation Statement of Work Document for communicate between customer and manufacturer (Software company) with agreements such as.. Product description Scope Objectives Deliverables #Other name Proposal, Term of Reference: TOR, Quotation
- 16. Planning is to know Project characteristics Product Characteristics the process and activities their sequences and components.
- 17. Project Plan The collection of plans that describe the activities to be performed for the project. It governs the management of the activities performed by the engineering group for a project. PM.O1 Documentation
- 18. Resource of Project (4M+1E) Material Man(People) Machine Method Environment Material Man Environmen t Machine Method Product Service
- 19. Includes: Product Description Scope Objectives Deliverables Tasks, including verification, validation and reviews with Customer and Work Team, to assure the quality of work products. Tasks may be represented as a Work Breakdown 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 when the resources are needed. Project Plan
- 20. Composition of Work Team Schedule of the Project Tasks, the expected start and completion date, for each task. Estimated Effort and Cost Identification of Project Risks Version Control Strategy Delivery Instructions Project Plan(cont.)
- 21. PM.Objective 2. Progress of the project is monitored against the Project Plan and recorded in the Progress Status Record. Corrections to remediate problems and deviations from the plan are taken when project targets are not achieved. Closure of the project is performed to get the Customer acceptance documented in the Acceptance Record.
- 23. How to measure project? Project duration Duration in each task task Size of project Plan Actual duration
- 24. Revision 3.3 05 PSP Basic Measurement 24 Project monitoring Project progress Plan Actual time Actual progress
- 25. “Record of any deviations ” Why? Plan Work Plan Work Plan Work Post mortem Plan Work Post mortem
- 26. PM.Objective 3. The Change Requests are addressed through their reception and analysis. Changes to software requirements are evaluated for cost, schedule and technical impact.
- 29. PM.Objective 4. Review meetings with the Work Team and the Customer are held. Agreements are registered and tracked.(Meeting record)
- 31. PM.Objective 5. Risks are identified as they develop and during the conduct of the project.
- 32. PM.Objective 6. A software Version Control Strategy is developed. Items of Software Configuration are identified, defined and baselined. Modifications and releases of the items are controlled and made available to the Customer and Work Team. The storage, handling and delivery of the items are controlled.
- 34. PM.Objective 7. Software Quality Assurance is performed to provide assurance that work products and processes comply with the Project Plan and Requirements Specification. Note: The implementation of the Software Quality Assurance process is through the performance of the verifications, validations and review tasks performed in Project Management and Software Implementation processes.
- 36. Summary of PM. PM.O1.>>Plan vs. Proposal (Statement of work). PM.O2>>Progress monitoring vs. Plan and solving problem. PM.O3>>Changing PM.O4>>meeting and communication PM.O5>>Avoid Risks PM.O6>>Configuration management PM.O7>> QA. In Project.