02 Project Management Fundamentals (2)
02 Project Management Fundamentals (2)
Management
Fundamentals
PMP® Exam Preparation Training
03
Project
Influencing
04
Project Business
Factors Dcouments
Had and Soft High level
factors which Documents to
affects the project justify the project
success intiation
PMP® Exam Preparation
positiviely Training
/negatively
PMBOK® 6th Edition
Project Management Body of
Knowledge
PMBOK® 6th Edition & Agile Practice Guide
A fundamental resource for effective project management in
any industry.
A powerful tool that enable the right approach for the right
project.
• Tailoring considerations
• 13 Sections
A methodology is a combination of
Practices
Techniques
Procedures
Rules.
• Provides
Aspirational
• Describe the conduct of the practitioners
Mandatory
• Organization Requirements & Practitioner behavior
Responsibility
Respect Code of Ethics Fairness
Honesty
PMP® Exam Preparation Training
Users of Code of Ethics
● Practitioners
○ PMI Members
○ Certification Holders
○ Volunteers
Portfolio Management
Portfolio Management
• Components may not necessarily be related but have common goals/ Objectives
• Select the optimal mix of programs & Projects to meet the SO(Objectives)
• Reduces Risk
Program
Application of
to meet program
requirements
• Managing interdependencies
• Resource Management
Acitivities/
Defined Gol Process / Phases Temporary
Stratgic buisness Interrelated and Fianite in duration
objectives , vision Dependable
and mission
People /
Progressive
Deliverables Organization
Elopration
Unique Prduct and Iteratively Single or group of
Services developed people involve
Undertaken by
PMP® Exam Preparation Training
single or group of
Project : Temporary
Deliverables are
• Unique Product
• Unique Service
• Unique Result
• Combination of all
• Tangible or Intangible
Product Project
Results Project Management
Hardware Plan
Software Project Document
Applications Reports
Contracts Mintues of Meeting
Products
● Fixtures ● Trademarks
• Funding issues
Regulatory / Social/
Legal Product / Process
Meet regulatory , scoail Create .improve. Fix
and legal requirements products , processes
and services
Economic
Political Changes Market Demand Changes
Is an strategy execution
framework which connects
portfolio, program , project
and operation to achieve
organization’s vision ,
mission and strategic
objectives
Continious
Integration Improvement
Integrate organizational Consitency of education
process and function and delivery of training
into PPP
Product
Concept
Delivery
Growth
Maturity
Retirement
Life Cycle
Operation Projects
Frozen stable pattern Unfreeze – Change – Refreeze
Project can intersect operation during the product life cycle @ Various Points
Developin
g a new
product
At each Upgradin
closeout g a new
Phase product
End of
Expandin
Product
g outputs
Life Cycle
Improving
Operation
and
Processe
s
The portfolio manager from your division thought it might be helpful to the project teams if
she delivered a short presentation on the elements in her portfolio. A number of team
members, after receiving the e-mail announcement for the presentation, come to you and
ask if this meeting is worth their time. After all isn’t a portfolio just a big project? As a Senior
Project manager your best response would be:
Which of the following are the four basic elements of the PMI code
of ethics and professional conduct?
a) Responsibility, respect, fairness, honesty
b) Responsibility, accountability, fairness, honesty
c) Responsibility, respect, fairness, transparency
d) Responsibility, transparency, fairness, honesty
a) Portfolio manager
b) Program manager
c) Project manager
d) Program coordinator
a) Project
b) Product
c) Project management
d) Process development
• Development Approach
A collection of
generally sequential project phases
whose name and number are
determined by the control needs of the organization or
organizations involved in the project”
• Collection of Phases
Time
End
Start
w
Lo
Time
End
Start
Hig
h
w
Time Lo
End
Start
• High level Planning & detailed planning should be done from the
beginning of the project.
• In the beginning , Define High-level scope , preliminary schedule and cost , Detailed scope, cost & schedule
developed iteratively
• Every iteration has the Prioritized requirements , Deliverables are produced through a series of iterations
• Contains only the necessary capability and final product will be after the final iteration.
• Customer get value sooner than the degree of change and variation
• But the deliverables are considered complete after the final iteration
• But cost and schedule are routinely modified based on the understanding of the product increases
• Single delivery
• Correctness of solution
• Time boxing assigned to an iteration for few weeks , gather insights and rework on activities based on the
insights
• May take longer because they are optimized for learning rather than speed of deliver
• Encourages a feedback and better understanding of the requirements that can be incorporated into each
deliverable
• The work required to meet those requirements are prioritized & Ranked.
• Cyclic Process
• Customer can change and reprioritize the requirements to adjust within the cost & Schedule
• Feedback from the customer is used to set the detailed scope of the next iteration
• Team pulls work / features from the backlog based on its capacity
• The team defines its work flow in column on a task board and
• Team keep work in progress sizes small to better identify issues and reduce rework
• Customer satisfaction increases with early and continuous delivery of valuable products
• Incorporates both iterative and incremental approaches to adapt high degree of changes and deliver project value often
• Are tools to help assess if an agile approach could fit your organization and
project. Agile Suitability Tools
• Helps to determine the likely fit or gaps for using agile approaches 1. The Slider
2. DSDM Suitability Filter
• Assess under what circumstances an agile approach is appropriate to use 3. Alistair Cockburn’s Project Criticality
and Team Size
4. Boehm and Turner – Radar Chart
• Assess project and organizational factors associated with the adaption and 5. Dave Cohen’s Agile Factors
suitability 6. The Organizational Suitability Filter
7. The Methodology Bias Hammer
• Assessment provide scores indicating alignment or potential risk areas.
• Projects often combine elements of different life cycles in order to achieve certain goals.
• Hybrid Agile is the combination of Agile methods with other non-Agile techniques..
• If the Elements of the project are well known or have fixed requirements , follow a predictive life cycle
• If the Elements are still unknown and still evolving, follow an adaptive development life cycle.
• No project is completely devoid of considerations around requirements, delivery, change, and goals.
• Inherent characteristics of the project determine which life cycle is the best fit for that project.
• Each project finds a spot on the continuum that provides an optimum balance of characteristics for its
context.
Because Different
• Types of projects
• Organizational structures
• Management styles
• Products or outputs
• Tailoring options
• Project Environment
• The PMBOK® Guide describes their sequence as beginning with an initial phase, followed by a series of
intermediate phases, and ending in a final phase
• Processes that aid in the completion of the deliverable are performed in each phase.
• Size,
• Complexity,
• Name
• Number
• Duration
• Resource Requirements
• Entrance Criteria
• Exit Criteria
• 1 Week
• Month
Duration
• Quarter
• People
Resource Requirements • Building
• Equipment
• Documented Approval
Exit Criteria
• Completed Documents
• Completed Deliverables
• Iteration lengths are fixed , time box and not flexible in anyway, it will end regardless of whether all assigned
work is completed.
• Outstanding work is either assigned to the next iteration, or reprioritized amongst the remaining tasks.
• The general rule is that iterations should not exceed 30 days (One Calendrer month) in duration,
• Although some teams use iterations that range from 2 weeks to 4 weeks to a single day.
• The length of an iteration is largely determined by how a team and customer are required to work together.
• Short time periods help the team, Product Owners, Product Managers, and other stakeholders regularly test
and evaluate the technical and business hypotheses in a working system.
• An integration point, a ‘pull event’ that assembles various system aspects—functionality, quality,
alignment, and fitness for use—across all the teams’ contributions.
Project Management PM
Processes
Activities
Process
Group
PM Life
Cycle
Determine what information you need from other projects and what information you will
share with the organization and other projects.
Hold a kickoff meeting with key stakeholders, team members, managers of team
members, and the customer to make sure everyone is on the same page and to gain
buy-in.
Recalculate how much the project will cost and how long it will take, and create
forecasts.
Exchange information about the project according to the plan, and solicit feedback to
ensure communication needs are being met.
Process
Group
PM Life
Cycle
PM
Project Management Process Processes
Process
Group
PM Life
Cycle
• All the process must be covered , Required should be in in detail and not required should
be at high level
Tools &
Techniques
An input to
the another
process
Input Output
PM Process
A deliverable
of the phase
or project
Skills
PMP® Exam and
Preparation Training
Knowledge
Define Scope : Preparing Scope Statement
Expert
OPA
Judgment Product Scope
Charter Exclusions
Alternative
Analysis
Acceptance
Project Criteria
Management
Plan
Meeting
Project
Document
• Product or Service
• Agreements / Contrcts
• Project Charter
• Project Documents
• EEF
• OPA
• Systematic Procedures
• Formulas
Tools and
Techniques
PMP® Exam Preparation Training
ITTO
A tangible template or software program .
Examples
• Analytical techniques
•
Project management information system (PMIS)
Benchmarking
Tools
• Product analysis
Examples:
• Meetings
• Decomposition
• Data Gathering
• Data Analysis
• Data Representation
• Decision Making
Output
Output
• Work Performance Data ,Work Performance Information &
Reports
• OPA Updates
• EEF Updates
Project ManagementProcess
Group
Planning
Closing
Initiating Monitoring &
Controlling
Integration Management
Quality Resources Risk
Planning
24
Processes
Enter Phase/Start Exit Phase/End
Project Initiating Closing Project
2 Processes 1 Processes
10
Processes
Executing
Develop Project
Identify Stakeholder
Charter
Plan Scope Plan Resource Plan Risk Plan Quality Plan Cost Plan Procure
Plan Schedule Mgt Mgt
Mgt Mgt Mgt Mgt Mgt
Perform
Qualitative Determine
Define Scope Sequencing
Analysis Budget
Activities
Perform
Estimate Activity Quantitative
Create WBS Analysis
Duration
Plan
StakeMgt
Plan Risk
Develop Schedule Responses
CR
Acquire Resources
CR
Implement Risk Monitor Risk
Risk Res
PICC
Conduct Control
Procure Procurements Procurements
ACR
Knowledge Areas
Communicatio
Procurement
Stakeholder
Integration
Resource
Schedule
Process
Groups
Quality
Scope
Cost
Risk
n
2
Initiation 1 1
Process Groups
24
Planning 1 4 5 3 1 2 1 5 1 1
Execution 2 1 3 1 1 1 1 10
12
Mon & 2 2 1 1 1 1 1 1 1 1
Cont.
1
Closing 1
7 6 6 4 3 6 3 7 3 4
PMP® Exam Preparation Training
Process Group and Knowledge Area
Initiating Planning Executing Monitoring Closing
&
Controlling
Integration
Scope Scope
Schedule Schedule
Cost Cost
Knowledge Area
Quality
Resource
Communication
Risk
Procurement
Stakeholders
Determine what information you need from other projects and what information you will
share with the organization and other projects.
Hold a kickoff meeting with key stakeholders, team members, managers of team
members, and the customer to make sure everyone is on the same page and to gain
buy-in.
Recalculate how much the project will cost and how long it will take, and create
forecasts.
Exchange information about the project according to the plan, and solicit feedback to
ensure communication needs are being met.
• Standards
• Processes
• Inputs
• Tools
• Techniques
• Outputs
• life cycle phases
• Development Cycle
• Project Team
• Project Sponsor
• Organizational Management
• Project Data are regularly collected through out the project life cycle.
• The collected data are fed in to respective monitoring and controlling process.
• Then data will be analyzed, aggregated and transformed, the outcome called project information / work
performance information
• The resulted work performance information are fed into monitor and control project work (PM), the outcome
will be work performance reports
• The work performance reports will be either communicated verbally or Stored and distributed as reports.
• Compliance of requirements, • how many activities • How much work has been
have been started, completed,
• Non-conformities,
• how many activities •
• Number of change requests how much money has been
have been finished spent to date, etc.
• CR received & accepted or • the status of current
rejected, etc. ongoing activities, etc.
• Project Document
• Past performance
Scope Schedule
Review the project’s Compare the planned
progress against the schedule and actual
scope baseline schedule
Cost Quality
Analyse planned and Analyse the planned &
actual cost to find the actual technical
cost performance and performance to find the
cost variance defects.
PMP® Exam Preparation Training
PMBOK® Guide Definition
The forecast analysis of what they should expect if the project is continued in the same way, or
What additional funds, resources, or schedule extensions may be required to complete the project if there is any deviation from the
baselines.
These reports help management review the status and progress of the project and make a decision on a future course of action.
• Progress Report
• Trend Report
• Memos
• Justification
Work
• Information Notes Performance
• Electronic Dashboards
Integration Communication
Perform Integarted Change Manage Communication –
Control – Analyse Change Sending reports to respective
Request stakeholders
Resource
Management Risk Management
Manage Team Monitor Risk –
Analyse the resource Analyse Risk & Responseplan
performance information
• S-Curves
• Tables
• Run Charts
ce Reports
c. Cost levels start low then increase over time before trailing off as
the project ends
• Customizing the methodology upfront will allow us to streamline the adoption process.
• Adapting the new methodology will be a good way for the team to learn about agile
practices.
• The team should become comfortable with the new methodology before we consider
changing it.
• We should wait to adjust our practices until we see where the team runs into difficulties
applying them.