MIS 578 Chapter 7: Defining Scope & constructing Work Breakdown Structures (WBS) Flashcards
Collect Requirements
o “The process of defining, documenting, and managing stakeholder needs and requirements to meet project objectives.”
o The first step in collecting requirements is to ensure that the project team is absolutely clear on the project objectives.
o The second step is to gather input from the various project stakeholders.
How to define scope – six-step process
- Clarify objectives
- List potential deliverables
- Gather stakeholder input
- Clearly state the scope
- Establish project boundaries
- Create baseline scope statement
Project Scope Statement – the output from scope definition
o Project objectives o Project scope description o Project requirements o Boundaries o Deliverables o Constraints and Assumptions
What is a WBS?
Tool to progressively divide project into smaller pieces until the team feels every deliverable is identified. While the WBS identifies deliverables, teams may define activities and milestones at the same time for use in the project schedule.
Why use a WBS?
To ensure all parts of the project are considered and as a basis for other planning – such at schedule, budget, resources, risk, and quality
WBS Formats
Each has advantages and disadvantages.
• Indented outline
Useful when typing WBS into scheduling software.
• Org chart
Org chart is a familiar form – easy to understand and somewhat flexible.
• Free form
Totally flexible – especially useful for project with structure initially unclear.
Work packages
They are the lowest level of WBS – smallest deliverables identified. Work packages for the basis for continued planning and much of the project control
How to construct a WBS
Include appropriate subject matter experts (SMEs).
• Identify major deliverables
-Use a top-down approach identifying deliverables from scope statement. Rolling wave planning can be used to identify early deliverables in detail and later ones at a high level. Organize in systematic manner such as by phase or design component.
• Divide into smaller deliverables
-Include both interim and final deliverables – use Post-it ® Notes for flexibility.
• Continue until deliverables are the right size – small enough for control, not so small as to micro-manage.
• Review
– ensure completeness.
– make sure each level is the summary of next lower level.
– ensure each item has unique name and number.
Types of project data
• Task data
-WBS elements as summary rows with black bar and bold text.Critical path tasks in contrasting color. Noncritical tasks in muted grey.
• Resource data
-Resources are often persons or machines. Available time is noted.
• Assignment data
-Assignment units, work, cost data, and task duration are calculated or set when a resource is assigned to a task.
Initialize the Project – five steps
- Set the project start date (Project menu, Project information …)
- Enter identifying information (File menu, Properties, Summary tab)
- Define your organization’s holidays (Tools menu, Change working time)
- Automatically generate a project summary row (Tools menu, Options, View tab)
- Hide highlighting (View menu, Show change highlighting)
Set Up the WBS – also five steps
- Understand WBS definitions and displays.
- Enter summaries, milestones, and tasks.
- Create the outline for your WBS.
- Insert row number column.
- Hide (or show) desired amount of detail.
What is the first step in developing the project scope management plan?
Developing a project scope statement.
What areas of the project can scope creep effect?
Time, cost, and resources.
A ________________________ is used to formally document changes made to the project.
Change control system
List the two types of deliverables.
Primary and secondary.