Como Fazer um Escopo de Projeto: Um Guia para Iniciantes

Concise summary

The video explains how to define and manage project scope for Waterfall (predictive) projects using PMBOK definitions and a Work Breakdown Structure (WBS / EAP) as the primary tool. Key points:

• Create the WBS collaboratively with the client and team.
• Baseline the WBS and control changes via formal change requests and sponsor/board approval.
• Use AI (e.g., ChatGPT) only as a supplement to help identify omissions — not as a substitute for team-driven scope definition.
• Keep deliverables (nouns) in the WBS separate from activities (verbs) used for scheduling.

Frameworks, processes, and playbooks

• PMBOK guidance
  • PMBOK Guide — 7th edition referenced for scope definition.
  • PMBOK 5th edition referenced for WBS definition.
• Work Breakdown Structure (WBS / EAP)
  • Hierarchical decomposition of total scope into deliverables and progressively detailed sub-deliverables.
  • WBS elements should be nouns (deliverables), not verbs (activities).
• Baseline and change control (Waterfall governance)
  • Create an initial baseline snapshot of the WBS for comparison during execution.
  • Any change requires a formal change request and sponsor/board approval; if approved, update the baseline.
• Collaborative scope-creation playbook
  • Convene client (internal or external) and development team to co-create the WBS.
  • Use iterative review: draft WBS → team validation → supplement (e.g., with AI) → team decision to accept or reject items.
• Scheduling separation
  • Keep deliverables (WBS) separate from activities; after the WBS is stable, break deliverables into tasks/verbs for scheduling.

Key tools recommended

• Miro — for collaborative WBS creation (templates available).
• ChatGPT (demonstrated with GPT-3.5) — used as a suggestion engine, not a final authoritative source.

Metrics, KPIs, and tracking

No explicit numeric KPIs were provided, but implied scope-related metrics include:

• Deliverable completion status (a parent deliverable is complete only when all child deliverables are complete).
• Baseline vs. actual comparisons (to detect scope drift).
• Number and outcome of change requests (approved vs. rejected).
• Time to approve and implement change requests.
• Team alignment/readability (qualitative KPI: any team member should understand their deliverables from the WBS).

Recommendation: fix the scope baseline for Waterfall projects to enable meaningful comparisons during execution.

Concrete example — House construction WBS

Top-level deliverable

• House construction

Level 1 deliverables

• Planning & design
• Land
• Electrical, plumbing & structure
• Finishing
• Review

Sample sub-deliverables

• Planning & design
  • Architectural project elaboration
  • Regulatory approvals
  • Materials & technologies definition
• Land
  • Clearing & demarcation
  • Excavation for foundations
  • Drainage & basement preparation
• Structure
  • Foundation & basic structure
  • Walls/partitions
  • Roof & covering

WBS usage note

• Mark a parent deliverable complete only when all child deliverables are complete. The WBS also helps visually spot missing items or misunderstandings.

AI (ChatGPT) guidance and playbook

Recommended workflow

1. First — create an initial WBS collaboratively with your team and, ideally, the client to capture context-specific knowledge.
2. Then — use ChatGPT to suggest additional deliverables or catch omissions.
3. Always review AI suggestions with the team; do not copy-paste without context adaptation.

Example prompt used in the video

Act as an experienced PMP-certified project manager. I created the WBS below for my house construction project. Suggest more deliverables that I may have forgotten…

Example AI suggestions to consider (optional)

• Landscaping & gardening
• Security installation
• Documentation & licensing
• Delivery & acceptance
• Training & manuals
• Post-delivery services

Treat AI as a collaborator that provides ideas to be validated, not an authoritative source.

Actionable recommendations / best practices

• Involve the client (internal or external) in scope definition meetings to increase engagement and reduce rework.
• Never write the scope alone — the project manager lacks full knowledge of all project parts.
• Use a visual hierarchical WBS so any team member can understand assigned deliverables if the PM is absent.
• Fix the WBS as the baseline for Waterfall projects; enforce change control via formal requests and sponsor approval.
• Keep WBS elements as nouns (deliverables); convert to verbs/activities only when building the schedule.
• Use collaborative tools (Miro templates) to co-create and iterate quickly, especially for distributed teams.
• Treat AI as a team “collaborator” that provides ideas to be validated, not an authoritative source.

Sources and presenter(s)

• Presenter: unnamed project management instructor / channel owner (not explicitly named).
• References/tools cited: PMBOK Guide (7th edition for scope; 5th edition for WBS), Miro (WBS template), ChatGPT (GPT-3.5 demo).