Project & Process Management Topics
Project management methodologies, process optimization, and operational excellence. Includes agile practices, workflow design, and efficiency.
Estimation and Scheduling
Estimating effort and building realistic schedules: estimation techniques, task sequencing, critical-path analysis, timeline development, and dependency mapping. Covers handling estimation uncertainty, schedule compression, and defending a timeline against optimism bias.
Technology Evaluation and Vendor Management
Selecting and integrating third-party technology: evaluating tools and platforms, vendor and technology assessment, procurement, and managing implementation and integration projects. Covers structured buy-versus-build and vendor-selection reasoning and running the resulting implementation.
Structured Problem Solving and Decomposition
Methodical problem solving for open-ended and ambiguous situations once the problem is defined: decomposing a goal or problem into mutually exclusive, collectively exhaustive parts (issue trees, metric trees and driver breakdowns, work breakdown into subproblems and vertical slices), forming and prioritizing hypotheses (hypothesis trees and funnels, including laying out candidate explanations for a metric drop or model degradation and the cheapest test for each branch), choosing an analytical approach, and reasoning to a recommendation. Also covers turning a vague mandate into measurable, testable subproblems with owners, breaking a large initiative into workstreams, mapping dependencies, sequencing the work, deciding the first deliverable and what to defer, structuring plans that mix research, analytics and experiments, and talking through real examples of cutting a messy problem into parts. Covers explaining and adapting structured problem-solving methods across contexts, choosing and switching methods, and coaching others to structure ambiguity. Excludes turning a vague request into a scoped problem statement, named-framework business cases, root-cause techniques for failures and metric movements (running the diagnosis itself), prioritization scoring and trade-off decisions, deciding how to act under incomplete information, market sizing and estimation, and framing machine-learning problems, which are covered elsewhere.
Sprint Planning and Backlog Management
Planning and running a sprint: backlog refinement and prioritization, capacity-based sprint planning, writing user stories with acceptance criteria, and estimating and committing to a sprint goal. Covers how backlog items flow into a sprint and how commitments are balanced against team capacity.
Agile and Scrum Fundamentals
Core agile values and the Scrum framework: the manifesto and principles, the three pillars (transparency, inspection, adaptation), Scrum roles and responsibilities, artifacts, and the theory behind empirical process control. Covers when agile fits versus a plan-driven approach and how the framework is meant to work end to end. This is foundational knowledge, not scenario execution.
Process Metrics and Operational KPIs
Measuring and managing processes with data: selecting operational KPIs, building visibility and dashboards, and driving process decisions from metrics rather than intuition. Covers defining the right measures for a process and using them to detect drift and prove improvement.
Navigating Ambiguity and Adaptive Planning
Operating effectively when information is incomplete, requirements are unclear, or the right path forward is not obvious: making a decision (or deliberately choosing to wait) with imperfect data, forming and testing assumptions, surfacing and closing data gaps, and replanning quickly as conditions, priorities, or organizational context change. Covers deciding when to act now versus gather more information first, running a lightweight experiment, spike, or prototype to reduce the biggest unknown before committing, communicating a decision and its trade-offs to stakeholders under time pressure, adjusting scope, timeline, or approach as new information emerges, and navigating unclear ownership or conflicting priorities that make the right call unclear. This is a decision-making and planning competency, tested through both direct scenarios and retrospective stories, and it applies across technical and non-technical roles at any level. Distinct from: team-facing leadership through organizational change such as reorgs or motivating a team through uncertainty (Leading Through Ambiguity and Change); a planned transformation program or formal change-management framework (Organizational Change Management); questions whose primary tested skill is a technical system-design, coding, or architecture deliverable that only mentions missing or incomplete data as color; and navigating organizational politics, competing power structures, or decision-rights and escalation-authority disputes between stakeholders, including structuring a communication artifact for an executive audience (Organizational Politics and Political Navigation; Executive Communication and Managing Up).
Project Delivery and Execution Ownership
Individually taking accountability for a project or initiative and driving it from kickoff to a shipped, committed outcome. Covers defining goals and measurable success metrics, scoping and decomposing the work, planning milestones and managing risk and dependencies, unblocking work and escalating when genuinely needed, adapting the plan under real-world constraints (deadlines, incomplete resources, ambiguous requirements), monitoring delivery health, and closing the loop on committed results. Equally covers the initiative side of ownership: acting with bias to action rather than waiting for permission, proactively identifying and fixing problems no one assigned, following through on commitments with limited oversight, and judging the right scope for unprompted initiative. Applies across technical and non-technical roles and at any level, from a first project to a cross-team program. Distinct from: narrating or selecting a single standout achievement or portfolio (Proudest Achievements and Project Portfolio); diagnosing and improving a recurring, systemic process (Process Improvement and Root Cause Analysis); the mechanics of coordinating with or negotiating between other teams whose incentives differ (Cross-Functional Collaboration); setting technical direction or influencing a strategic technical decision (Technical Leadership and Strategic Influence); the technique of managing stakeholder relationships and expectations as its own skill (Stakeholder Management and Alignment); the craft of communicating upward to executives (Executive Communication and Managing Up); and the candidate's own career trajectory or promotion path (Career Goals and Progression).
Delivery Prioritization: Scope, Speed, Quality, and Cost
Reasoning through the trade-offs among scope, speed, quality, and cost on a project that is already committed to a date, budget, or team: deciding what to cut, defer, or phase, when adding people or contractors helps or hurts, how much quality or testing risk to accept to hit a deadline, when taking on technical debt or a simpler solution is justified, and how to quantify the options and present a recommendation to executives, sales, and engineering. Covers the iron triangle, MVP and release slicing, cost of delay versus cutting scope, negotiating scope with a customer-facing team or client, limiting exposure of a risky or incomplete feature at launch, handling a mid-project capacity drop, late requirement, delayed vendor or dependency, regulatory surprise, or budget cut, and recovering a slipping project. Ranking which items to build, personal time management, estimation techniques, managing and paying down technical debt over time, and architecture-level design trade-offs are covered elsewhere.