Because software projects operate in dynamic and evolving working environments, project managers should always maintain flexibility in the Work Breakdown Structure (WBS).
Ch 09: Risk and Change Management
Examines proactive vs reactive risk management, calculating Risk Exposure (RE = P x I), creating Risk Mitigation, Monitoring, and Management (RMMM) tables, and handling change request lifecycles.
79 Questions79 MCQs0 Short Questions0 Long Questions
SEMESTER PASS
CS615 - Software Project Management Examination Practice
Timed practice exam simulation for CS615 - Software Project Management.
Showing 61 – 70 of 79 Questions
Page 7 of 8
In Work Breakdown Structure (WBS) design, ________ theory is applied when project deliverables are more important than its phases, which typically occurs when deliverables are agreed upon before the project begins.
In a Work Breakdown Structure (WBS), each ________ can be subdivided into smaller subtasks or work packages.
Over the course of a software project, comparing the planned due date against the actual date delivered provides a key metric for evaluating how well deliverable dates are ________ by the project team.
Describe a product-oriented Work Breakdown Structure (WBS) for a Bicycle manufacturing project.
List the core features and characteristics of a Work Breakdown Structure (WBS).
Explain the importance and primary reasons for using a Work Breakdown Structure (WBS) in software project management.
What does a complete WBS document contain?
If you are a project manager in an HRM software company, what method would you adopt to structure and use the WBS?
Briefly explain what a Work Breakdown Structure (WBS) is.