Top 30 Project management Interview Questions and Answers
30 multiple-choice questions on Project management, drawn from 30 bites out of the 66 tagged Project management on Tezvyn. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
30 questions. Pick an answer, or open “Show the answer” to read it.
Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.
Question 1 of 30
Which statement best describes the Agile Manifesto's core identity?
Show the answer
Answer: b · It is a set of guiding values and principles for software development.
The card clearly states the Agile Manifesto is "a value system" and "a declaration of four core values," making it a philosophical guide rather than a rigid methodology. It is not a specific framework, nor does it advocate for abandoning all documentation, but rather valuing working software more.
Read the full bite: The Agile Manifesto: A Shift in Software Values
Question 2 of 30
When is conducting a stakeholder analysis most crucial for a project's success?
Show the answer
Answer: b · When the project involves diverse groups with potential conflicting interests or varying power.
The card emphasizes that stakeholder analysis is crucial for navigating the 'human landscape' and balancing 'competing demands' from parties with varying interest and influence. While identifying risks (option A) is an important project management activity, stakeholder analysis specifically focuses on understanding and managing the human element and their impact on the project.
Read the full bite: Stakeholder Analysis: Mapping Influence and Interest
Question 3 of 30
Which scenario best describes a project where the Waterfall model would be an appropriate choice?
Show the answer
Answer: b · A project with a well-defined scope and stable requirements that are unlikely to change.
The Waterfall model is explicitly recommended for projects with stable, well-understood, and fixed requirements, as its sequential nature struggles with changes. Projects with evolving requirements (like option A) are a poor fit due to the high cost of late-stage modifications.
Read the full bite: Waterfall Model: Build Software Like a Building
Question 4 of 30
Which of the following best explains the Lean Software Development principle of 'Decide as Late as Possible'?
Show the answer
Answer: c · It aims to preserve flexibility and keep options open until the last responsible moment, adapting to new information.
The card explicitly states that 'Decide as Late as Possible' is to 'preserve flexibility and keep options open until the last responsible moment.' This allows for adaptation to new information. Option B is incorrect because Lean emphasizes fast feedback and adaptation over extensive upfront analysis, which could be considered waste if it delays learning or delivery.
Read the full bite: Lean Software Development: Focus on Value, Not Waste
Question 5 of 30
For what kind of problem domain is empirical process control primarily designed?
Show the answer
Answer: a · Complex problems where requirements and technical challenges are unpredictable.
Empirical process control is explicitly designed for complex problem domains where more is unknown than known, and where requirements or technical challenges are likely to change. It is inefficient for simple, well-understood problems or situations where a detailed, predictive plan is sufficient.
Read the full bite: Empirical Process Control: Steer by Observing, Not by Plan
Question 6 of 30
During an active Scrum Sprint, what is the general approach to the scope of work?
Show the answer
Answer: d · It remains fixed to ensure the team can achieve the defined Sprint Goal.
The card explicitly states, "The scope is fixed; no changes are made that would endanger the Sprint Goal." This ensures focus and predictability for the team. While the overall product backlog is flexible, the scope within an active sprint is protected.
Question 7 of 30
What is the primary outcome a team should aim for by the end of a Daily Scrum?
Show the answer
Answer: c · A synchronized plan for the team's work over the next 24 hours.
The Daily Scrum is described as a "planning session for the next 24 hours" to "create a shared understanding and a plan for the day." It is explicitly stated that it is "not a status report for a manager" and "not for deep problem-solving" or "backlog refinement."
Question 8 of 30
In Scrum, what is the primary purpose and commitment of the Sprint Backlog?
Show the answer
Answer: d · To provide a detailed plan created by the Developers for delivering the Sprint Goal, including selected Product Backlog Items and the work needed.
The Sprint Backlog is a plan created by the Developers during Sprint Planning to achieve the Sprint Goal, detailing the selected Product Backlog Items and the work required. Option B describes the Product Backlog, which is committed to the Product Goal, not the Sprint Backlog.
Read the full bite: Explain the Product Backlog, Sprint Backlog, and Increment
Question 9 of 30
When a Scrum team is blocked by an external dependency, what is a Scrum Master's characteristic approach?
Show the answer
Answer: d · Facilitate communication, make the dependency visible, and coach the team to establish a resolution like an SLA.
The Scrum Master acts as a coach and facilitator, helping the team address impediments by making them visible and guiding the team to establish solutions, rather than solving the problem for them or managing the risk directly. The card's example shows the SM facilitating communication and coaching the team to create an SLA.
Read the full bite: The Scrum Master: A Coach, Not a Manager
Question 10 of 30
A stakeholder approaches a Developer mid-sprint with an urgent feature request. What is the most appropriate initial action?
Show the answer
Answer: b · Politely listen to understand the request, then direct the stakeholder to the Product Owner.
As a Developer, the correct first action is to listen to understand the request and then redirect the stakeholder to the Product Owner, who is solely responsible for managing the Product Backlog and prioritizing new work. Directly implementing the feature (option A) bypasses the Product Owner, endangers the Sprint Goal, and undermines Scrum principles.
Read the full bite: How do you handle an urgent mid-sprint feature request?
Question 11 of 30
What is the primary purpose of establishing a 'Definition of Ready' for backlog items?
Show the answer
Answer: a · To ensure a backlog item is sufficiently understood and actionable before being accepted into a sprint.
The Definition of Ready is an upstream quality gate to ensure work is clear and valuable before a team commits. The most common distractor confuses this with the Definition of Done, which defines the criteria for an item to be considered complete at the end of a sprint.
Read the full bite: What is the Definition of Ready for a backlog item?
Question 12 of 30
Which principle best describes the MoSCoW method's approach to project delivery?
Show the answer
Answer: d · Adjusting the scope of work to meet a predefined delivery schedule.
The MoSCoW method treats time as fixed and scope as flexible, meaning the scope is adjusted to ensure a viable product is delivered by a specific deadline. Option A is incorrect because MoSCoW is used when the timeline is fixed, not flexible.
Read the full bite: The MoSCoW Method: Prioritizing for Fixed Deadlines
Question 13 of 30
How should a project manager engage a stakeholder with high power but low interest, according to the Power/Interest grid?
Show the answer
Answer: b · Keep them satisfied with concise, high-level updates.
The card states that High Power and Low Interest stakeholders should be 'kept satisfied with concise updates.' Managing closely is for High Power, High Interest, while keeping informed is for Low Power, High Interest.
Read the full bite: Stakeholder Mapping: Prioritizing Voices by Power and Interest
Question 14 of 30
When would a Scrum team find a formal Definition of Ready (DoR) most valuable?
Show the answer
Answer: c · When sprints are frequently disrupted by unclear requirements or unexpected blockers
The card states a formal DoR is most valuable "when teams frequently find their sprints derailed by surprises" or "when work gets blocked waiting for external dependencies or clearer requirements." Option A is incorrect because the card explicitly warns against using the DoR as a "contractual weapon or a bureaucratic gate."
Read the full bite: Definition of Ready (DoR): The Bouncer for Your Sprint
Question 15 of 30
When breaking down a large epic into user stories, which approach best ensures incremental value delivery and team collaboration?
Show the answer
Answer: a · Collaboratively define a 'thin vertical slice' MVP through story mapping, then break it into small, INVEST-compliant stories with clear acceptance criteria.
The correct approach involves collaborative story mapping to define a minimal viable product (MVP) as a 'thin vertical slice' first, ensuring early value. These are then broken into small, INVEST-compliant stories with clear acceptance criteria. Option D, while mentioning user value, describes a feature list approach which lacks the iterative, collaborative breakdown and MVP focus for incremental delivery.
Read the full bite: How do you break down an epic into user stories?
Question 16 of 30
Which scenario presents the most significant challenge or risk for adopting an incremental build model?
Show the answer
Answer: c · The core architectural foundation is highly unstable, potentially leading to expensive redesigns in later stages.
The card states that incremental builds are a "poor fit if the core architecture is highly uncertain, as early increments might be built on flawed assumptions that require costly rework later." This highlights the significant risk of an unstable architectural foundation. Options B and D describe key benefits and purposes of the incremental build model, not its challenges.
Read the full bite: Incremental Build: Develop and Ship Software in Pieces
Question 17 of 30
Which statement best describes the primary purpose of a Sprint Goal?
Show the answer
Answer: a · It provides a unifying, high-level objective that guides the Developers and allows for plan adaptation.
The Sprint Goal is the 'why' for the Sprint, a single high-level objective that provides focus and flexibility, guiding the Developers. It is not merely a summary of the selected Product Backlog Items, but rather the overarching purpose that those items serve.
Read the full bite: Sprint Goal: Purpose and Influence on Sprint Planning
Question 18 of 30
During a sprint, the Developers realize a task is far more complex than estimated, jeopardizing the Sprint Goal. What is the best immediate course of action?
Show the answer
Answer: d · The Developers should consult the Product Owner to renegotiate the Sprint Backlog's scope to protect the Sprint Goal.
The correct action is to create transparency and collaborate with the Product Owner, who is responsible for backlog scope. This allows the team to adapt the plan to save the Sprint Goal. Unilaterally dropping items undermines the PO's role.
Read the full bite: A mid-sprint task jeopardizes the Sprint Goal. What now?
Question 19 of 30
The concept of technical debt is best understood as:
Show the answer
Answer: b · A deliberate tradeoff where short-term speed is gained at the expense of potential future rework.
The card defines technical debt as a "tradeoff between short-term speed and long-term quality" and an "implied cost of rework." Option A is incorrect because debt is not necessarily permanent if repaid, and it's about future rework, not just a permanent reduction in quality.
Read the full bite: Technical Debt: The Hidden Cost of Shipping Fast
Question 20 of 30
What is the main reason Planning Poker requires team members to reveal their estimates simultaneously?
Show the answer
Answer: b · To prevent any single individual's initial estimate from influencing others' independent judgment.
The card explicitly states that simultaneous reveal "prevents one person's opinion from influencing everyone else" and "forces independent thought first," directly addressing groupthink. Option D is a tempting distractor, but the process aims to discuss and understand differing estimates, not simply eliminate them, to uncover hidden complexities.
Read the full bite: Planning Poker: Avoid Groupthink in Estimates
Question 21 of 30
What is the primary intended purpose of a burndown chart in a project?
Show the answer
Answer: c · To visually track remaining work and prompt discussions about progress and blockers.
The card states that a burndown chart is a "fuel gauge" to track progress and facilitate discussions about deviations and blockers, not a performance report. Options A and D describe common misuses explicitly warned against in the card. Option A is incorrect as the chart reflects current work and changes, rather than forecasting all future scope changes.
Question 22 of 30
What is the main function of an Epic in an Agile product backlog?
Show the answer
Answer: d · To serve as a high-level placeholder for a major feature too large for a single sprint.
An Epic captures large-scale ideas and features that are too big for one sprint, acting as a container for smaller user stories. Option C is incorrect because Epics represent large features, not small tasks completable within one sprint.
Read the full bite: Epic: The Agile Placeholder for Big Ideas
Question 23 of 30
What is the primary purpose of an Agile Theme in strategic planning?
Show the answer
Answer: a · To organize and communicate how multiple epics align with a major business objective.
An Agile Theme serves as a strategic focus that groups related epics to achieve a larger business goal and communicate this alignment to stakeholders. It is not intended for detailing technical specifications or tracking individual sprint tasks, which are lower-level concerns.
Read the full bite: Agile Themes: Connecting Work to Strategy
Question 24 of 30
According to the card, what is the primary negative consequence of converting story points directly to hours in relative sizing?
Show the answer
Answer: d · It undermines the abstraction of complexity and introduces a false sense of precise time-based commitment.
The card explicitly states that converting points to hours "destroys the psychological safety and abstraction that makes relative sizing effective, turning points into just another word for hours." This defeats the purpose of relative estimation by reintroducing a misleading focus on absolute time. Option C is incorrect because velocity can still be tracked, but its meaning changes from relative effort to absolute time, which is the problem.
Read the full bite: Relative Sizing: Estimate Effort, Not Hours
Question 25 of 30
What is the most crucial characteristic for an Information Radiator to be effective?
Show the answer
Answer: a · It presents simple, current, and actionable information that is easily understood at a glance by everyone.
An Information Radiator's effectiveness hinges on its ability to display simple, current, and actionable information that is easily understood by all at a glance, driving immediate collective awareness and action. It is not primarily for detailed historical archives or restricted access, nor does it necessarily require manual daily updates.
Read the full bite: Information Radiator: Your Team's Public Billboard
Question 26 of 30
Which statement best describes how timeboxing addresses the scope of a task?
Show the answer
Answer: d · The scope is flexible, allowing for partial completion or adjustment when the fixed time limit is reached.
Timeboxing fixes the duration and lets the scope vary, meaning work stops when the time is up, and the task may be partially completed or adjusted. Option A describes the traditional project management approach, which timeboxing explicitly flips.
Read the full bite: Timeboxing: Fix the Time, Flex the Scope
Question 27 of 30
What key element transforms a simple 'To Do, In Progress, Done' board into a true Kanban system for managing workflow and improving processes?
Show the answer
Answer: b · Implementing Work In Progress (WIP) limits on 'In Progress' columns to manage flow.
The core mechanism of Kanban is managing flow by limiting Work In Progress (WIP). While detailed columns (D) are useful for visualization, it is the WIP limits that prevent overload and expose bottlenecks, thus enabling process improvement.
Read the full bite: What columns would you set up on a new Kanban board?
Question 28 of 30
For a new team adopting Kanban, which initial set of columns is most recommended to visualize workflow effectively?
Show the answer
Answer: d · To Do, In Progress, Done
The card emphasizes starting with a simple 'To Do, In Progress, Done' structure to visualize basic workflow and allow for evolution. Options B and C represent overly complex initial setups that impose a rigid process, while option B is too simplistic to effectively visualize flow.
Read the full bite: What initial columns would you set up on a Kanban board?
Question 29 of 30
In a Cumulative Flow Diagram, what does a steadily widening band for a specific workflow state primarily indicate?
Show the answer
Answer: d · Work items are entering that stage at a faster rate than they are being completed and moved to the next stage.
The card explicitly states that "If a band gets wider over time, it means more work is entering that stage than leaving it, signaling a bottleneck." This directly corresponds to option D. Option B is a common misinterpretation, as CFDs are not for tracking individual performance but for identifying systemic issues.
Read the full bite: Cumulative Flow Diagrams: Spotting Workflow Bottlenecks
Question 30 of 30
For which scenario would applying the SMART framework likely be least beneficial?
Show the answer
Answer: c · Developing a high-level, inspirational mission statement for a startup
The card states that SMART is "less useful for high-level, aspirational vision statements" because it's a tool for tactical execution, not strategic direction. The other options are all examples where SMART is explicitly recommended for setting concrete, actionable goals.
Read the full bite: SMART Goals: From Vague Hopes to Actionable Plans
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
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.