Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Project Management Fundamentals Course Preview
Similaire à Project Management Fundamentals Course Preview (20)
Plus de Invensis Learning
Plus de Invensis Learning (20)
Dernier
Dernier (20)
Project Management Fundamentals Course Preview
- 1. 1 Project Management Fundamentals Course Name : PM Fundamentals Version : INVL_PMF_CW_01_1.0 Course ID : PMGT – 141
- 2. 2 About Invensis Learning Invensis Learning is a leading certification training provider for individuals and enterprises globally. Our expertise in providing globally-recognized IT & Technical certification courses has enabled us to be one of the trusted certification training partners for many Fortune 500 organizations and Government institutions worldwide. Invensis Learning has trained and certified thousands of professionals across a wide-range of categories such as IT Service Management, Project Management, Quality Management, IT Security and Governance, Cloud Computing, DevOps, Agile Project Management, and Digital Courses. Invensis Learning’s certification training programs adhere to global standards such as PMI, TUV SUD, AXELOS, ISACA, DevOps Institute, EXIN, and PEOPLECERT.
- 3. 3 What We Offer We offer globally-recognized training and certifications in categories such as Project Management, ITSM, Agile, Quality Management, Technology Training, Program Management and IT Security & Governance. ITSM Project Management Quality Management Technology Training Agile & Scrum IT Security & Governance ITIL Foundation PMP Project Rescue Six Sigma Yellow Belt Training Cloud Computing PMI-ACP COBIT5 Foundation ITIL SD CAPM Project Scope Management Six Sigma Green Belt Training Big Data Scrum Training COBIT5 Implementation ITIL SS PRINCE2 Project Schedule Management Six Sigma Black Belt Training Hadoop DevOps Foundation COBIT5 Assessor ITIL ST PgMP Project Communications and Management Lean Six Sigma Green Belt Training .Net Technologies ISO/IEC 27001 Foundation ITIL SO PMI-RMP Project Cost Management Lean Six Sigma Black Belt Training Data Warehousing CRISC ITIL CSI P3O Project Procurement Management Introduction to Lean Training CISSP CGEIT ITIL RCV MSP Project Leadership Lean Fundamentals Program VC++, MCF ITIL OSA Microsoft Project Change Management Lean Management Training Advanced WCF, ITIL SOA Microsoft Project Server Implementing a Project Management Lean Manufacturing Training Advanced JAVA ITIL PPO IT Project Management Managing Conflict in the Workplace Lean Processes and Tools Advanced J2EE ITIL MALC Project Management Overview Negotiating in a Project Environment Lean Six Sigma in Information ISO 20000 Project Initiation Presentation Skills for Project Personnel Lean Six Sigma in Healthcare Earned Value Management Project Estimating Techniques DFSS Yellow Belt Training Project Risk Management Managing Multiple Projects DFSS Green Belt Training Project Sponsorship DFSS Black Belt Training Team Development MINITAB Training
- 4. 4 Topics Sl. No. Topics Slide No. 1 Project management concepts 6 2 Project influences 24 3 Role of the project manager 29 4 Project management cycle 32 5 Agile projects overview 39 6 Project management certifications 42
- 5. 5 Copyright Notice This training material is a property of Invensis Learning. Reproduction of this courseware in its entirety or in part is strictly prohibited.
- 6. Module 1 – Project Management Concepts
- 7. 7 Project Management Concepts Module 1 Project Management Institute USA defines a project as a temporary endeavor undertaken to create a unique product, service or result. Temporary: Temporary nature of the project indicates a definite beginning and end Unique: Although repetitive elements may be present in some project deliverables, this repetition does not change the fundamental uniqueness of the project work Projects drive change, they enable business value creation, the value may be tangible or intangible Projects are initiated due to several factors or reasons AXELOS Ltd., UK defines a project as a temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case. Every project: is unique has associated risks (negative/threats or positive/opportunities) is cross-functional has an intention to bring some change What is a Project?
- 8. 8 Project Management Concepts Module 1 What is Project Management?
- 9. 9 Project Management Concepts Module 1 Project success is often measured against constraints A change in one constraints is likely to affect one or more other constraints Constraints may be • Scope • Cost • Schedule • Quality • Resources • Risk • Benefits Project Constraints
- 10. 10 Project Management Concepts Module 1 Projects vs. Operations Projects Operations Temporary Ongoing Unique Product Standard Product Definite start and end date Indefinite Heterogeneous Teams (varied) Homogenous Teams (similar)
- 11. 11 Project Management Concepts Module 1 A group of related projects and activities coordinated and managed to obtain outcomes and benefits not available from managing them individually Programs are larger in scope than projects Though a program has a schedule but it will run until the planned outcomes and benefits are achieved The projects in a program have to be related Projects may exist separately from programs within an organization Program is not just a collection of projects, they have to be related and coordinated together What is a Program?
- 12. 12 Project Management Concepts Module 1 A collection of projects, programs, operations and functions managed together to achieve strategic business objectives Portfolio management performs the selection and initiation of new projects or programs and also their termination if necessary Portfolio management is accountable to ensure resource supply for the organizational needs What is a Portfolio?
- 13. 13 Project Management Concepts Module 1 Example - Project, Program and Portfolio Real Estate portfolio High rise residential complexes program Residential tower 1 Residential tower 2 Global residential complex marketing operations Commercial complexes program Commercial complex project Commercial complex market growth initiative Commercial complex marketing operations Seashore tower projects
- 14. 14 Project Management Concepts Module 1 Determining the appropriate combination of processes, tools, techniques, outputs, and the life cycle phases to manage a project Done in consultation with key stakeholders Depends on the project’s context Tailoring example - an organization may modify an existing project management approach to create a suitable project management methodology • This methodology may also provide guidelines to adjust (tailor) project management based on project complexity, size, etc. Project Management Tailoring
- 15. 15 Project Management Concepts Module 1 Business case • Business justification for the project • It may justify the project as required, desired or optional (this is known as situational analysis) • It may recommend various alternatives (options) which may be do nothing, do the minimum work possible, do more than the minimum • Economic analysis and evaluations are performed in order to make a decision • Risks, constraints and assumptions are also documented • Final recommendations are documented Benefits management plan or approach • Benefits, their timelines, owners and metrics are detailed • It ensures that each benefit is aligned to business strategies • Risks and assumptions of this plan are documented Project sponsor is accountable for creation and maintenance of these documents Project Business Documents
- 16. 16 Project Management Concepts Module 1 Timely delivery of agreed scope within budget There may be other measures also, these should be agreed and documented. For example: • Meeting financial targets • Fulfilling the contract • Customer satisfaction Project Success Measures
- 17. 17 Project Management Concepts Module 1 Project life cycle – A series of one or more phases form start to the finish of the project Types of project life cycles • Predictive or waterfall • Iterative and incremental • Adaptive or change driven or agile • Hybrid (mix of predictive and adaptive) Development approach or life cycles – Phases in the product development approach which are industry based, for example: • Software development life cycle - Analyze, Architect, Design, Construct, Test, Release • Construction - Engineering, Procurement and Commissioning (EPC) Product life cycle – the cycle of product conceptualization, development, growth, maturity, decline and end of life Project Life Cycles
- 18. 18 Project Management Concepts Module 1 Project Life Cycle (single phase) Pre-project Feasibility, Business case Start-up or initiate Agree to project objectives Plan, prepare Estimates, Plans, Baselines Execute Close or windup Project Life Cycle Project monitoring and control A project charter or project initiation document is produced
- 19. 19 Phase 1 Phase 2 Phase 3 Phase 1 Phase 2 Phase 3 Start-up, planning, execution, and closure may occur in each phase Project Life Cycle (multi-phase) Project Management Concepts Module 1
- 20. 20 Analyze Architect Design Construct Test Release Software Development Engineering Procurement Commissioning Construction Development Approach or Life Cycle Project Management Concepts Module 1
- 21. 21 Concept Development Growth Maturity Decline End of life Product Life Cycle Project Management Concepts Module 1
- 22. 22 Project Management Concepts Module 1 Predictive life cycle (waterfall) • Project scope, time and cost are determined early • Any changes to the scope will trigger going back to earlier phases again (like modifying the design) Iterative and incremental life cycle • Project scope is generally determined early, time and cost may be modified as product becomes more clear • The product is developed in several iterations (repetitions of similar activities in phases) • Each iteration adding functionality to the product (incrementing the product) Project Life Cycles
- 23. 23 Project Management Concepts Module 1 Adaptive (agile or change-driven) life cycle • An approximate product outline, vision and/or roadmap are developed at the start • Detailed scope is defined and approved before the start of an iteration, based on current and emerging priorities (therefore flexible scope and high adaption to change) • Iterations are short, usually 2-4 weeks, and called sprints, and the duration of each iteration in the project is fixed • Working product at the end of each iteration • Close customer involvement for features prioritization, product review and feedback after each iteration • Highly collaborative and empowered project team which does the detailed planning for each iteration as per customer/sponsor priorities • Uses approaches like Scrum, Kanban, etc. Hybrid life cycle • A combination of a predictive and an adaptive life cycles • Well known project elements or fixed requirements follow a predictive development approach • Evolving project elements follow an adaptive development approach Project Life Cycles
- 24. 24 CONTACT INVENSIS LEARNING Email Us: © Copyright 2019 Invensis Learning Pvt Ltd. All Rights Reserved. www.invensislearning.com support@invensislearning.com USA +1-910-726-3695 | IND +91-96-2020-0784 UK +44 2033-223-280 | Germany +49 2119-5987-989 Switzerland +41-22-518-2042 | Hong Kong +852-5803-9039
Notes de l'éditeur
- Training is designed around PMBOK knowledge domains (10). The PMBOK is an accredited American Standard that contains best practices of project management that have been collected and verified by the project management community represented in the PMI (The Project Management Institute)
- A Guide to the Project Management Body of Knowledge (PMBOK® Guide) addresses the processes that project management experts agree are necessary for most projects in most environments.
- How Temporary? It has a definite beginning and end, and it is not an ongoing effort. It comes to an end when the objectives have been met Project Team members are released on the completion of the Project How Unique? The end result, product or service is different in some way from the other product, service or result. For example: Within a Housing complex, each type of flat has different designs, facilities and features to differentiate their end characteristics -mosaic with the teak wood finish or marble with the teak wood finish or red-oxide flooring with forest wood finish.
- Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. Project requirements are the stakeholders’ needs, wants and expectations from the project.
- How Temporary? It has a definite beginning and end, and it is not an ongoing effort. It comes to an end when the objectives have been met Project Team members are released on the completion of the Project How Unique? The end result, product or service is different in some way from the other product, service or result. For example: Within a Housing complex, each type of flat has different designs, facilities and features to differentiate their end characteristics -mosaic with the teak wood finish or marble with the teak wood finish or red-oxide flooring with forest wood finish.
- Projects are different from operations in the following ways: Temporary – projects are temporary and complete when his objective is achieved. Operations continue indefinitely and sustain the business Unique - Normal operations would produce standard product or service where as projects would produce unique product or service Project Teams usually comprise of members from a wide range of Functions/Departments with a diverse skill set whereas operations involve similar skill set resources.
- The project lifecycle is a series of phases that the project passes from Initiation to Closure. A phase is a discrete unit of work to be completed on the project. The various project lifecycles are: Predictive Lifecycles - also known as fully plan driven. These are the ones in which the project scope, time and cost required to deliver the scope are determined early in the project lifecycle as practically as possible. The work performed in each phase is generally different from the other phases, be it preceding or subsequent. In this lifecycle, there are very less or no adjustments to the project scope during the course of the project. These are suited for projects where the product to be delivered is well understood and well defined. Iterative & Incremental Lifecycles are the ones in which the project phases intentionally repeat one or more project activities as the project team’s understanding of the product increases. The lifecycle is broken into multiple iterations; during each iteration, work is performed to deliver the deliverables, and with each increment, functionality is added to the product. In this lifecycle, only a high-level vision is known at the start of the project, but the detailed scope is elaborated with every iteration, Large and complex projects are frequently executed in an iterative fashion to reduce risk by allowing the team to incorporate feedback and lessons learned between iterations. Adaptive Lifecycles are also known as change driven or agile methods. These Lifecycles are iterative and incremental too but differ from the Iterative lifecycle as the iterations are very rapid and are fixed in time and cost. This lifecycle should be chosen when stakeholder involvement in the project is high, and it is predicted that there will be high levels of change. In this lifecycle, the overall scope is decomposed into a set of requirements and work to be performed; this is known as a product backlog. At the beginning of each iteration, the team would decide how many items from the backlog are to be included in the current iteration based on priority. At the end of each iteration, the product deliverables should be ready for customer review. The customer is continuously involved in providing feedback and in updating the backlog. After the completion of one iteration, the next set of requirements will be compiled based on priority as the next iteration to be performed.
- The project lifecycle is a series of phases that the project passes from Initiation to Closure. A phase is a discrete unit of work to be completed on the project. The various project lifecycles are: Predictive Lifecycles - also known as fully plan driven. These are the ones in which the project scope, time and cost required to deliver the scope are determined early in the project lifecycle as practically as possible. The work performed in each phase is generally different from the other phases, be it preceding or subsequent. In this lifecycle, there are very less or no adjustments to the project scope during the course of the project. These are suited for projects where the product to be delivered is well understood and well defined. Iterative & Incremental Lifecycles are the ones in which the project phases intentionally repeat one or more project activities as the project team’s understanding of the product increases. The lifecycle is broken into multiple iterations; during each iteration, work is performed to deliver the deliverables, and with each increment, functionality is added to the product. In this lifecycle, only a high-level vision is known at the start of the project, but the detailed scope is elaborated with every iteration, Large and complex projects are frequently executed in an iterative fashion to reduce risk by allowing the team to incorporate feedback and lessons learned between iterations. Adaptive Lifecycles are also known as change driven or agile methods. These Lifecycles are iterative and incremental too but differ from the Iterative lifecycle as the iterations are very rapid and are fixed in time and cost. This lifecycle should be chosen when stakeholder involvement in the project is high, and it is predicted that there will be high levels of change. In this lifecycle, the overall scope is decomposed into a set of requirements and work to be performed; this is known as a product backlog. At the beginning of each iteration, the team would decide how many items from the backlog are to be included in the current iteration based on priority. At the end of each iteration, the product deliverables should be ready for customer review. The customer is continuously involved in providing feedback and in updating the backlog. After the completion of one iteration, the next set of requirements will be compiled based on priority as the next iteration to be performed.
- The project lifecycle is a series of phases that the project passes from Initiation to Closure. A phase is a discrete unit of work to be completed on the project. The various project lifecycles are: Predictive Lifecycles - also known as fully plan driven. These are the ones in which the project scope, time and cost required to deliver the scope are determined early in the project lifecycle as practically as possible. The work performed in each phase is generally different from the other phases, be it preceding or subsequent. In this lifecycle, there are very less or no adjustments to the project scope during the course of the project. These are suited for projects where the product to be delivered is well understood and well defined. Iterative & Incremental Lifecycles are the ones in which the project phases intentionally repeat one or more project activities as the project team’s understanding of the product increases. The lifecycle is broken into multiple iterations; during each iteration, work is performed to deliver the deliverables, and with each increment, functionality is added to the product. In this lifecycle, only a high-level vision is known at the start of the project, but the detailed scope is elaborated with every iteration, Large and complex projects are frequently executed in an iterative fashion to reduce risk by allowing the team to incorporate feedback and lessons learned between iterations. Adaptive Lifecycles are also known as change driven or agile methods. These Lifecycles are iterative and incremental too but differ from the Iterative lifecycle as the iterations are very rapid and are fixed in time and cost. This lifecycle should be chosen when stakeholder involvement in the project is high, and it is predicted that there will be high levels of change. In this lifecycle, the overall scope is decomposed into a set of requirements and work to be performed; this is known as a product backlog. At the beginning of each iteration, the team would decide how many items from the backlog are to be included in the current iteration based on priority. At the end of each iteration, the product deliverables should be ready for customer review. The customer is continuously involved in providing feedback and in updating the backlog. After the completion of one iteration, the next set of requirements will be compiled based on priority as the next iteration to be performed.
- The project lifecycle is a series of phases that the project passes from Initiation to Closure. A phase is a discrete unit of work to be completed on the project. The various project lifecycles are: Predictive Lifecycles - also known as fully plan driven. These are the ones in which the project scope, time and cost required to deliver the scope are determined early in the project lifecycle as practically as possible. The work performed in each phase is generally different from the other phases, be it preceding or subsequent. In this lifecycle, there are very less or no adjustments to the project scope during the course of the project. These are suited for projects where the product to be delivered is well understood and well defined. Iterative & Incremental Lifecycles are the ones in which the project phases intentionally repeat one or more project activities as the project team’s understanding of the product increases. The lifecycle is broken into multiple iterations; during each iteration, work is performed to deliver the deliverables, and with each increment, functionality is added to the product. In this lifecycle, only a high-level vision is known at the start of the project, but the detailed scope is elaborated with every iteration, Large and complex projects are frequently executed in an iterative fashion to reduce risk by allowing the team to incorporate feedback and lessons learned between iterations. Adaptive Lifecycles are also known as change driven or agile methods. These Lifecycles are iterative and incremental too but differ from the Iterative lifecycle as the iterations are very rapid and are fixed in time and cost. This lifecycle should be chosen when stakeholder involvement in the project is high, and it is predicted that there will be high levels of change. In this lifecycle, the overall scope is decomposed into a set of requirements and work to be performed; this is known as a product backlog. At the beginning of each iteration, the team would decide how many items from the backlog are to be included in the current iteration based on priority. At the end of each iteration, the product deliverables should be ready for customer review. The customer is continuously involved in providing feedback and in updating the backlog. After the completion of one iteration, the next set of requirements will be compiled based on priority as the next iteration to be performed.