Direct and Manage Project Work

 

1. Introduction to Direct and Manage Project Work

• This is the first process in execution and is an integration process.
• It represents all the execution-related processes combined.
• Example:
  • If a company is developing a new mobile app, this process ensures coding, testing, and deployment happen as per the project plan.

2. Purpose of Direct and Manage Project Work

• It involves performing the work as per the Project Management Plan (PM Plan).
• The PM Plan includes 18 components (e.g., scope baseline, schedule baseline, cost baseline).
• Example:
  • If the plan says to paint a wall white, then the execution involves actually painting the wall white.

3. Key Activities in This Process

• Managing People: Assigning tasks and ensuring team efficiency.
• Keeping Stakeholders Engaged: Regular communication with sponsors and stakeholders.
• Improving Processes: Adapting workflows to optimize efficiency.
• Requesting and Implementing Approved Changes: Handling project modifications.
• Example:
  • A company starts a website redesign project. Midway, the client requests to change the color scheme. If the change is approved, the development team implements it immediately.

4. Inputs of Direct and Manage Project Work

• Project Management Plan: Defines how execution should proceed.
• Approved Change Requests:
  • If a stakeholder requests a change, and it gets approved, it must be implemented.
  • Example:
    • The project scope initially planned for a two-floor building, but the sponsor approved an additional third floor. Execution must reflect this change.

5. Tools Used in This Process

• Project Management Software: Jira, Trello, MS Project for tracking progress.
• Communication Tools: Slack, Zoom for team collaboration.
• Issue Tracking Systems: Excel sheets, databases for logging issues.

6. Outputs of Direct and Manage Project Work

1) Deliverables (Main Output)

• The tangible output of the project.
• Example:
  • If the plan was to build a 20-story skyscraper, the deliverable is the completed 20-story skyscraper.

2) Work Performance Data

• Information about work progress, budget, and schedule adherence.
• Example:
  • Tracking how many coding tasks are completed and whether they are on time.

3) Issue Log

• A list of all problems affecting the project.
• Example:
  • Risk vs. Issue:
    • Risk: A forecasted issue (e.g., "Bad weather may delay construction").
    • Issue: A problem that already happened (e.g., "Construction was delayed due to heavy rain").

4) Change Requests

• If execution deviates from the plan, changes might be needed.
• Types of Change Requests:
  • Corrective Actions: Fix deviations.
    • Example: If over budget, request more funds.
  • Preventive Actions: Avoid future problems.
    • Example: If future budget overruns are predicted, reduce expenses.
  • Defect Repair: Fixing errors.
    • Example: If a bug is found in software, fix it before launch.

7. Summary of Direct and Manage Project Work

• It ensures the planned work gets executed.
• It integrates all execution processes.
• It produces deliverables, work performance data, issue logs, and change requests.
• It works alongside Monitoring & Controlling to ensure progress stays on track.

Key Takeaway: Execution = Deliverables

• Whatever is in the plan, this process turns it into reality.
• If the plan says to build a product, execution builds it.