PMP Process

Process Detailed Explanation

The Process domain focuses on applying technical project management skills and following established processes to deliver a project successfully. It forms the backbone of project execution and ensures that goals are achieved using structured approaches.

2.1 Execute Project with the Urgency Required to Deliver Business Value

Executing a project with urgency ensures that the organization receives its expected benefits as early as possible.

Understanding Business Value

• Definition: Business value refers to the benefit the project brings to the organization.

  • Examples of business value include:
    • Return on Investment (ROI): The financial gain compared to the project cost.
    • Cost Savings: Reducing operational or production costs.
    • Competitive Advantage: Improving the company’s market position.
    • Customer Satisfaction: Enhancing product/service quality to meet customer needs.

• Steps to Ensure Business Value:

  1. Define Project Objectives: Align project deliverables with business goals.
     • Example: If the business goal is to save 10% in operational costs, the project scope must focus on process improvements.
  2. Track Value Delivery: Monitor tasks and milestones to confirm they align with business objectives.

Urgency in Execution

• Prioritizing Critical Activities:

  • Use the Critical Path Method (CPM) to identify tasks that directly impact the project timeline.
    • Critical Path: The sequence of tasks that determines the shortest project duration.
    • Example: If Task A, B, and C must happen in sequence, and Task B is delayed, the entire project will be delayed.

• Identifying and Removing Delays:

  • Recognize bottlenecks (e.g., resource unavailability, process inefficiencies).
  • Take action to remove delays:
    • Fast-Tracking: Perform tasks in parallel instead of sequentially (riskier).
    • Crashing: Add extra resources to speed up activities (increases cost).

Example: If software testing is delaying the release, you can fast-track by starting documentation and training before testing is complete.

2.2 Manage Communications

Effective communication ensures that the right information reaches the right stakeholders at the right time.

Communication Planning

• Develop a Communication Management Plan:
  • Identify:
    • Who: Stakeholders to communicate with.
    • What: Information to share (status updates, issues, deliverables).
    • When: Frequency (daily, weekly, monthly).
    • How: Communication methods (email, meetings, dashboards).

Communication Methods

1. Push Communication:

   • Information is sent to stakeholders.
   • Examples: Emails, reports, memos.
   • Best for: Stakeholders who need general updates but do not need to respond immediately.

2. Pull Communication:

   • Stakeholders retrieve information when they need it.
   • Examples: Shared folders, project websites, dashboards.
   • Best for: Large teams or stakeholders who prefer self-service access to information.

3. Interactive Communication:

   • Two-way communication.
   • Examples: Meetings, calls, instant messaging, feedback sessions.
   • Best for: Critical discussions, decision-making, or resolving issues.

Monitor Communication Effectiveness

• Feedback Loops:
  • Collect feedback from stakeholders to ensure messages are clear and effective.
  • Example: After sending a report, confirm the recipient understood the data and its implications.
• Adjust Communication Strategies:
  • Modify communication frequency, content, or methods based on feedback.

2.3 Assess and Manage Risks

Risk management identifies, analyzes, and responds to uncertain events that may affect the project. Managing risks reduces the likelihood of negative impacts and enhances project success.

Risk Management Processes

1. Identify Risks:

   • Use tools and techniques to uncover potential risks:
     • Brainstorming: Collect risk ideas from the team.
     • SWOT Analysis: Analyze project strengths, weaknesses, opportunities, and threats.
     • Expert Judgment: Consult experienced team members or stakeholders.
   • Document risks in a Risk Register.

2. Qualitative Risk Analysis:

   • Prioritize risks based on their likelihood and impact using a Probability-Impact Matrix.
     • High Probability + High Impact = Critical Risk.
   • Example: A delay in critical components delivery is a high-probability, high-impact risk.

3. Quantitative Risk Analysis:

   • Use numerical methods to measure risk impact. Common tools include:
     • Monte Carlo Simulation: Simulate project outcomes based on risk probabilities.
     • Sensitivity Analysis: Determine which risks have the highest impact.

4. Plan Risk Responses:

   • Avoid: Eliminate the risk entirely (e.g., changing project scope).
   • Mitigate: Reduce the impact or likelihood of the risk (e.g., using backups).
   • Transfer: Shift risk ownership to a third party (e.g., insurance, contracts).
   • Accept: Acknowledge the risk but do nothing (e.g., low impact risks).

5. Implement Risk Responses:

   • Execute the planned responses and monitor their effectiveness.

Monitor Risks

• Regularly review the Risk Register to track active risks.
• Look for new risks as the project progresses.
• Conduct periodic risk reviews and update mitigation plans.

Example: If the risk of a supplier delay increases, escalate to alternative vendors to avoid impact.

2.4 Engage Stakeholders

Engaging stakeholders effectively ensures their support, involvement, and alignment throughout the project lifecycle. Active collaboration with stakeholders reduces risks, resolves conflicts, and improves project outcomes.

Stakeholder Identification and Analysis

1. Identify Stakeholders:

   • Stakeholders are individuals, groups, or organizations that can influence or be influenced by the project.
   • Tools for identification include:
     • Stakeholder Register: A document listing stakeholders, their roles, and contact details.

2. Analyze Stakeholders:

   • Determine each stakeholder’s level of power (influence) and interest (engagement):
     • Use the Power-Interest Grid to classify stakeholders:
       • High Power, High Interest: Manage closely (e.g., sponsors).
       • High Power, Low Interest: Keep satisfied (e.g., executives).
       • Low Power, High Interest: Keep informed (e.g., team members).
       • Low Power, Low Interest: Monitor with minimal effort.
   • Example: A CEO has high power and high interest, so you must keep them actively informed and engaged.

Engagement Strategies

1. Collaborate with Stakeholders:

   • Understand their expectations, needs, and concerns through:
     • One-on-one meetings.
     • Surveys or interviews.
   • Example: If a key stakeholder wants faster updates, adjust the frequency of project reports.

2. Plan for Engagement:

   • Develop a Stakeholder Engagement Plan that outlines:
     • Who to engage.
     • How and when to communicate.
     • Preferred communication methods (e.g., email, calls, in-person meetings).

3. Maintain Involvement:

   • Use regular updates, workshops, or reviews to keep stakeholders engaged.
   • Hold status meetings and involve stakeholders in decision-making to maintain their support.

Monitor Stakeholder Engagement

1. Regular Reassessment:

   • Stakeholder needs and influence may change over time.
   • Continuously review their engagement level and adapt strategies as needed.

2. Engagement Metrics:

   • Measure how effectively stakeholders are engaged by tracking their participation in meetings, response rates, and feedback.
   • Example: If stakeholders are disengaged, you may need to increase face-to-face interactions to rebuild trust.

Benefits of Effective Stakeholder Engagement

• Reduces resistance to changes and builds trust.
• Improves project alignment with business goals.
• Resolves issues faster by leveraging stakeholder support.

2.5 Plan and Manage Budget and Resources

Budget and resource management ensures that the project has the necessary financial and human resources to meet its objectives efficiently.

Budget Planning

1. Estimate Project Costs:

   • Use the following techniques to predict project expenses:
     • Analogous Estimating: Use costs from previous similar projects as a reference.
       • Example: “Project X cost $100,000, so this project will likely have similar expenses.”
     • Parametric Estimating: Use statistical relationships (e.g., cost per square foot or per hour).
       • Example: “Each software feature costs $5,000 to develop.”
     • Bottom-Up Estimating: Sum up detailed cost estimates for each task or activity.
       • Example: Estimate costs for coding, testing, and documentation individually, then combine them.

2. Develop Cost Baselines:

   • A cost baseline is the approved budget for the project, including contingencies.
   • The baseline helps monitor and control costs during project execution.

Resource Planning

1. Identify Resource Needs:

   • Use tools like:
     • Resource Breakdown Structure (RBS): A hierarchical breakdown of resources (people, equipment, materials).
     • RACI Chart: Defines roles and responsibilities:
       • Responsible: Who performs the task.
       • Accountable: Who makes decisions.
       • Consulted: Who provides input.
       • Informed: Who is kept updated.

2. Balance Resource Availability:

   • Ensure that resources are allocated efficiently across tasks.

Resource Optimization

1. Resource Leveling:

   • Adjust schedules to resolve resource conflicts (e.g., when someone is overbooked).
   • Example: Shift non-critical tasks to later dates to balance workloads.

2. Resource Smoothing:

   • Adjust resource allocation within project constraints without changing the project schedule.
   • Example: Spread tasks evenly across team members to avoid overtime.

Benefits of Effective Budget and Resource Management

• Prevents cost overruns and resource shortages.
• Ensures efficient use of human and financial resources.
• Improves project predictability and stakeholder confidence.

2.6 Plan and Manage Schedule

Schedule management ensures that tasks are completed on time to meet project deadlines.

Schedule Planning

1. Define Activities:

   • Break the project scope into smaller tasks using the Work Breakdown Structure (WBS).
   • Example: “Develop Feature A” is broken into coding, testing, and documentation.

2. Sequence Activities:

   • Identify dependencies between tasks using:
     • Precedence Diagramming Methods (PDM):
       • Finish-to-Start (FS): Task B cannot start until Task A finishes.
       • Start-to-Start (SS): Task B starts when Task A starts.
       • Finish-to-Finish (FF): Task B finishes when Task A finishes.

3. Estimate Durations:

   • Use tools to predict how long tasks will take:
     • Three-Point Estimating (PERT): Use optimistic, pessimistic, and most likely durations.
       • Formula: .
     • Example: If a task has 2 days (optimistic), 4 days (most likely), and 8 days (pessimistic), the average duration is days.

4. Develop the Schedule:

   • Use tools like:
     • Critical Path Method (CPM): Identify the longest path through the project.
     • Gantt Charts: Visualize task timelines.
     • Schedule Network Diagrams: Show dependencies and task sequences.

Schedule Monitoring

1. Analyze Variances:

   • Use Earned Value Management (EVM) to compare planned vs. actual progress.
     • Schedule Variance (SV) = Earned Value (EV) - Planned Value (PV).

2. Adjust for Delays:

   • Crashing: Add resources to speed up tasks (increases cost).
   • Fast-Tracking: Perform tasks in parallel instead of sequentially (higher risk).

Benefits of Schedule Management

• Ensures project completion on time.
• Improves predictability of deliverables.
• Helps identify delays early and take corrective actions.

2.7 Plan and Manage Quality of Products/Deliverables

Ensuring product and deliverable quality is critical for meeting stakeholder expectations and project success. Quality management ensures that processes and outputs are efficient, defect-free, and meet established standards.

Quality Planning

Quality planning involves defining the quality objectives and the standards that the project’s deliverables must meet.

1. Define Quality Objectives:

   • Identify the performance goals and quality benchmarks for the deliverables.
   • Example: “The software must meet a response time of under 2 seconds for 95% of operations.”

2. Set Performance Metrics (KPIs):

   • KPIs (Key Performance Indicators) are measurable indicators used to track performance.
   • Examples:
     • Number of defects per 1,000 lines of code.
     • Customer satisfaction rate (e.g., surveys).

3. Identify Quality Standards:

   • Standards might come from industry best practices, organizational policies, or external bodies like ISO.
   • Examples:
     • ISO 9001: Quality management system standards.
     • Organizational benchmarks for defect rates, safety, or efficiency.

4. Tools for Quality Planning:

   • Cost of Quality (COQ): Understanding the cost of achieving quality vs. not achieving it.
     • Prevention costs: Training, process improvements.
     • Appraisal costs: Testing, inspections.
     • Failure costs: Rework, recalls.

Quality Assurance

Quality assurance ensures that processes are being followed correctly to meet quality goals. It focuses on prevention rather than correction.

1. Conduct Process Audits:

   • Review processes to ensure compliance with quality standards.
   • Example: Auditing the software development lifecycle (SDLC) to ensure proper code reviews and testing procedures.

2. Quality Tools for Assurance:

   • Benchmarking: Comparing project processes with industry best practices.
   • Process Analysis: Analyzing and improving inefficient processes.

Quality Control

Quality control involves monitoring and inspecting deliverables to identify defects or deviations from standards.

1. Perform Inspections and Testing:

   • Regular checks to validate the deliverable against quality criteria.
   • Examples: Code testing, product sampling, physical inspections.

2. Tools for Quality Control:

   • Pareto Analysis: Identifying the most common causes of defects using the 80/20 rule (80% of problems come from 20% of causes).
   • Control Charts: Monitoring process stability over time to detect variations.
   • Cause-and-Effect Diagrams (Ishikawa/Fishbone): Identifying root causes of defects or quality issues.

3. Analyze and Correct Defects:

   • Log defects in a defect tracking system and assign corrective actions.
   • Example: In software testing, developers fix bugs identified during quality control reviews.

Benefits of Quality Management

• Reduces the cost of rework and failures.
• Increases stakeholder satisfaction by meeting or exceeding expectations.
• Ensures deliverables meet organizational and regulatory standards.

2.8 Plan and Manage Procurement

Procurement refers to the process of acquiring goods, services, or resources from external suppliers. Effective procurement management ensures the project has the necessary support to meet goals while controlling costs and risks.

Procurement Planning

1. Identify Procurement Needs:

   • Determine what resources or services must be procured externally.
   • Use make-or-buy analysis to decide whether to:
     • Make: Use internal resources.
     • Buy: Outsource to vendors.

2. Develop Procurement Strategies:

   • Define how procurements will be conducted, such as contract types and evaluation criteria.

Types of Contracts

1. Fixed Price (FP):

   • The price is agreed upon upfront and does not change.
   • Best for: Clearly defined scope and requirements.
   • Example: “Build a website for $10,000.”

2. Cost-Reimbursable (CR):

   • The buyer pays the actual costs plus an agreed-upon fee.
   • Best for: Uncertain or evolving scopes.
   • Example: “Development costs plus a 10% fee.”

3. Time and Material (T&M):

   • A blend of fixed price and cost-reimbursable where payment is based on labor hours and materials used.
   • Best for: Short-term or undefined scope.
   • Example: “$100 per developer hour plus material costs.”

Vendor Management

1. Procurement Activities:

   • Create procurement documents: Request for Proposal (RFP), Request for Quotation (RFQ).
   • Conduct bid evaluations to select vendors.
   • Negotiate terms and finalize contracts.

2. Monitor Vendor Performance:

   • Track deliverables against the contract using:
     • Procurement Performance Reviews: Assess vendor progress.
     • Procurement Audits: Verify compliance with contract terms.

3. Resolve Procurement Issues:

   • Address vendor delays, quality problems, or scope deviations promptly.
   • Example: If a vendor misses a delivery, escalate the issue and identify alternatives.

Benefits of Effective Procurement Management

• Ensures timely availability of resources and services.
• Reduces project risks through structured vendor management.
• Optimizes costs through effective contract negotiation.

2.9 Manage Project Artifacts

Project artifacts are documents, records, and deliverables that support the planning, execution, and monitoring of a project. Proper management ensures accuracy, accessibility, and compliance.

Artifact Management

1. Maintain Project Documents:

   • Examples of artifacts include:
     • Project Plans: Scope, schedule, and resource plans.
     • Baselines: Cost, time, and scope baselines for performance measurement.
     • Change Logs: Records of approved changes.
     • Issue Registers: Lists of current project issues.

2. Ensure Version Control:

   • Use tools like document repositories (e.g., SharePoint, Google Drive) to maintain the latest versions of documents.

3. Accessibility:

   • Ensure team members and stakeholders can access the required artifacts when needed.

Document Reviews

1. Periodic Audits:

   • Review artifacts to ensure accuracy, completeness, and compliance.
   • Example: Conducting a monthly audit of change logs to confirm proper approvals.

2. Validation:

   • Validate project documentation before submission to stakeholders or regulatory bodies.

Benefits of Managing Artifacts

• Provides a reliable reference for decision-making.
• Ensures compliance with standards and regulations.
• Improves project transparency and communication.

2.10 Determine Appropriate Project Methodology

Selecting the right project methodology ensures that the processes, tools, and techniques used are tailored to the project’s goals, scope, and organizational needs.

Methodology Selection

1. Predictive (Waterfall) Methodology:

   • Definition: A linear, step-by-step approach where the project scope, timeline, and deliverables are defined upfront.
   • Best Suited For:
     • Projects with well-defined requirements and minimal changes.
     • Large infrastructure projects, construction, or projects with fixed deliverables.
   • Phases: Initiation → Planning → Execution → Monitoring/Controlling → Closure.
   • Example: Building a bridge or manufacturing a standard product.

2. Agile Methodology:

   • Definition: An iterative, incremental approach that delivers small portions of the project in shorter time cycles (sprints). Agile promotes adaptability to change.
   • Best Suited For:
     • Projects with evolving requirements or where frequent changes are expected.
     • Software development, creative projects, or product innovation.
   • Key Concepts:
     • Scrum: Uses roles like Scrum Master, Product Owner, and sprints for delivery.
     • Kanban: Visualizes workflows to manage tasks (e.g., Trello boards).
     • Lean: Focuses on minimizing waste and maximizing value.
   • Example: Developing a new mobile app where requirements may change based on user feedback.

3. Hybrid Methodology:

   • Definition: A combination of predictive and agile methods. It applies agile techniques for specific project phases while using waterfall for others.
   • Best Suited For:
     • Projects where parts are well-defined while others are uncertain.
     • Example: A software project with a fixed hardware integration phase (predictive) and iterative software updates (agile).

Tailoring Processes

Tailoring means adjusting the project management processes, tools, and techniques to meet specific project needs.

1. Assess Project Requirements:

   • Scope, complexity, and size of the project.
   • Stability of requirements (fixed vs. evolving).

2. Choose the Best Approach:

   • Determine if predictive, agile, or hybrid methodologies are best based on the project’s context.

3. Customize Tools and Techniques:

   • Adapt techniques like communication plans, scheduling tools, and risk management approaches to suit the methodology.

Benefits of Methodology Selection

• Ensures the project approach aligns with stakeholder expectations and project complexity.
• Allows for flexibility when requirements are uncertain.
• Improves efficiency and resource utilization.

2.11 Manage Project Issues

Project issues are unplanned events that occur during project execution and require immediate attention. Managing issues effectively ensures they don’t derail project progress.

Issue Identification and Tracking

1. Identify Issues:

   • Issues can include technical failures, resource shortages, scope disagreements, or stakeholder conflicts.
   • Example: A key team member unexpectedly leaves the project.

2. Log Issues:

   • Use an Issue Register to document issues. Include:
     • Description of the issue.
     • Owner responsible for resolving it.
     • Priority (High/Medium/Low).
     • Status (Open, In Progress, Resolved).

3. Assign Ownership:

   • Allocate someone to resolve the issue based on expertise and role.

Issue Resolution

1. Prioritize Issues:

   • Address issues based on urgency and impact on project goals.
   • Use tools like an Impact-Urgency Matrix to rank them.

2. Root Cause Analysis:

   • Identify the underlying cause of the issue using techniques like:
     • 5 Whys: Ask “why” repeatedly to trace the root cause.
     • Fishbone Diagrams (Ishikawa): Identify possible causes related to processes, resources, tools, etc.

3. Determine Corrective Actions:

   • Develop solutions to resolve the issue. Examples include:
     • Re-assigning resources.
     • Adjusting schedules to accommodate delays.

4. Monitor Resolution Progress:

   • Update the issue status in the Issue Register until resolved.

Benefits of Managing Issues

• Prevents small issues from becoming major problems.
• Ensures project timelines remain on track.
• Demonstrates accountability and effective problem-solving.

2.12 Ensure Knowledge Transfer

Knowledge transfer is the process of capturing and sharing critical information, skills, and insights to ensure the project team and stakeholders can benefit from past experiences.

Knowledge Management

1. Document Lessons Learned:

   • During or after each phase, document:
     • What went well.
     • What did not work.
     • Recommendations for future projects.
   • Tools: Use a Lessons Learned Register to capture insights.

2. Facilitate Knowledge Sharing:

   • Conduct retrospectives for iterative projects (e.g., in agile teams).
   • Hold knowledge-sharing meetings to discuss solutions to challenges.
   • Example: After a software release, the team discusses the testing challenges and documents ways to improve test efficiency in future projects.

3. Transfer Critical Knowledge:

   • Ensure that key expertise is not lost when team members transition or leave.
   • Use mentoring, shadowing, or handover sessions.

Benefits of Knowledge Transfer

• Prevents repeat mistakes by applying lessons learned.
• Ensures continuity of work when team members leave or change roles.
• Enhances team capabilities and organizational learning.

2.13 Plan and Manage Project/Phase Closure

Project or phase closure marks the formal completion of project activities and ensures that all requirements have been met.

Project Closure Activities

1. Finalize Deliverables:

   • Verify that all project deliverables meet quality standards and stakeholder requirements.
   • Obtain formal acceptance (sign-off) from stakeholders.

2. Conduct Lessons-Learned Sessions:

   • Gather the team and stakeholders to review:
     • What went well.
     • What challenges occurred.
     • What improvements can be made for future projects.

3. Release Project Resources:

   • Free up team members, equipment, or tools for other projects.
   • Communicate the end of assignments and express gratitude to the team.

4. Archive Project Documentation:

   • Save all important artifacts for future reference. Examples include:
     • Project plans, contracts, baselines, and final reports.
     • Change logs, issue registers, and lessons-learned documents.

Benefits of Project Closure

• Provides a clear sense of completion and success for stakeholders.
• Ensures the project meets all goals and objectives.
• Allows future projects to benefit from documented lessons learned.

Conclusion of the Process Domain

The Process domain forms the technical foundation of project management, guiding project managers to plan, execute, and monitor projects effectively. By understanding:

• How to prioritize work to deliver value,
• Manage risks, communications, budgets, schedules, and quality,
• And finalize projects properly,

You ensure a well-structured and successful project lifecycle.

Process (Additional Content)

1. Agile and Hybrid Project Execution

Delivering Value with Urgency (Agile Focus)

• Agile projects prioritize early value through:

  • Short iterations (Sprints)

  • MVP (Minimum Viable Product) releases

  • Backlog prioritization using tools like:

    • MoSCoW (Must, Should, Could, Won’t)

    • WSJF (Weighted Shortest Job First)

Example: A team delivers version 1.0 of a product with core features in two Sprints to test user adoption before investing in full development.

2. Communication Management in Complex Environments

2.1 Agile Communication Tools

• Agile emphasizes frequent, transparent, and direct communication:

  • Daily Stand-ups (synchronous updates)

  • Sprint Reviews (collaborative feedback)

  • Task Boards (Kanban, Scrum boards for visual tracking)

2.2 Barriers to Effective Communication

• Common barriers include:

  • Time zone differences

  • Cultural misunderstandings

  • Information overload in large distributed teams

Example: A team working across 4 time zones struggles to coordinate stand-ups, requiring asynchronous updates via Slack and recorded demos.

3. Risk and Issue Management

3.1 Agile Risk Management Practices

• Agile manages uncertainty through:

  • Incremental delivery

  • Early and continuous feedback

  • Tools like:

    • Risk Burn Down Charts

    • Spike tasks for uncertainty exploration

3.2 Positive Risk (Opportunity) Responses

• In addition to Threat responses (Avoid, Mitigate, Transfer, Accept), PMs must recognize Opportunity strategies:

  • Exploit – Guarantee the opportunity occurs

  • Enhance – Increase likelihood or impact

  • Share – Partner with others to gain benefit

  • Accept – Do nothing proactively

3.3 Issues as Realized Risks

• Issues are materialized risks; issue logs connect with risk registers for traceability.

Agile Extension: Use an Impediment Log to record and resolve real-time team blockers.

4. Stakeholder Engagement and Participation

4.1 Agile Stakeholder Roles

• Agile projects engage stakeholders frequently:

  • Product Owners prioritize the backlog

  • Customer representatives provide feedback during reviews

  • Stakeholders are available at least once per Sprint

4.2 Common Stakeholder Challenges

• Low responsiveness or unclear feedback loops can hinder decision-making.

Example: The Product Owner skips two Sprint Reviews. The PM proposes mandatory check-in sessions mid-Sprint to ensure engagement.

5. Budget and Resource Management

5.1 Agile Budgeting Techniques

• Budget evolves through Rolling Wave Planning:

  • High-level estimates early

  • Detailed planning for near-term work only

• Capacity-Based Budgeting:

  • Forecasts cost based on team size × velocity × time

5.2 Earned Value Basics (for both Agile and Predictive)

Introduce key formulas:

• CPI = EV / AC (Cost Performance Index)

• SPI = EV / PV (Schedule Performance Index)

These are foundational for scope-schedule-cost performance tracking.

6. Schedule Management Techniques

6.1 Three-Point Estimating (PERT)

Formula:
Expected Duration = (O + 4M + P) / 6
Where:

• O = Optimistic

• M = Most likely

• P = Pessimistic

6.2 Agile Scheduling Tools

• Sprint Backlogs define current work

• Burn Down Charts track progress visually

• Daily Stand-ups help with short-term replanning

7. Quality Planning and Assurance

7.1 Agile Quality Strategies

• Embed quality within the process:

  • Test-Driven Development (TDD)

  • Definition of Done (DoD) to ensure consistent quality expectations

  • Continuous Integration (CI) for early defect detection

7.2 Clarify Quality vs Grade

• Quality: Degree to which requirements are met (e.g., no defects)

• Grade: Category of the product (e.g., luxury vs economy)

Example: A low-grade product (basic phone) can have high quality (no defects).

8. Procurement in Adaptive Environments

8.1 Agile Procurement Contracts

• Favor flexibility and value-based agreements:

  • Incentive Contracts: Rewards for early delivery or high performance

  • Time & Materials with Cap: Combines flexibility with cost control

  • Agile Delivery Contracts: Payments per Sprint or milestone

8.2 Dispute Resolution Methods

• Include methods such as:

  • Arbitration

  • Mediation

  • Termination clauses (defined in contract)

9. Artifact Management and Organizational Knowledge

9.1 Document Types and Classification

• Differentiate:

  • OPA (Organizational Process Assets): Templates, lessons learned

  • EEF (Enterprise Environmental Factors): Culture, systems, regulations

9.2 Agile Documentation Principles

• Apply “Just Enough Documentation” philosophy:

  • Focus on delivering value, not exhaustive documents

  • Maintain critical artifacts like Definition of Ready (DoR), DoD, and lightweight status reports

10. Methodology Selection and Tailoring

10.1 Comparative Method Case Example

• One project, three methods:

Method	Approach
Predictive	Full scope defined upfront; sequential execution
Agile	Iterative delivery; scope evolves based on feedback
Hybrid	Predictive for hardware, Agile for software components

10.2 Advanced Methods (e.g., DA)

• Disciplined Agile (DA): Goal-driven, tool-kit-based Agile framework

• Helps teams choose their “way of working” (WoW) based on context

11. Project Closure and Knowledge Transfer

11.1 Incremental Closure in Agile

• Each Sprint ends with:

  • Potentially Shippable Increment

  • Formal or informal closure (review, retrospective, documentation)

11.2 Lessons Learned vs Knowledge Transfer

• Lessons Learned = Captured insights

• Knowledge Transfer = Delivering those insights to others for reuse

11.3 Knowledge Transfer Methods

• Communities of Practice (CoP)

• Knowledge Wikis

• Shadowing or handover sessions