Module 04 Flashcards
What does the The Project Management Plan do?
Defines, prepares, coordinates, and integrates subsidiary plans
- Scope Management Plan
- Risk Management Plan
- Communication Management Plan
- Cost Management Plan
- Milestone List
- Project Schedule
Guideline for how the project will be planned, executed, controlled and closed
Project Scope Management Plan
Collect Requirements
-Requirements Management Plan
Define Scope
-Project Scope Statement
Create WBS
-WBS and Scope Baseline
Verify Scope (Monitoring and Controlling) Control Scope (Monitoring and Controlling)
Requirements Management Plan
Prioritization of requirements
Configuration management
Reporting
Traceability
Whats included in Requirements Documentation
Sources of requirements Types of requirements -Functional -Non-functional -Quality requirements -Support and training requirements -Requirements based on assumptions Impact of requirement
Traceability Matrix
is a document that maps and traces user requirement with test cases
Requirement linked to the origin of the project
Requirement linked to the project objectives and deliverables
Requirement linked to the project scope and the product scope
Requirements linked of the product design, development and testing
High-level requirements linked to their details
The attributes of the requirement
What is the purpose of the Project Scope Statement
Develop a common understanding among stakeholders
Make project descriptions throughout the lifecycle
Measuring performance deviations from the scope
Project Scope Statement Components
Assumptions and Constraints
-Quality, resources, scope, time
Project Deliverables
Project Exclusions
Product Description
- Product scope description
- Product acceptance criteria
Work Breakdown Structure
(Trying to hit schedule, cost, scope) - Triple Threat
A deliverable-oriented hierarchical decomposition of the work that must be performed to accomplish the objectives and create the deliverables of the project
What does a Work Breakdown Structure do?
Subdivides project deliverables into smaller, manageable tasks called work packages
This process is called decomposition
Excellent approach for large, complex tasks
Steps for Decomposition
- Identify the deliverables and the work involved by analyzing the project
- Understand the relationships among the deliverables
- Structure and organize the first level
- Decompose the upper level into more detailed components
- Keep decomposing to lower levels until necessary and sufficient decomposition has been achieved
- Assign identification codes to the WBS components
Output of Creating WBS
Work Breakdown Structure
WBS Dictionary
Updates
Scope Baseline
How does a systems development life cycle differ from a WBS?
Fundamental units differ.
SDLCs have a “process” orientation, WBS have a “work package” orientation
What does a systems development life cycle have in common with a WBS?
Both have activities
Why is the orientation of each important?
(How does a systems development life cycle differ from a WBS?)
(What does a systems development life cycle have in common with a WBS?)
SDLC emphasizes quality and process improvement. WBS emphasizes deliverables, schedule, cost. scope,