Project Management Principles and Practices Level 1 Agenda
- Slides: 100
Project Management Principles and Practices Level 1
Agenda n Introductions n Course Objective n Unit 1: Introduction to Project Management n Unit 2: Project Definition n Unit 3: Project Planning
Introductions n What is your Project Management Experience? n What types of projects will you be involved in? n What would you like to get out of the course?
Course Objectives n Learn what project management is and the qualities of an effective project manager. n Understand the nine knowledge areas of project management and how they can be applied to your project. n Discover the phases of a project and what deliverables are expected when. n Identify a project’s key stakeholders. n Understand the different types of business cases and how to create a Statement of Work. n Learn to be prepared for the unexpected by utilizing risk management and change control. n Learn how to organize project activities by creating a Work Breakdown Structure. n Create a network diagram to track your project’s progress. n Learn budgeting and estimating techniques.
Reference Material n Project Management n The Complete Idiot’s Guide
Unit 1 Introduction to Project Management
Introduction to Project Management n Project Failures n Project Successes n What is Project Management? n Key Functional Areas of Project Management n Project Life Cycle
Project Failure n Identify reasons that project fail
Reasons for Project Failure Chapter 3 Page 22 1. Poor project and program management discipline 2. Lack of executive-level support 3. No linkage to the business strategy 4. Wrong team members 5. No measures for evaluating the success of the project 6. No risk management 7. Inability to manage change
Project Success Criteria Chapter 1 Page 6 n On time n On budget n Meeting the goals that have been agreed upon
Iron Triangle
Pick Any Two
What is a Project? n Temporary with specific start and end dates n Unique n Progress elaboration
What is a Project Manager? Chapter 2 n Ultimately responsible for the Project’s Success n Plan and Act n Focus on the project’s end n Be a manager & leader
Seven Traits of Good Project Managers Trait 1 Enthusiasm for the project Trait 2 Ability to manage change effectively Trait 3 A tolerant attitude toward ambiguity Trait 4 Team – building and negotiating skills
Seven Traits of Good Project Managers Trait 5 A customer-first orientation Trait 6 Adherence to the priorities of business Trait 7 Knowledge of the industry or technology
Project Success 12 Golden Rules (Chapter 3) Rule #1 Thou shalt gain consensus on project outcome.
Project Success 12 Golden Rules Rule #2 Thou shalt build the best team possible.
Project Success 12 Golden Rules Rule #3 Thou shalt develop a comprehensive, viable plan and keep it up-to-date.
Project Success 12 Golden Rules Rule #4 Thou shalt determine how much stuff you really need to get things done.
Project Success 12 Golden Rules Rule #5 Thou shalt have a realistic schedule.
Project Success 12 Golden Rules Rule #6 Thou won’t try to do more than can be done.
Project Success 12 Golden Rules Rule #7 Thou will remember that people count.
Project Success 12 Golden Rules Rule #8 Thou will gain the formal and ongoing support of management and stakeholders.
Project Success 12 Golden Rules Rule 9 Thou must be willing to change.
Project Success 12 Golden Rules Rule 10 Thou must keep others informed of what you’re up to.
Project Success 12 Golden Rules Rule 11 Thou must be willing to try new things.
Project Success 12 Golden Rules Rule 12 Thou must become a leader
Project Management Chapter 4 n Project Management n The “application of knowledge, skills, tools and techniques to project activities to meet project requirements. ” n 9 Knowledge areas
Integration Management n Fitting everything together n Planning n Project Changes
Project Scope Management n Clear scope statement n Prevent scope creep
Project Time Management n Time and Schedule n Planning n Managing
Project Cost Management n Manage costs n Out of your control n Competing projects
Project Quality Management n Planning quality n Enforcing quality n Checking quality control
Project Human Resource Management n Organizational planning n Staff acquisition n Making a team
Project Communications Management n Communication plan
Project Risk Management n Risk management plan
Project Procurement Management n Acquisition and contract management
Project Life Cycle Chapter 5
Project Definition Phase n Initiate the project n Identify the Project Manager n Develop the Project Charter n Conduct a Feasibility Study n Define Planning Phase n Sign off on the Project Charter
Project Planning Phase n Organize and staff the project n Develop a Project Plan n Sign off on the Project Plan
Project Execution Phase n Execute the Project Plan n Manage the Project Plan n Implement the project’s results n Sign off on project’s completion
Project Close-out Phase n Document the lessons learned during the project n After-implementation review n Provide performance feedback n Close-out contracts n Complete administrative close-out n Deliver project completion report
Project Life Cycle Flow Know Partial Answer Execution Pr oj ec HOW Solution Space t. P lan nin g Don’t Know Problem Space Partial Answer Project Definition Don’t Know WHAT
Unit 1 Review n What is Project Management? n Key Functional Areas n Project life cycle
Unit 2 Project Definition
Project Definition n Stakeholder Identification n Business Case n Risk n Constraints
Stakeholder Identification Chapter 6 n Stakeholder definition n Key stakeholders to identify n Project sponsor n Customer n Project team n Functional managers n Communicate with everyone n Manage conflicts in priorities
The Customer n Uses the product or services n May be internal or external n Provides requirements n May have multiple categories
Project Sponsor n Also shares responsibility for project success n Has authority to make decisions and may provide funding n Overcome political and organizational obstacles
Steering Committee n Group of stakeholders who approve and agree on: Project scope n Schedule n Budgets n Plans n Changes n
Working Committee n Line managers who are responsible for delivering business results once the project is completed
Functional Managers n May manage or supply people that work on the team n Need to be communicated with n Need their commitment to the project
Activity n Read case study n Identify stakeholders n Project sponsor n Customer(s) n Functional Managers n Steering committee n Working committee
Business Case Chapter 7 n Reasons why the project is undertaken n Options that were considered n Benefits that are hoped to be realized n High-level risks n High-level costs & schedule n Cost/benefit analysis
Feasibility Study n A general estimate used to determine whether a particular project should be pursued.
Business Goals & Objectives n Need to understand: n Goals (the need for the project and the measurable benefits) n Scope n Time to complete n Estimates of timeline, resource requirements and costs
SMART goals n S – Specific n M – Measurable n A – Agreed upon n R – Realistic n T – Time related
Statement of Work (SOW) n Purpose statement n Scope statement n Project deliverables n Goals & objectives n Cost and schedule estimates n Stakeholders n Chain of command n Benefits and risks n Assumptions and constraints n Communication plan
Activity n Create a SOW for the case study n Purpose n Scope n Project deliverables n Goals and objectives n Cost and schedule estimates
Risk management Chapter 8 n Identify n Sources of risk n n n n Funding Time Staffing Customer relations Project size and/or complexity Overall structure Organizational resistance External factors
Risk Analysis n Probability n Impact n Overall exposure = probability X impact
Risk Plan n Accept n Avoid n Mitigation n Contingency with trigger n Transfer
Risk Track and Control n Risk log n Review and update regularly n Assign ownership to risk
Constraints n Real-world limits n Typical constraints: n Budget n Schedule n People n Real world n Facilities and equipment
Activity n Identify the risks and constraints in the case study
Unit 2 Review n Project Definition n Stakeholder identification n Business Case n Risk n Constraints
Unit 3 Project planning
Project Planning n Work Breakdown Structure n Network diagramming n Scheduling n Budgeting
Work Breakdown Structure (WBS) Chapter 9 n Breaks large project into manageable units Total project n Subprojects n Milestones (completion of an important set of work packages) n Major activities (summary tasks) n Work packages (tasks, activities, work elements) n
WBS n Helps to: n Identify all work needing to be done n Logically organize work so that is can be scheduled n Assign work to team members n Identify resources needed n Communicate what has to be done n Organize work using milestones
WBS 1. Break work into independent work packages that can be sequenced, assigned, scheduled and monitored 2. Define the work package at the appropriate level of detail 3. Integrate the work packages into a total system 4. Present in a format easily communicated to people. Each work package must have a deliverable and a time for completing that deliverable 5. Verify the work packages will meet the goals and objectives of the project
Work Packages n Way of managing the project by breaking it down n Help determine skills required and amount of resources needed n Communicate work that needs to be done n Work sequences are identified and understood
WBS tips n Deliverables should be clearly stated n All work in the same package should occur at the same time n A work package should only include related work elements
Activity n List all work packages required for the case study
Network Diagrams Chapter 10 n Logical representations of scheduled project activities n Define the sequence of work in a project n Drawn from left to right n Reflect the chronological order of the activities
WBS and Network Diagram n WBS: what needs to be done n Network Diagram: shows the workflow, not just the work
Precedence n Precedence defines the sequencing order n How work elements are related to one another in the plan
Concurrent (Parallel) activities n Many activities can be done at the same time as long as resources are available
Network Diagram rules n Boxes hold description of each task n Lines connect activities to one another n Activities are laid out horizontal from left to right n Parallel activities are in the same column n Precedence is shown by drawing lines from activity to activity n One activity may depend on the completion of multiple other activities
Lead and Lag n Lead – amount of time that precedes the start of work on another activity n Lag – amount of time after one activity is started or finished before the next activity can be started or finished
Other network diagrams n PERT – Performance Evaluation and Review Technique Better for software-oriented projects n Uses 3 time estimates to determine most probable n n CPM – Critical Path Method n Better for construction type projects n One time estimate
Activity n Create a network diagram from the WBS for the case study
Scheduling Chapter 11 1. Establish scheduling assumptions 2. Estimate the resources, effort and duration • • Effort – time that it takes to work on the activity Duration – the time to complete the activity 3. Determine calendar dates for activities 4. Adjust individual resource assignments 5. Chart final schedule
Estimating Time n Have people who are doing the work provide the estimates n Get an expert’s estimate n Find a similar task n Look for relationship between activity and time (parametric estimate) n Educated guess
PERT Estimating n Optimistic estimate (OD) n Most likely (MLD) n Pessimistic estimate (PD) n Expected = [OD + 4(MLD) +PD] / 6
Contingency n Don’t pad estimates n Will never get good estimates n Adds expense and time n Add contingency as an activity n Typically 10 -15%
Critical Path & Float Chapter 12 n Critical Path n Sequence of tasks that forms the longest duration of the project n Float n Amount of time that an activity may be delayed from its earliest possible start date without delaying the project finish date n Latest possible finish date – earliest possible start – duration = total float
Normalizing the Schedule n Assign people to the schedule n Start with the critical path first, non- critical tasks second
Loading and Leveling n Resource Load – the amount of work that is assigned to a resource n Resource Leveling – redistribution to even out the distribution of work across all resources
Scheduling Tips n Ensure that learning time is identified n Ensure that administration time is included n Be aware that resources seldom work 100% of the time on one project
Activity n Create a schedule for the case study
Budgeting Chapter 13 n Budget = People + Resources + Time
Budgeting Levels n Ballpark Estimate n Rough Order of Magnitude n Detailed Estimate
Direct & Indirect Costs n Direct costs n Directly attributed to the project n Indirect costs n Shared amongst other projects
Types of Budgeting n Bottom-up n Top-Down n Phased
Contingency Reserve n 10 -15% of budget is normal n Don’t pad but manage the contingency
Activity n Build a budget for the case study
Unit 3 Review n Project Planning n WBS n Network Diagrams n Scheduling n Budgeting
Wrap-up n Evaluations n Next Course n Principles and Practices part 2 n n n n n Leadership Operating guidelines Project teams Communication plan Procurement management Quality management Monitoring and controlling Close-out activities Common project problems
- Project management principles and practices
- Project management principles and practices
- Change management principles and practices
- Risk management principles and practices
- Basic principles of cost management in project management
- Agenda sistemica y agenda institucional
- It infrastructure project management best practices
- Critical practices in software project management
- Best practice erp implementation
- Importance of software project management
- Sdlc principles and practices
- Security program and policies principles and practices
- Security program and policies principles and practices
- Security program and policies principles and practices
- Security program and policies principles and practices
- Broadcasting principles and practices
- Florida real estate principles practices & law
- Infection control principles and practices milady
- Language assessment principles and classroom practices
- What is this
- Language assessment principles and classroom practices
- Corrupted size vs. prev_size:
- Corporate governance principles policies and practices
- Codes standards and practices lesson 1
- Tourism: principles, practices, philosophies
- Involuntary inactive real estate license florida
- 8 principles of evidence based practices
- Florida real estate principles practices & law
- Florida real estate principles practices
- Florida real estate principles practices
- Example of no brokerage relationship
- Project portfolio management guiding principles
- Inoculation marketing
- Second level agenda setting
- Agenda architecture
- Ssis protection level best practices
- Kick off meeting agenda for construction project
- Project review agenda
- Pmo project intake process
- The role of project management in achieving project success
- Modern process transitions in spm
- Project cost-duration graph
- Introduction to project management kathy schwalbe
- What is strategic assessment in software project management
- Perpetual project closure
- Ms project agile
- Types of project termination in project management
- Flipchart on safety practices and sports injury management
- Management practices across firms and countries
- How to interpret confidence intervals example
- Confidence level and significance level
- Confidence level and significance level
- Data flow diagram level 0 1 2 examples
- Agenda management systems
- Management review agenda
- Value management workshop agenda
- Prm vs. crm
- Contemporary management practice
- Security management practices
- Conclusion of nursery management
- Sales territory management best practices
- Data quality management best practices
- Grant management best practices
- Supplier contract management best practices
- Fleet maintenance management system best practices
- Change management network infrastructure
- Dhirubhai ambani management practices
- Treasury management best practices
- Sap best practices help
- Prudent financial management practices
- Te expenses best practices
- Epic training uw
- Altiris patch management best practices
- Contract management best practices matrix
- Disability management best practices
- Internet lead response best practices
- Outsourced offshore testing
- Beef cattle management practices crossword
- Fscm collection management best practices
- Asset management vs project management
- Configuration management system pmp
- Define software configuration management
- Project integration management example
- Unit 543 research project examples
- Level design principles
- Principles of level design
- What does fifo stand for in food safety
- Principles of customer service level 2 answers
- Principles of customer service level 2 answers
- Molecular level vs cellular level
- Isis level 1 vs level 2
- Isis level 1 vs level 2
- Level security
- Costa levels
- Instruction level parallelism vs thread level parallelism
- Low-level thinking in high-level shading languages
- Grade 4 pfp
- Top management and middle management
- Top management middle management first line management
- Top management and middle management
- Scheduling principles in software engineering