Resource Planning and Prioritization Questions

Covers managing limited resources and competing priorities across teams and projects. Topics include capacity planning, resource leveling, allocation of shared resources, handling resource constraints, negotiating for required capabilities with functional leaders, and resolving resource conflicts. Candidates should be able to explain prioritization techniques such as value versus effort trade offs and prioritization scorecards including reach impact confidence effort, how to sequence work across multiple projects, and how to maintain team morale and productivity when resources are tight. Also includes communication strategies for explaining prioritization decisions to stakeholders, working with resource managers, and balancing short term delivery pressures with longer term roadmap goals.

MediumTechnical

61 practiced

A VP insists a feature be prioritized because it promises revenue, but your scorecard deprioritized it due to execution risk and high effort. How would you handle the conversation with the VP, what evidence would you present, and what compromise or alternatives would you propose if you cannot fully prioritize the feature now?

MediumTechnical

77 practiced

Recommend a capacity buffer percentage to protect the roadmap against unexpected work (bugs, outages, urgent requests). Explain what data sources you would use to calculate the buffer, how the buffer impacts throughput and predictability, and provide examples of conservative vs. aggressive buffer choices for different team types.

HardSystem Design

82 practiced

Design a company-wide resource allocation process for a 200-person engineering organization composed of ~20 product teams and several centralized platform squads. Requirements: support quarterly planning, handle shared resources, surface cross-team conflicts, provide executive visibility, and scale as the company grows. Describe roles, tools, workflows, metrics, and escalation paths.

Sample Answer

Requirements clarification:- Quarterly planning cadence, must support shared resources (platform, SRE, design), surface cross-team conflicts, give exec visibility, and scale beyond 200 engineers.

High-level design:1. Roles & governance- Resource Council (weekly): Head of Eng, VP Product, Program Managers (PMOps), leads of platform squads, 3 rotating product leads — approves cross-team allocations.- Team-level: Product Manager (owns priority), Eng Manager (owns capacity), Tech Lead (estimates), PMOps (facilitates).- RACI: PM = Request & prioritise; EM = commit capacity; Resource Council = adjudicate conflicts; Execs = final decisions on strategic trade-offs.

2. Tools- Central capacity/portfolio tool (e.g., Jira Portfolio/Advanced Roadmaps or Aha! + Confluence) with per-sprint capacity model.- Shared “Resource Pool” board for centralized squads and contractors.- Dashboards (Looker/Mode/Tableau) for exec view: utilization, forecast, blocked requests.- Slack + Incident channel for urgent escalations.

3. Workflow (quarterly + continuous)- Pre-planning (3 weeks before quarter): Teams submit requests with scope, RICE score, effort estimate (story points or FTE-weeks), dependencies, and required shared resources.- Capacity Model: PMOps aggregates per-team capacity (actual historical velocity) and marks dedicated vs. negotiable %.- Allocation Draft: Resource Council produces draft allocation; platform squads publish a “capacity calendar” with committed work and reserve slots (e.g., 20% for unplanned).- Review Cycle: Teams iterate on scope or timeline; conflicts auto-flagged by tool based on shared resource over-commit.- Finalize: Exec sign-off on high-impact conflicts; allocations frozen for quarter with monthly rebalancing window (2-way swaps allowed).- Continuous: Ad-hoc requests use SLAs (e.g., platform urgent <48h triage, non-urgent next planning window).

4. Conflict surfacing & escalation- Automatic conflict detection in portfolio tool triggers: (a) Resource Council review, (b) if unresolved >72h escalate to VP Eng & VP Product, (c) exec decision within 5 business days.- Triage ladder: PM Ops -> Resource Council -> Execs.- Use decision framework: business impact, OKR alignment, customer SLA, risk/time-to-market.

5. Metrics & KPIs- Allocation accuracy: planned vs. actual capacity utilization.- On-time delivery rate per team.- Shared resource contention rate (# of conflicts / quarter).- Time-to-resolution for escalations.- Mean time platform preemption (how often platform work is delayed).- OKR delivery % and customer-impact incidents.

6. Scaling considerations- Automate inputs (CI/CD + story telemetry) to improve estimates.- Increase PMOps bandwidth; add regional Resource Councils (matrix) as headcount grows.- Move from manual spreadsheets to portfolio management with API integrations.

Why this works:- Balances centralized arbitration and team autonomy.- Anchors decisions in data (capacity, OKRs).- Clear roles, SLAs, and escalation reduce ad-hoc fights and provide executive visibility via dashboards.

EasyTechnical

81 practiced

Explain capacity planning in a product organization: define what it is, the typical inputs and outputs, common cadences (sprint vs. quarter), and at least three concrete artifacts you'd produce (for example: resource calendar, capacity heatmap, committed-scope document). Give a short example of how you'd use capacity planning to decide between two competing feature requests that require different skill sets and timelines.

HardTechnical

80 practiced

Design a practical heuristic or lightweight algorithm to sequence three conflicting initiatives that share a dependent team. The goal is to maximize delivered value over the quarter while minimizing context switching. Explain the inputs (e.g., setup cost, run time, value), the steps of the heuristic, and provide a small example schedule.

Sample Answer

Goal: produce most value in a quarter from three initiatives sharing one dependent team while minimizing context-switching overhead. Use a lightweight score-based sequencing heuristic that balances value, throughput and switching cost.

Inputs (per initiative):- Value V (business value delivered if completed this quarter; normalized 0–100)- Run time R (weeks of focused team work to complete)- Setup cost S (one-time onboarding/context setup in weeks if switching into it)- Continuation benefit CB (fraction 0–1: how much remaining value remains if partially completed; for simplicity assume 0 or 1)- Context-switch penalty P (weeks lost whenever switching between initiatives; can be modeled as S of the new initiative or global fixed penalty)

Heuristic steps:1. Normalize: compute effective value density D = V / (R + S). This favors high value and low total cost to onboard+deliver.2. Adjust for switching: when considering a sequence, add switching penalty for each transition: total_cost = sum(R) + sum(S for every time you switch into an initiative) + (#switches × global switch_penalty).3. Sequence candidates: generate simple sequences with minimal switches (i.e., run one initiative to completion before starting next). For three items, there are 6 permutations—evaluate each by: - Total effective value delivered = sum(V of initiatives completed within quarter) - Net value per week = total_value / (total_cost clipped to quarter length)4. Choose sequence that maximizes delivered value within quarter and minimizes number of switches; break ties by higher D earlier.5. If an initiative’s R exceeds remaining quarter weeks, consider partial delivery only if Continuation Benefit justifies partial value (e.g., deliver a minimum viable slice).

Example (12-week quarter). Initiatives:- A: V=90, R=6w, S=1w- B: V=60, R=4w, S=0.5w- C: V=80, R=8w, S=1wGlobal switch_penalty = 0.5w

Compute densities:- D_A = 90 / (6+1) = 12.86- D_B = 60 / (4+0.5) = 13.33- D_C = 80 / (8+1) = 8.89

Rank by D: B, A, C.

Evaluate sequence B → A → C:- Costs: S_B(0.5)+R_B(4) =4.5; switch to A adds switch_penalty 0.5 + S_A1 =1 => +1.5; R_A6 => total after A = 12So B (4.5) + A (7.5 incl switches) = 12.0 weeks. That uses full quarter; C not started.Total value delivered = V_B + V_A = 60 + 90 = 150.

Alternate A → B → C:- A cost:1+6=7; switch to B:0.5+0.5=1 => B runs 4 => total 12; value =90+60=150 (same value). Both sequences use 2 switches; but B-first gives slightly earlier delivery of B value (finish week 4.5 vs week 7).

Alternate C-first:- C cost 9 weeks -> remaining 3 weeks; can’t finish A or B. If partial doesn't yield value, delivered value =80 (worse).

Recommendation / Practical rules for PM:- Keep number of switches minimal: prefer run-to-completion for initiatives that fit.- Use V/(R+S) to prioritize short, high-value work early to maximize throughput.- If initiatives are large, split into vertical slices (MVPs) so each slice has its own V and smaller R/S—then apply same heuristic on slices.- Recompute weekly with real progress and new estimates; freeze scope for in-progress initiative to avoid extra S.

This heuristic is fast, explainable to stakeholders, and balances value vs context-switching without heavy optimization.

Unlock Full Question Bank

Get access to hundreds of Resource Planning and Prioritization interview questions and detailed answers.

Join thousands of developers preparing for their dream job.