• INTRODUCTION
    • Also called waterfall/predictive: scope well defined, clear, changes not expected
    • Project manager is in control & all planning is done upfront
    • The objective is to complete the set scope in/within time and reduce the cost
    • 49 processes divided into 5 groups [Process groups: practice guide] by PMI Pg 22 of this book has the entire table w list [replaced PMBOK Guide 6th edition]
    • The goal of processes to output a deliverable — they live in every phase of the project
    • Processes that focus on predictive, but can be used for agile. Considered good practice, not mandatory
  • PROCESS GROUPS
    • Initiating: Authorize the start of project & assign project manager
    • Planning: Establish scope, define course of action for attaining objectives
    • Executing: Complete defined work
    • Monitor + Control: Track, review & regulate the progress & performance. Look for changes might be required & initiate those changes.
    • Closing: Done to formally complete/close project, phase or contract
  • PROCESSES ITTO’s: Inputs, tools, techniques, outputs
    • Inputs: starting point of the process, to begin execution [could be the output of a previous process]
    • Tools & techniques: Used to transform raw materials into output
    • Output: End result of our efforts [maybe the input into another process]
    • Each of 49 processes have ITTOs
  • ITTOs COMMON
    1. Enterprise environment factors [EEF] — an input on most of the 49 processes
      1. impact the project but not part of the project itself
      2. consider these int/ext factors while planning
      3. internal for eg: org culture, structure, appetite for risk, comm. channels, IT software, facility & resources, infrastructure, employee capability
      4. external for eg: political climate, govt/industry standard, legal/regulations, financial considerations
    2. Organization Process Assets [OPA] — widespread input
      1. knowledge base, policies & procedures, and documents — to help PMs achieve their objectives
      2. ex: project templates, software tool, historical info, procedures, guidelines, etc.
    3. Project Documents
      1. These documents are created & used throughout the 49 processes and are related to the project but not part of the project management plan
      2. 33 docs through 49 processes
      3. page 33, PMI process
    4. Project Management Plan
      1. Defines how the project is executed, monitored, controlled & closed
      2. 18 components, 14 plans & 4 baselines
    5. Expert Judgement
      1. one of the most common tools in planning
      2. includes hiring an SME [subject matter expert] to help you plan or conduct a process
      3. People with specialized knowledge/training
    6. Data Gathering, Analysis, Representation & decision-making
      1. Gathering: brainstorming, interviews, focus groups, checklist, questionnaires/survey
      2. Analysis: alternative analysis [different ways to accomplish something], RCA [root cause analysis — identify underlying reason], variance [how far off you off], trend [see where you’re going]
      3. Representation: illustrate data to stakeholders [flowcharts, fishbone diagrams, histograms]
      4. Decision-making: what to do next with the data through voting, multicriteria decision analysis, autocratic decision
    7. Tool/Technique: Interpersonal and team skills
      1. people’s person — most imp tool in real-life project mngmt
      2. methods: active listening, conflict management, facilitation, meeting mng [agenda, inviting right people, setting time limit, minutes, action items]
    8. Meetings: tool
    9. PMIS [project management information system]: technique
      1. Information system that is used PMIS: for ex: we use notion, monday
      2. automated system that is used to help PM optimize the schedule
      3. should include all software & hardware tools that we need to manage project from start to finish
      4. work authorization system & the configuration mngmt system
    10. Change Request: Output
      1. proposal to change a document, deliverable, or baseline
      2. add or remove scope, finish faster, complete more cheap, etc.
      3. types/implements: corrective action, preventive action, defect repair
    11. Work Performance Data, Info & Report: output
      1. work performance data is simply raw info: status of work done, not usually by itself, usually outputs of executing processes
      2. work performance info is the info on the work that was performed compared to the plan giving the actual status of deliverables — output of most monitor/control process
      3. work performance report: overall status report of the actual project: take all work performance info & together in one comprehensive doc.
      4. take data, compare to the project plan, to get work perf info, then all info creates work perf reports.
      5. data → info → report [executing → monitor/control]
    12. Updates: output
      1. Updates is a catchall term
      2. can include project documents, PM plan, OPA & EEF updates