Scope Management Flashcards
Scope management process
- Plan scope management
- Collect requirements
- Define scope
- Create WBS
- Validate scope
- Control scope
Requirements engineering V-model
Baseline
Function
Verification
Validation
Requirements engineering: general structure
- customer requirements
- user requirements
- system requirements
- functional requirements
- detailed requirements
- test requirements
- approval requirements
MuSCoW
Use-Cases
Requirements Development
-Elicitation or gathering techiques
-Kano model (customer satisfaction vs customer needs)
-Quality Function Deployment
1. identify and prioritize market requirements
2. evaluate own product in comparison with competitors
3. identify technical characteristics in line with market reqirements
4.
QFD
- identify and prioritize market requirements
- evaluate own product in comparison with competitors
- identify technical characteristics in line with market requirements
- connect technical characteristics and features with market requirements
- interdependencies between technical characteristics
- sum up weighted evaluations and find priorities for technical characteristics and features.
Concept development
General process
Abstract/specific vs Chaotic/structured
Walt Disney strategy
Analytical
Sampling of products
Four samples; A, B, C, and D
CDQ0515
Negotiation
- Repeat until closure
- Combine: cost, time, quality, quantity, specification, hobby horses.
- Soft on people, hard on points (focus on interest, not position. Separate people from the problem)
Setting up a WBS
- identify deliverables and related work.
- Structure and organize into WBS
- Decompose upper level into more details
- Verify the degree of decomposition
Work package
Agreement on objective between PM and team member
Describe overview of basic PM tools
Statement of work —> Project charter —> Scope statement —-> WBS (Activity list, OBS) —> work packages, schedule (network diagram, gantt, milestone), cost plan, resource plan —->WBS dictionary
All contribute to project report
