project management

Page 1: Laboratory Classes Overview

  • Defining and measuring project goals according to the SMART methodology.

  • Building a business case for the project.

  • Development of a Project charter that outlines important project information.

  • Creating a Work Breakdown Structure (WBS) to manage tasks and deliverables.

  • Estimating task duration using the PERT method.

  • Critical path determination and analysis to identify essential tasks.

  • Creation of a Responsibility Matrix and rules for verification.

  • Conducting stakeholder analysis and developing a stakeholder management plan, including a stakeholder assessment matrix.

  • Performing risk analysis, establishing risk assessments, and forming a risk matrix with possible responses to identified risks.

  • Using earned value (EV) analysis with indicators such as EV, PV, CPI, and SPI for project performance measurement.

Page 2: Lecture Topics Overview

  • Introduction to class structure and expectations.

  • Comparison of various project management methods.

  • Integration management strategies.

  • Scope management to define project boundaries.

  • Time management techniques.

  • Cost management including budget development.

  • Quality management practices.

  • Human resource management techniques.

  • Communication management strategies.

  • Risk management methodologies.

  • Order management in project operations.

  • Engaging stakeholders effectively in projects.

  • Analyzing project effectiveness post-completion.

  • Managing project changes and adjustments effectively.

  • Introduction to project portfolio management concepts.

Page 3: Software Application

  • Utilization of Microsoft Project 2019 for project management tasks.

Page 4: Project Management Definition

  • Project Management defined as the process of planning, executing, and finalizing projects effectively and efficiently.

Page 5: Project Management Roles and Structure

  • Key roles in project management include:

    • Logistic Manager

    • Marketing Manager

    • Security Manager

    • Human Resources Manager

    • IT Manager

    • Communication Manager

    • Project Manager

    • Internal Supervisor

    • PR Manager

    • Product Development Manager

    • Named example: Herbert (specific roles).

Page 6: Definition of a Project

  • A Project is defined as a unique, non-routine process aimed at creating a unique product or service.

  • A process is a sequence of logically ordered tasks/activities resulting in a specific outcome (product/service).

  • Reference: Szyjewski Z., Metodyki zarządzania projektami informatycznymi, Warsaw: PLACET 2004.

Page 7: Case Study Example

  • Projects such as Aprivia on ul. Słowackiego in Gdańsk and the National Stadium in Warsaw, which may involve penalties and issues with companies like PBG and Hydrobudowa Polska.

Page 8: SMART Goals Methodology

  • Focus on understanding and applying the SMART methodology for project goal-setting.

Page 9: Understanding SMART Methodology

  • Describes 5 characteristics of effective goals:

    • Specific: Clearly stated goals e.g., answering "Why?" and outlining methods to achieve it.

    • Measurable: Must ensure verification through clear metrics.

    • Achievable: Ensuring realistic opportunities.

    • Relevant: Goals must align with reasonable expectations and available resources.

    • Time-bound: Must have clear deadlines to foster motivation.

Page 10: Specificity in Goals

  • Goals must be specific; no ambiguity in their interpretation during project implementation.

  • A well-defined goal answers:

    • Why? (Purpose)

    • By which methods? (Approach)

Page 11: Measurable Goals

  • Goals should be measurable, allowing verification throughout the course of the project, answering:

    • When will the goal end? (Completion)

    • What will the results be? (Outcome)

Page 12: Attractive Goals

  • Goals must foster a natural inclination to achieve them, providing inherent challenges and benefits, articulating:

    • Why implement this project?

Page 13: Realistic Goals

  • Goals should be realistic and achievable within available resources, time, and strength, evaluating:

    • Am I equipped to achieve this? (Capability)

Page 14: Time-bound Goals

  • Goals must have specific timeframes established for accomplishment, answering:

    • When is the deadline? (Timeliness)

Page 15: SMART Goal Scenario Analysis

  • Evaluating whether car production stages can exemplify SMART goals with necessary components defined.

Page 16: Assessing Additional Goals

  • Example goals assessed for SMART criteria:

    • Learning first aid

    • Passing driving tests in a year

    • Unaffordable aspirations like flying into space

    • Simple tasks like buying bread on Wednesday

    • General goals like weight loss this year.

Page 17: Project Management Methodologies Comparison

  • An overview comparing Classic (Waterfall) and Agile project management methodologies.

Page 18: Classic Project Management Methodologies Overview

  • PMI founded in 1969, promoting knowledge exchange among project managers globally.

  • PMBOK serves as a standard for project management definitions and accepted practices.

  • Publications include PM Network and Project Management Journal.

  • Offers certifications like PMP and PgMP.

Page 19: PRINCE2 Overview

  • PRINCE2 (Projects IN Controlled Environments) established in 1996, focusing on structured project management methodologies.

  • Publications include managing successful projects guides and certification by APM Group Ltd.

Page 20: Methodologies Structure

  • Breakdown of PMBOK and PRINCE2 processes:

    • PMBOK: 5 process groups, 9 knowledge areas.

    • PRINCE2: structured components providing methods for comprehensive management.

Page 21: PMBOK Guide Processes

  • Core processes include initiation, planning, execution, monitoring, and control, and closing, highlighting the roles of project initiators and sponsors.

Page 22: Knowledge Areas in PMBOK Guide

  • Major knowledge areas include integration, scope, time, cost, quality, human resources, communication, risk, and procurement management.

Page 23: Project Management Process Groups

  • Division into initiating, planning, executing, and controlling processes specifies task focus within project management.

Page 24: Project Documentation per PMBOK Guide

  • Essential documentation:

    • Project Charter, Project Scope, and Project Plan.

Page 25: Project Charter Insights

  • Must include project name, description, business rationale, goals, products, constraints, stakeholders, risk assessment, and approvals.

Page 26: Project Scope Plan Details

  • Content for Project Scope plans involves product goals, requirements, acceptance criteria, boundaries, constraints, organization, milestones, and cost estimates.

Page 27: Comprehensive Project Management Plan

  • Details scope, quality, schedule, cost, procurement, human resources, communication, and risk management throughout the project.

Page 28: Project Initiation Stages

  • Encompasses stages from starting up to closing the project efficiently.

Page 29: PRINCE2 Components Clarification

  • Outlines components such as business case, progress monitoring, organizational structure, change, quality, and risk management processes.

Page 30: PRINCE2 Documentation Insights

  • Highlights product-based planning, change management approaches, and quality review techniques as central to successful project output.

Page 31: Project Triangle Explanation

  • A triangle depicting the relationship between Timeline, Quality, and Cost indicating project constraints.

Page 32: Documentation Requirements per PRINCE2

  • Discusses project charters and their essential role in project management documentation.

Page 33: Mandatory Project Charter Components

  • Context background, project goal, scope, constraints, tolerances, control, organizational structure, communication, and quality planning.

Page 34: Optional Project Charter Components

  • Include initial scope, initial plan, and initial risk log as supplemental project insights.

Page 35: Agile Manifesto Overview

  • Agile Manifesto advocates for prioritized principles such as individuals, working software, collaboration, and responsive change in software development.

Page 36: Agile Methodology Insights

  • Summary of common Agile processes, concepts, and advantages in project management.

Page 37: Agile Sprints Dynamics

  • Elaboration on Agile sprint structures: planning, reviews, and outputs throughout multiple iterations.

Page 38: Selecting Project Management Methodologies

  • Importance of adapting various methodologies to meet project specificities, emphasizing PMBOK and PRINCE2 knowledge.

Page 39: Selecting PRINCE2 for Specific Projects

  • Highlights the benefits that PRINCE2 offers for organization, planning, and managing complex project elements.

Page 40: Selecting PMBOK for Project Management

  • Advantages of using PMBOK for decomposing projects and applying useful techniques in management approaches.

Page 41: Agile Flexibility and Technique Emphasis

  • Promotes Agile's focus on team-level techniques, adaptability, iterative delivery, and minimal documentation requirement.

Page 42: Holistic Approach Necessity

  • It stresses that no single approach is the best; a multifaceted understanding is crucial.

Page 43: Class Closing

  • Expressing appreciation to the audience.

Page 44: Project Selection Methods

  • Discusses methodologies such as business cases and profitability assessments prior to project initiation.

Page 45: Project Initiation Rationale

  • Explains various reasons leading to project initiation, focusing on strategic alignment and organizational objectives.

Page 46: Decision-Making Document Requirements

  • Statement of Work (SoW) defines a project's need, while the Business Case elucidates its economic justification.

Page 47: Financial Effectiveness Assessment Overview

  • Critically assesses necessary financial viability and profitability of project outcomes against projected costs.

Page 48: Cash Flow Understanding

  • Discusses typical cash flows from project profit utilization in future revenue projections.

Page 49: Project Investment Perspective

  • Presents spending as an investment while ensuring reliable cost calculations for project execution.

Page 50: Financial Analysis Methodologies

  • Static vs dynamic analysis methods with tools like cost comparative analysis, payback period, and NPV evaluation frameworks.

Page 51: Cost Comparison Framework

  • Framework established for project realization costs alongside revenue assessment and timeline perspective.

Page 52: Break-even Point Analysis

  • Evaluates variable and fixed cost relationships with resulting revenue determination.

Page 53: Profitability Point Analysis Methodology

  • Refines assessment methodologies for single and multiple products regarding profitability metrics.

Page 54: Payback Period Analysis

  • Highlights critical time for recovering investment alongside revenue projections.

Page 55: Payback Period Examples

  • Walks through practical examples of calculating payback based on given expected revenue figures.

Page 56: Discounted Cash Flow Explanation

  • Calculations to analyze changes in monetary values, stressing the need for careful discount rate selection.

Page 57: Discounted Cash Flow Example

  • Analysis of various projects aimed at understanding cash flow repercussions based on set discount rates.

Page 58: NPV Method Evaluation

  • Explanation of NPV as the difference between revenue and investment values using discount rate factors for investment decisions.

Page 59: Exploring NPV Outcomes

  • Analyzes profitability implications resulting from evaluated NPV values across different project timelines.

Page 60: Internal Rate of Return Definition

  • Explains IRR as the discount rate at which NPV equals 0, directing project investment strategies to maximize returns.

Page 61: Summary of Financial Analysis Indicators

  • Summing critical indicators for measuring project profitability and effectiveness through various established measures.

Page 62: Financial Pragmatics in Projects

  • Dissects insights on desired payback periods, NPV, and IRR outcomes for comprehensive project evaluations.

Page 63: Project Planning Objectives

  • Establishes goals of precise project definition, task assignment, and effective management planning.

Page 64: Initiating Project Requirements

  • Key inputs cover organizational requirements, ideas for customer satisfaction, and overall necessity drivers leading to project initiation.

Page 65: Initiating Project Process

  • Focused on structured initiation phases, including charter development and stakeholder analysis incorporation.

Page 66: Input Data for Project Initiation

  • Highlights necessary input data such as product descriptions and previous project knowledge influencing the initiation phase.

Page 67: Project Charter Significance

  • Serve as an essential document that commences the project while clarifying initial stakeholder expectations.

Page 68: Typical Project Charter Content

  • Components include goals, success criteria, project description, assumptions, constraints, timeline, and budgets.

Page 69: Project Charter Preparation Process

  • Outline procedures follow established input data, business cases, contracts, and regulatory aspects.

Page 70: Stakeholder Identification Objectives

  • Primary goal is defining and analyzing stakeholder groups relevant to project execution and influence.

Page 71: Stakeholder Identification Process

  • Establishes methodologies utilized to identify stakeholders, including project charter, contracts, and documented insights.

Page 72: Summary of Project Initiation and Stakeholder Analysis

  • Goals focus on building confidence in execution bases, analyzing stakeholders, and authorizing projects.

Page 73: Project Planning Overview

  • Introduces planning goals covering aspects from project realization to change management.

Page 74: Planning Processes Overview

  • Provides insights into project management planning processes ensuring clarity in scope and requirements management.

Page 75: Comprehensive Project Management Plan Definition

  • The plan involves all management processes comprehensively outlining methods, levels, and techniques utilized across project stages.

Page 76: Project Management Planning Key Principles

  • Prepare the plan with a focus on clarity, accuracy, and integration principles guiding management processes.

Page 77: Input Data for Project Planning

  • Use various documents, organizational assets, and environmental factors guiding project planning specifications.

Page 78: Project Planning Summary

  • Emphasizes importance for a thorough, realistic management plan boosting project success.

Page 79: Reflection on Successful Projects

  • Cites the essence of proactive project management correlating with success factors throughout project execution.

Page 80: Class Closure

  • Final remarks and expressions of gratitude.

Page 81: Scope Management Overview

  • Overview of scope management covering requirements, scope definitions, and verification processes.

Page 82: Scope Management Functions

  • Setting project requirements and defining both in-scope and out-of-scope activities crucial for project definition.

Page 83: Project Scope Management Breakdown

  • Focus on planning scope management processes and structure of requirements and documentation.

Page 84: Requirements Capturing Essentials

  • Essential to establish stakeholder expectations and derive project requirements to build a WBS systematically.

Page 85: Detailed Project Requirements Definition

  • Requirement capturing includes functional and non-functional requirements that must be clearly specified.

Page 86: Requirement Capturing Techniques

  • Outline techniques such as interviews, focus groups, and workshops for effective requirements gathering.

Page 87: Outcomes from Requirement Capturing

  • Generates documentation reflecting identified requirements and management strategy tailored for the project.

Page 88: Requirement Characteristics Summary

  • Necessitates requirements to be relevant, consistent, testable, clear, feasible, and unambiguous in nature.

Page 89: Requirement Prioritization Methodology

  • Introduces MOSCOW classification for prioritizing project requirements based on necessity and importance.

Page 90: Scope Definition Process Insights

  • Constructing a clear scope statement to outline project details, controls, and definitions.

Page 91: Scope Statement Essentials

  • Clarifies the project scope, ensuring comprehensive stakeholder agreement and documented baseline for future change management.

Page 92: Goals and Criteria Alignment

  • Emphasizes SMART criteria for defining project goals and aligning them with project strategies effectively.

Page 93: Work Breakdown Structure (WBS) Definition

  • WBS outlines structured activities, presenting both hierarchical views and detailed tasks conducting within a project.

Page 94: WBS Functions Overview

  • Breakdown of WBS utility in project management aiding task communication, estimation, and control measures.

Page 95: Steps to Construct WBS

  • Identification of deliverables and systematic task decomposition pivotal for WBS construction.

Page 96: WBS Construction Principles

  • Focus on ensuring bottom-level tasks are manageable and easy to control for project management effectiveness.

Page 97: WBS Example Case Studies

  • Practical examples illustrating three-level WBS structures for clearer visualization of task breakdown.

Page 98: Constructing a House WBS Example

  • Four primary divisions and tasks involved in house construction presented through a structured WBS model.

Page 99: Tabular Representation of WBS

  • Illustrates six-level WBS in a tabular layout for detailed representation of tasks throughout project phases.

Page 100: Pragmatics of WBS Construction

  • Emphasizes the importance of WBS maintenance during project execution ensuring task clarity.

Page 101: WBS Benefits Insight

  • Identifying project scope comprehensively while providing clarity, accountability, and reporting structures.

Page 102: Detailed Scope Description Overview

  • Delineates agreements on project deliverables and clarifying scope inclusions to avoid misunderstandings.

Page 103: Scope Clarity Importance

  • Outlines the significance of precise requirements in preventing scope creep and enhancing project governance.

Page 104: Scope Verification and Control Overview

  • Describes processes ensuring alignment between project scope and initial plans with methods to prevent deviation.

Page 105: Scope Creep Identification

  • Analyzes causes for scope creep and implications for project success - recognizing potential weaknesses.

Page 106: Pragmatics for Scope Control

  • Expediting change requests while managing project updates to keep it aligned with objectives.

Page 107: Scope Control Dynamics

  • Establishes protocols for efficient change management interactions and communications for project updates.

Page 108: Scope Control Follow-ups

  • Follow through measures to ensure project remains aligned whilst managing expectations post-change.

Page 109: Class Closure

  • Final expressions of gratitude towards participants.

Page 110: Time Management Overview

  • Defining task structures, organizing activities, and estimating necessary resources for project timelines.

Page 111: Importance of Time in Projects

  • Reflects on the value of time management as a pivotal success factor in project delivery.

Page 112: Fundamentals of Time Management

  • Structuring tasks into manageable segments while ensuring correct sequencing and resource allocation.

Page 113: Processes Involved in Time Management

  • Categorization of tasks and adjustment of timelines to set an effective project schedule baseline.

Page 114: Activity Definition Process

  • Emphasizing baseline definitions in WBS for clear activity separation and management.

Page 115: Activity Management Techniques

  • Leverages techniques like decomposition and templates for comprehensive activity planning.

Page 116: Sequencing Activities Framework

  • Establishes proper connections between activities to define task order efficiently.

Page 117: Understanding Activity Relationships

  • Highlights types of task relationships and their implications for project scheduling.

Page 118: Network Diagram Drafting

  • Importance of network diagrams to visualize and optimize project activity flows effectively.

Page 119: Resource Estimation Process Description

  • Focused on identifying and allocating the required resources for project activity execution.

Page 120: Resource Estimation Techniques

  • Depicts how to utilize activity attributes, calendars, and constraints to establish accurate resource demands.

Page 121: Resource Requirement Outputs

  • Essential documentation generated outlines needed resources supporting project completion.

Page 122: Duration Estimation Process

  • Recognizing how distributed timelines impacting project completion and overall scheduling.

Page 123: Duration Estimation Principles

  • Detailing the necessary methods to ascertain complete timelines across various tasks.

Page 124: Adjusting for Activity Duration Variables

  • Outlined approaches adjust project durations based on calculated activity traits.

Page 125: Final Estimation Remarks

  • Emphasizes the significance of differentiating between time needed and effort put into tasks.

Page 126: Acknowledging Common Estimation Errors

  • Highlights frequent pitfalls encountered during project duration estimations.

Page 127: Understanding Parkinson's Law

  • Highlights the lesson regarding work expansion concerning set timelines avoiding pitfalls.

Page 128: Involving Expert Insight

  • Demystifies using structured methods like the Delphi technique to harness collective expertise for improved estimates.

Page 129: Implementing Three-Point Estimation

  • Method allowing precise activity duration forecasting while factoring in uncertainties.

Page 130: Developing the Project Schedule

  • Strategies to formulate and enhance project schedules ensuring clarity and dedication to timelines.

Page 131: Critical Path Method Analysis

  • Delineates methods to manage critical paths ensuring project deadlines remain intact.

Page 132: Pert Method Contrasts

  • Distinguishes the PERT method from CPM with focus on probabilistic scenarios and outcomes.

Page 133: Comprehensive Scheduling Outputs

  • Outputs from developing schedules inclusive of diagrams, buffers, and resource evaluations.

Page 134: Time Management Summary

  • Review of pivotal aspects targeting timeline management skills and knowledge.

Page 135: Time Management Pragmatics

  • Emphasizes ongoing adjustments and tracking for optimal time management.

Page 136: Monitoring and Control Objectives

  • Effective monitoring essential for comparing project alignment against planned procedures.

Page 137: Key Control Processes Overview

  • Centers on key subprocesses concerning project performance evaluation against initial plans.

Page 138: Project Control Dynamics

  • Highlights essential monitoring activities supporting recognition and correction of deviations.

Page 139: Change Management Objectives

  • Established frameworks ensuring systematic approaches to capturing and managing project changes.

Page 140: Change Management Activities

  • Detailed journey through change management measures ensuring alignment with project specifications.

Page 141: Exploring Conflict in Projects

  • Assessing sources of conflict and their potential resolutions standing vital for team success.

Page 142: Thank You Closing

  • Final appreciation for audience participation and insight exchange.