Project management
66 bites tagged Project management: interview questions with model answers, and 60-second explainers.
Test yourself: Top 30 Project management interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.How do you consolidate scattered feedback and track document revisions?
Your ability to turn chaos into a structured approval workflow. A strong answer covers triage into one source of truth, owner assignment per revision, and tracking tools. Red flag: manual consolidation without version control or deadlines.
Throughput vs. Velocity in Agile Planning
This tests your grasp of flow vs. estimation metrics. Define throughput as a count of delivered items and velocity as a sum of estimated points. Throughput measures actual output, making it better for forecasting. Red flag: claiming velocity is more accurate.
Explain story points vs. time-based estimation.
This tests your grasp of Agile philosophy. A good answer defines points as relative effort (complexity, volume, risk), contrasts this with the pitfalls of time, and links it to predictable team velocity. A red flag is mapping points directly to hours.
What columns would you set up on a new Kanban board?
Tests your grasp of workflow visualization, not just Agile terms. A good answer starts with To Do/In Progress/Done, then adds columns like Code Review to mirror the real process, and crucially, mentions setting WIP limits to manage flow and identify…
A mid-sprint task jeopardizes the Sprint Goal. What now?
This tests your grasp of Scrum's core principles: adaptation and prioritizing the Sprint Goal. A great answer involves immediate transparency, collaborating with the Product Owner to renegotiate scope, and adapting the plan. A red flag is suggesting overtime.
What is the Definition of Ready for a backlog item?
Tests your grasp of upstream quality gates in Agile. Define DoR as a team's checklist for sprint-ready items, explain it protects dev focus and predictability, and give examples like clear acceptance criteria.
Scrum Master vs. Project Manager: How do they direct teams?
This tests your understanding of servant-leadership vs. command-and-control. A good answer contrasts their core goals (process vs. project), team interaction (coaching vs. directing), and how they handle change. Red flag: saying an SM is just an 'agile PM.'
How do you build a Monte Carlo project forecast?
Tests your ability to model uncertainty and communicate probabilistic outcomes. A good answer covers gathering cycle time data, running thousands of simulations, and presenting results as a probability distribution (e.g., "85% confidence by X date"), not a…
Burn-up vs. Burn-down Charts: What's the Difference?
Tests your understanding of project tracking metrics and their implications. A burn-down shows work remaining vs. time. A burn-up shows work completed vs. total scope, making it better for visualizing scope creep. A red flag is just describing the lines.
How do you provide a probabilistic forecast for completing 25 stories?
This tests your ability to move beyond single-date estimates to probabilistic forecasting. A good answer outlines using historical cycle times in a Monte Carlo simulation to generate a range of dates with confidence levels.
How do you use a spike to de-risk a story?
This tests your ability to use agile spikes for targeted de-risking, not just vague research. A strong answer defines the specific question the spike will answer, proposes a strict time-box, and lists concrete deliverables like a decision or a better estimate.
What initial columns would you set up on a Kanban board?
Tests your grasp of Kanban's core goal: visualizing workflow. Start with a simple board (To Do, In Progress, Done), explaining how each column represents a work state. A red flag is creating an overly complex board without justifying the need for each stage.
Sprint Goal: Purpose and Influence on Sprint Planning
Tests if you understand a Sprint is about a single objective, not just a list of tasks. Define the Sprint Goal as the 'why'—a commitment providing focus and flexibility that guides PBI selection. A red flag is defining the goal as a summary of tickets.
How do you break down an epic into user stories?
Tests translating business needs into incremental work. A great answer uses story mapping to define a vertical slice MVP, then creates sprint-ready stories with acceptance criteria. A red flag is just listing features without prioritizing user value.
How do you handle an urgent mid-sprint feature request?
This tests your understanding of Scrum roles and protecting the Sprint Goal. Acknowledge the request, redirect the stakeholder to the Product Owner who manages the backlog, and explain the trade-offs.
Explain the Product Backlog, Sprint Backlog, and Increment
Tests your understanding of Scrum's three artifacts and their commitments (Product Goal, Sprint Goal, Definition of Done). Define each, explain the flow from Product to Sprint Backlog, and how completed items form a usable Increment.
Nexus Framework: Scaling Scrum Without Breaking It
Nexus is a lightweight wrapper for 3-9 Scrum teams working on one product. It adds a coordinating Nexus Integration Team and shared events to manage dependencies and deliver a single, integrated increment each sprint.
Right-Shifting Forecasts: Why Your Deadlines Keep Moving
A forecast is like a GPS ETA in traffic; new tasks are like accidents ahead, pushing your arrival time further out. This happens when initial estimates are treated as fixed deadlines, ignoring new scope. The footgun is anchoring on the first date given.
Classes of Service: Prioritize Work Beyond 'First In, First Out'
Classes of Service are policies that prioritize work by its business impact, not just arrival time. When a bug, a deadline, and normal work compete, CoS tells you which to pull first.
Stakeholder Communication Plan: Who Gets Told What, and When
A stakeholder communication plan is a roadmap for who needs to know what, when, and how. It's used to keep executives, dependent teams, and users aligned on project progress. The biggest footgun is a one-size-fits-all approach; tailor updates to each group.
Launch Readiness Checklist: Your Launch's Single Source of Truth
A launch checklist is a flight plan, not just a to-do list, coordinating every team from engineering to sales. It ensures marketing, sales, and support are aligned for a release.
Scope Creep: When 'Just One More Thing' Derails a Project
Scope creep is the uncontrolled growth of a project's requirements after it starts. It shows up as 'small tweaks' that balloon into major features, delaying schedules and increasing costs. The footgun is trying to prevent it entirely instead of managing it.
Release Trains: Aligning Multiple Agile Teams
A Release Train is a long-lived 'team of teams' (50-125 people) building a large solution together. It aligns multiple Agile teams to a common roadmap, ensuring they deliver value in sync.
Justifying a Design System with Cost-Benefit Analysis
CBA for a design system isn't a spreadsheet; it's a formal argument weighing upfront costs (dev time) against future benefits (faster shipping). Use it to pitch a new system or justify major components.
Get Project management bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.