Professional Documents
Culture Documents
A complex, non-routine, one-time effort limited by time, budget, resources, and performance
specifications designed to meet customer needs.
Has an established objective
Defined life span, with beginning and end
Typically requires cross organizational participation
Can involve doing something never done before
Has specific time, cost, and performance requirements
Program
Series of coordinated, related, multiple projects that continue over time
Higher level group of projects targeted at a common goal
Project Management
Balance technical (quality), schedule, cost
Customer, management, team expectations
Identify project requirements and customer expectations
Projects v Routine operations
Unique v repetitive
Limited life v continuous
Multiple stakeholder v departments
Management
Perceived risk
Project size
Project complexity
These three determine the amount of detail of planning, when planning effort occurs,
functionality requirements, amount of reporting
Project Life Cycle- divided into different phases to better management control, slow start, buildup speed,
and slowdown near completion
Defining
Planning
Executing
Closure
A project manager must
Manage temporary, non-repetitive activities and frequent acts independently of the formal org.
Appropriate resources
Provide direction, coordination and integration to project team
Manage stakeholders
Ask others for technical answers
Responsible for performance and success of project
Organizational strategy
Global competition
Shortened product life cycles
Industry consolidation
Accountability
Strategic management
Responding to changes
Allocate resources
Link mission, goals, objectives, strategy, and implementation
SMART
Specific-state action needed
Measurable-measure quality and quantity
Assignable-divide up tasks to people
Realistic-objectives challenging but not too much
Time- set deadlines
Project portfolio system
Select different projects for implementation
Matches strategic goals of company
Compliance (must do)
Operational Projects
Strategic projects
Project Selection
Financial
Payback model-emphasizes cash flow
Ignores time value of money
=project costs/annual savings
Net Present Value (NPV)
Uses desired rate of return to compute inflows and return of cash
+= approve, - = reject
Non-financial
Capture larger market share
Stop competitors
Make better project
Develop technology
Reduce dependency on unreliable suppliers
Comply with government intervention and regulation
Weighted
Project Proposal
Request for proposal (RFP)
Statement of work (SOW) detailing scope and major deliverables
Cost
Type of contract
Organizational Planning
Purpose-identify, document, and assign roles and responsibilities
Balance need of project with needs of organization
Project Organization Structures
Functional
One clear supervisor
Used when interest of one functional area dominates the project
Different groups: marketing, engineering, manufacturing, procurement
Dedicated Teams
Full time project manager
Teams operate as separate units
Separate teams drawn out
Matrix Structure
Two chains of command, functional and project
Optimizes the use of resources
Draws people from everywhere
Organizational culture
A system of shared norms, beliefs, values and assumptions which bind people together, creating
shared meanings
Job v Organization
Loose v Tight Control
Internal v External
Low risk v High risk
Define Project
Scope and Requirements
Scope-definition of end result or mission of project
Give deliverables for customers
Milestones, requirement, limits, and reviews with customer
Planning tool
Scope Statement- Statement of Work (SOW)
Project Charter- Authorizes the project manger
Scope Creep
Changes to the scope over time
Know: Contract, Schedule, Cost, and Technical
Requirements- Complete, Consistent, Correct, Unambiguous, Measureable, traceable,
design-free, necessary
Project Priorities
Project Trade-offs
Shifts in relative importance of criteria related to cost, time, and performance
Constrain-Fixed requirement
Enhance- optimizing a parameter over others
Accept-reducing or not meeting a parameter
Scope v Cost v Time=Quality
Work Breakdown Structure
Deliverable oriented hierarchical decomposition of work to be executed by the project
team to accomplish the project objectives and create the required deliverables,
defines the total scope of the project
Decomposes work into manageable tasks to be defined, scheduled, budgeted
Helps evaluate cost, time, and technical performance
Helps the development of the organization breakdown structure (OBS)
Hierarchy
Project
Deliverable
Sub deliverable
Lowest sub deliverable
Cost account
Work Package
How low?
All activities do not usually end up at the same level throughout WBS
OBS- Defines organizational unit responsible for performing the work
Integrate WBS with OBS
Responsibility Assignment Matrix (RAM)
A structure that relates the project OBS to the WBS to ensure that each
component of the projects scope of the work that assigned to the person
or team
Defines a single person with authority and accountability
Intersection points are control accounts
Focal point for data collection and comparisons of work performed
against the plan
Create the Project control point (control account) that integrates work and responsibility
Large projects, projects with distributed teams
Stakeholder Communications
Low Power to High Power v Low interest to high interest
Project Communication Plan
Maps out the flow of information on the project
What info needs to be collected?
Who, and what methods with be used
When?
How?
Stakeholder analysis => Info Needs => Sources of info => Dissemination modes =>
Responsibility and timing
Estimating Projects
The process of forecasting or approximating the time and cost of completing project deliverables
Balancing the expectations of stakeholders and the need for control
Top-Down
Group consensus or mathematical relationships
Strategic decision making
High Uncertainty
Internal, small project
Unstable scope
Bottom up
Uses WBS, document of estimate in a Basis of Estimate (BOE)
Time consuming and costly
Justify costs
Fixed price contract
Customer wants details
Cost and time important
Use both top and bottom to validate estimates
Guidelines
Have people familiar with tasks make the estimate
Have several people to make estimates
Base estimates on normal conditions, efficient methods and a normal level of resources
Use consistent time units
Treat each task as independent
Do not make allowances for contingencies
Add risk assessment