ASEP Technical Planning and Management 2 — Questions and Answers
Question 1: What is the primary purpose of a Systems Engineering Management Plan (SEMP)?
- To document test results
- To define how systems engineering will be planned, organized, and executed throughout the project lifecycle (Correct answer)
- To list all project team members
- To specify hardware components
Correct answer: To define how systems engineering will be planned, organized, and executed throughout the project lifecycle
The SEMP defines the approach, organization, resources, processes, and schedule for executing systems engineering activities throughout the project.
The Systems Engineering Management Plan is the overarching document that defines how systems engineering will be conducted on a project. It covers the SE organizational structure, roles and responsibilities, SE processes to be applied (and their tailoring rationale), technical reviews and milestones, SE tools and methods, resource allocation, risk management approach, technical performance measurement, configuration management approach, and interfaces with other project management activities. The SEMP serves as the contract between the SE team and project management, establishing expectations for SE rigor, deliverables, and schedule integration.
Question 2: What is Earned Value Management (EVM) and how does it support technical management?
- A method for calculating employee bonuses
- An integrated cost-schedule-technical performance measurement technique that compares planned work, completed work, and actual costs (Correct answer)
- A technique for estimating system reliability
- A method for managing configuration items
Correct answer: An integrated cost-schedule-technical performance measurement technique that compares planned work, completed work, and actual costs
EVM integrates cost, schedule, and technical scope by comparing planned value, earned value, and actual cost to assess project performance and forecast completion.
Earned Value Management is a project management technique that integrates scope, schedule, and cost measurement to assess project performance. Three key metrics are compared: Planned Value (PV, the budgeted cost of work scheduled), Earned Value (EV, the budgeted cost of work actually completed), and Actual Cost (AC, the actual cost incurred). Key performance indicators include Cost Performance Index (CPI = EV/AC) and Schedule Performance Index (SPI = EV/PV), where values below 1.0 indicate overrun. EVM supports technical management by providing objective, quantitative measures of progress against the plan, enabling early detection of cost and schedule problems, and supporting estimate-at-completion forecasting.
Question 3: What is the purpose of a Technical Review in the systems engineering lifecycle?
- To approve budget increases
- To evaluate technical maturity, verify that technical products meet their requirements, and support informed decision-making at lifecycle milestones (Correct answer)
- To assign work packages to teams
- To conduct stakeholder interviews
Correct answer: To evaluate technical maturity, verify that technical products meet their requirements, and support informed decision-making at lifecycle milestones
Technical reviews evaluate the maturity and adequacy of technical products at lifecycle milestones, supporting go/no-go decisions for proceeding to the next phase.
Technical reviews are formal evaluations conducted at key lifecycle milestones to assess the maturity, completeness, and adequacy of technical products. Common reviews include System Requirements Review (SRR), System Design Review (SDR/PDR), Critical Design Review (CDR), Test Readiness Review (TRR), and System Verification Review (SVR). Each review has specific entrance criteria, review scope, evaluation criteria, and exit criteria. Reviews serve multiple purposes: they verify that technical products meet their requirements, they identify risks and issues requiring resolution, they provide management with objective data for go/no-go decisions, and they create formal records that support configuration management and accountability.
Question 4: How does a Work Breakdown Structure (WBS) support systems engineering planning?
- It replaces the system architecture
- It hierarchically decomposes project scope into manageable work packages that can be estimated, scheduled, and tracked (Correct answer)
- It defines system interfaces
- It lists all project risks
Correct answer: It hierarchically decomposes project scope into manageable work packages that can be estimated, scheduled, and tracked
A WBS decomposes the total project scope into a hierarchy of manageable work packages, providing the foundation for cost estimation, scheduling, and progress tracking.
A Work Breakdown Structure hierarchically decomposes the total project scope into progressively smaller, manageable work packages. In systems engineering, the WBS typically aligns with the system architecture—each subsystem, component, and integration activity appears as a WBS element. This alignment enables cost and schedule estimates at every system level, assignment of work packages to responsible teams, tracking of progress against the plan at each level, integration of cost/schedule data with technical performance data (through EVM), and identification of the complete scope to prevent work being overlooked. A product-oriented WBS (organized by system elements) is generally preferred over a process-oriented WBS for SE projects because it directly supports technical accountability.
Question 5: What is the role of a decision gate in technical management?
- To automatically approve all decisions
- To provide a formal checkpoint where technical maturity is assessed and authorization to proceed is granted based on defined criteria (Correct answer)
- To delegate all decisions to senior management
- To eliminate the need for trade studies
Correct answer: To provide a formal checkpoint where technical maturity is assessed and authorization to proceed is granted based on defined criteria
Decision gates are formal checkpoints where predefined criteria are evaluated to determine whether the project has sufficient technical maturity to proceed to the next phase.
Decision gates (also called phase gates or milestone reviews) are formal checkpoints in the project lifecycle where technical maturity is assessed against predefined criteria to determine whether the project should proceed, iterate, or stop. Each gate has entrance criteria (what must be completed before the review), evaluation criteria (what is assessed during the review), and exit criteria (what conditions must be met to pass). Gate decisions include proceed to next phase, proceed with conditions (specific actions required), iterate (repeat current phase activities), or stop (redirect or cancel). Decision gates prevent premature advancement to the next phase when technical risks have not been adequately resolved, protecting against costly downstream rework.
Question 6: Why is resource planning critical in systems engineering management?
- It only matters for large projects
- Inadequate resource planning leads to skill gaps, schedule delays, and quality degradation as workload exceeds available capacity (Correct answer)
- It is handled automatically by project management software
- It only applies to hardware procurement
Correct answer: Inadequate resource planning leads to skill gaps, schedule delays, and quality degradation as workload exceeds available capacity
Resource planning ensures that the right skills, tools, and facilities are available when needed, preventing bottlenecks and quality degradation from overloaded resources.
Resource planning in systems engineering management ensures that adequate human resources (with the right skills and experience), tools (modeling, analysis, testing), facilities (labs, test ranges), and computing infrastructure are available when needed throughout the lifecycle. Inadequate resource planning leads to multiple problems: skill gaps force unqualified staff into critical roles, schedule delays occur when bottleneck resources are oversubscribed, quality degrades when engineers are spread too thin across too many tasks, and critical activities are deferred or abbreviated. Effective resource planning involves workload estimation based on the SEMP and WBS, identification of critical skill needs, resource leveling to prevent overallocation, and contingency planning for resource risks.
ASEP Technical Planning and Management 2
What is the primary purpose of a Systems Engineering Management Plan (SEMP)?