Intro to Industrial Engineering Unit 11 Review: Project Management for Engineers

What's Project Management?

• Discipline involving planning, organizing, and managing resources to successfully complete specific project goals and objectives
• Involves applying knowledge, skills, tools, and techniques to project activities to meet project requirements
• Aims to deliver a unique product, service, or result with a defined beginning and end
• Requires balancing competing project constraints including scope, quality, schedule, budget, resources, and risks
• Differs from operations management focuses on ongoing, repetitive activities
• Temporary endeavor with a defined beginning and end
• Creates a unique product, service, or result
• Often involves cross-functional teams working together towards a common goal

Key Project Management Concepts

• Project scope defines the boundaries of the project, including what work will be done and what deliverables will be produced
• Work Breakdown Structure (WBS) hierarchical decomposition of the total scope of work to be carried out by the project team
• Gantt chart type of bar chart that illustrates a project schedule, showing the start and finish dates of the terminal elements and summary elements of a project
• Critical path longest sequence of activities that must be completed on time for the project to complete on due date
• Resource allocation process of assigning available resources to project tasks
• Stakeholder management process of identifying and managing individuals or groups who can impact or be impacted by the project
• Change control process used to manage changes to the project scope, schedule, or budget
• Project closeout process of finalizing all project activities, archiving documents, and transitioning resources

Project Lifecycle Stages

• Initiation phase where the project is defined, stakeholders are identified, and the project charter is created
  • Includes developing a business case and obtaining project sponsorship
  • Key deliverables project charter and preliminary scope statement
• Planning phase where the project scope is defined, the project plan is developed, and the project team is assembled
  • Involves creating a detailed project schedule, budget, and resource plan
  • Key deliverables project management plan, scope statement, WBS, and project schedule
• Execution phase where the project work is performed, and the project deliverables are created
  • Involves coordinating resources, managing stakeholder expectations, and monitoring project progress
  • Key deliverables project deliverables and progress reports
• Monitoring and Controlling phase where the project performance is measured and analyzed, and corrective actions are taken as needed
  • Involves comparing actual performance to planned performance and making adjustments as necessary
  • Key deliverables change requests, updated project plan, and project status reports
• Closing phase where the project is formally closed, lessons learned are documented, and project resources are released
  • Involves obtaining client acceptance of deliverables and archiving project documents
  • Key deliverables final project report, lessons learned document, and project archive

Tools and Techniques

• Project charter document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
• Stakeholder register document that identifies project stakeholders, their interests, and their level of influence on the project
• Responsibility assignment matrix (RAM) chart that shows the relationship between project activities and team members, clarifying roles and responsibilities
• Work Breakdown Structure (WBS) deliverable-oriented hierarchical decomposition of the work to be executed by the project team
• Gantt chart bar chart that shows the dependencies between project activities and the project schedule
• PERT (Program Evaluation and Review Technique) chart network diagram that shows the sequence of project activities and the dependencies between them
• Critical path method (CPM) technique used to estimate the minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model
• Earned value management (EVM) methodology that combines scope, schedule, and resource measurements to assess project performance and progress

Risk Management Basics

• Risk identification process of determining which risks may affect the project and documenting their characteristics
  • Techniques include brainstorming, checklists, and root cause analysis
• Risk assessment process of prioritizing risks for further analysis or action by assessing their probability of occurrence and impact
  • Can be qualitative (high, medium, low) or quantitative (numeric values for probability and impact)
• Risk response planning process of developing options and actions to enhance opportunities and reduce threats to project objectives
  • Strategies include avoid, transfer, mitigate, and accept
• Risk monitoring process of implementing risk response plans, tracking identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness throughout the project
• Risk register document that contains the results of the risk management processes, including identified risks, risk owners, and risk response strategies
• Contingency plan predefined actions that the project team will take if a specific risk event occurs
• Fallback plan alternative plan that will be executed if the original plan proves inadequate and contingency plans are unsuccessful

Team Dynamics and Leadership

• Team development process of bringing together a diverse group of individuals and forming them into a cohesive, high-performing team
  • Stages include forming, storming, norming, performing, and adjourning
• Team building activities and events designed to improve interpersonal relationships, communication, and trust among team members
• Conflict management process of identifying and addressing conflicts that arise within the project team
  • Techniques include confronting, compromising, smoothing, forcing, and avoiding
• Leadership providing direction, motivation, and support to the project team to help them achieve project objectives
  • Styles include autocratic, democratic, and laissez-faire
• Emotional intelligence ability to recognize and manage one's own emotions and the emotions of others
  • Key components include self-awareness, self-regulation, motivation, empathy, and social skills
• Communication ensuring that project information is collected, generated, distributed, stored, retrieved, and ultimately disposed of in a timely and appropriate manner
  • Methods include verbal, non-verbal, written, and visual
• Motivation process of encouraging team members to perform at their best and contribute to project success
  • Techniques include recognition, rewards, and professional development opportunities

Real-World Applications

• Construction projects (buildings, bridges, roads) require extensive planning, coordination, and risk management to complete on time and within budget
• IT projects (software development, system implementations) often involve complex technical requirements, multiple stakeholders, and rapidly changing technologies
• Research and development projects (new product development, scientific research) are characterized by high levels of uncertainty and require flexibility and adaptability
• Event planning projects (conferences, weddings, festivals) have fixed deadlines and require careful coordination of multiple vendors and stakeholders
• Disaster response projects (natural disasters, humanitarian crises) require rapid mobilization of resources and effective communication in chaotic and unpredictable environments
• Aerospace projects (satellite launches, space missions) involve cutting-edge technologies, stringent quality requirements, and significant public scrutiny
• Government projects (public infrastructure, social programs) often have complex political and regulatory environments and require transparency and accountability

Common Pitfalls and How to Avoid Them

• Scope creep gradual expansion of project scope without corresponding adjustments to time, cost, and resources
  • Avoid by clearly defining and documenting project scope and managing change requests through a formal change control process
• Unrealistic schedules and budgets setting project objectives that are not achievable given the available time, resources, and constraints
  • Avoid by involving the project team in the planning process, using historical data to inform estimates, and building in contingency buffers
• Lack of communication failing to effectively share information and coordinate activities among project stakeholders
  • Avoid by developing a communication plan, using multiple communication channels, and regularly soliciting feedback
• Inadequate risk management failing to identify, assess, and mitigate potential project risks
  • Avoid by conducting thorough risk assessments, developing risk response plans, and regularly monitoring and updating the risk register
• Poor quality deliverables producing project outputs that do not meet customer or stakeholder requirements
  • Avoid by clearly defining quality standards, conducting regular quality reviews, and involving customers in the quality assurance process
• Scope creep adding additional features or requirements to the project scope without adjusting the project timeline or budget
  • Avoid by clearly defining project scope in the project charter and managing change requests through a formal change control process
• Inadequate resource planning failing to identify and secure the necessary human, financial, and material resources to complete the project
  • Avoid by conducting a thorough resource needs assessment, identifying potential resource constraints, and developing a resource management plan