Program and Delivery Management Questions

Addresses planning and execution across teams to deliver business outcomes. Topics include identifying and managing dependencies, early detection and removal of blockers, stakeholder influence and negotiation, escalation strategies, scope definition and scope control, trade off decision making under constraints, prioritization, definition of clear success metrics and key performance indicators, tracking progress, communicating outcomes, and adapting plans in response to changing inputs or risks.

EasyTechnical

64 practiced

Define the difference between a project, a program, and a portfolio in the context of software delivery. Provide one example scenario from your past experience (or hypothetical) where treating work as a program rather than separate projects changed the outcome.

EasyTechnical

83 practiced

Which prioritization framework (choose one) would you use to prioritize features under tight time constraints: MoSCoW, RICE, Kano, or Weighted Shortest Job First (WSJF)? Explain why, and outline how you'd apply it across multiple teams working on the program.

Sample Answer

**Answer (pick: WSJF)**

**Why WSJF**WSJF (Weighted Shortest Job First) optimizes for maximum economic value under time pressure by prioritizing items with the highest Cost of Delay (CoD) relative to effort. As an engineering manager I prefer WSJF when time is tight because it focuses teams on the highest-impact, smallest-effort work first — reducing wasted time and delivering value faster.

**WSJF formula**

text

WSJF = Cost of Delay / Job Size

Intuition: prioritize items that lose the most value per unit of work.

**How I'd apply across multiple teams**- Align stakeholders on CoD components: user/business value, time criticality, and risk reduction. Calibrate scoring scale (1–10).- Break features into comparable job-size buckets (story points or T-shirt sizes).- Run a joint prioritization session (PI/planning) with PMs, architects, and leads to score items.- Compute WSJF and produce a ranked backlog; group into team-aligned slices.- Enforce a cadence: weekly triage for short-lived changes, PI-level review for cross-team commits.- Monitor outcomes (delivery cadence, realized value) and recalibrate scoring monthly.

**Trade-offs**WSJF requires rough but consistent scoring and senior alignment; it favors incremental, high-value small pieces over large bets — good under tight schedules.

EasyTechnical

66 practiced

Explain what a program-level "Definition of Done" (DoD) should include and how it differs from a team-level DoD. Give three examples of program-level DoD items for a distributed microservices delivery.

HardTechnical

79 practiced

You must balance two competing roadmaps: one focused on long-term platform investment and one geared to short-term revenue-driving features. Propose a decision framework and a quarterly allocation strategy that balances both objectives.

MediumTechnical

66 practiced

Propose a set of SLAs/SLIs to evaluate the performance of a program team delivering APIs (availability, latency, error rate). Include thresholds, measurement windows, and escalation triggers when thresholds are breached.

Unlock Full Question Bank

Get access to hundreds of Program and Delivery Management interview questions and detailed answers.

Join thousands of developers preparing for their dream job.