Escopo de Projeto

Prévia do material em texto

Here is a detailed summary of the video lecture on defining the project scope:
1. Introduction: 
The video was presented by an experienced project management instructor, covering the important
topic of defining and detailing the project scope.
2. Topics Covered:
a) Collecting Requirements: 
 - Techniques like workshops, role-playing (roleplanning), interviews, questionnaires, and prototypes
are used to gather detailed requirements from stakeholders and users.
 - Workshops involve gathering multiple stakeholders to brainstorm and reach a consensus on
requirements through facilitated discussions.
 - Role-playing allows experiencing the user's activities to better understand their needs.
 - Interviews use questionnaires, storyboards, and brainstorming to extract requirements from
individual stakeholders.
 - Questionnaires support other techniques by providing a structured way to collect information,
though care must be taken in their design.
 - Prototypes and mockups help visualize and validate the understanding of requirements.
b) Scope Statement:
 - The collected requirements are compiled into a detailed scope statement document.
 - It includes objectives, scope description, prototypes, assumptions, constraints, team organization,
schedule milestones, and identified risks.
 - The scope statement serves as the primary reference for project scope and managing changes.
c) Work Breakdown Structure (WBS):
 - The WBS is a hierarchical decomposition of the project's deliverables into work packages.
 - It provides a single view of the entire project scope.
 - Lower levels represent smaller components, with the lowest level being work packages.
 - The WBS aids in risk analysis, resource estimation, roles assignment, communication, and team
participation.
 - It serves as the baseline for project planning and execution.
 - An example WBS was created for a wedding project, breaking it down into phases like
preparations, ceremony, reception, and honeymoon.
3. Key Insights:
- Thoroughly detailing requirements and scope is crucial for project success.
- The scope statement and WBS provide a comprehensive view of the project scope.
- Involving the team and using visual aids like prototypes enhance scope understanding.
- The WBS hierarchically links deliverables, aids planning, and facilitates progress tracking.
4. Examples, Definitions, and Explanations:
- Detailed examples were provided for techniques like workshops, interviews, and the WBS creation
process.
- Definitions of key terms like scope statement, WBS, and work packages were clearly explained.
- Step-by-step explanations were given for creating the WBS by decomposing higher-level
deliverables.
5. Conclusion:
The lecture comprehensively covered the process of defining the project scope, including techniques
for requirements gathering, creating a scope statement, and developing a Work Breakdown Structure.
The importance of involving the team, using visual aids, and creating a detailed scope baseline was
emphasized for effective project planning and execution.