Agile, Scrum & Kanban Methods Flashcards
7 cards from real PMI practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Agile, Scrum & Kanban Methods flashcards as text
Which Lean concept directly inspired the Kanban method's use of visual signals and pull-based workflow?
Answer: Toyota Production System's just-in-time manufacturing
Kanban was inspired by Toyota's just-in-time production system, which uses visual signals (kanban cards) to pull work only when capacity is available.
In Scrum, the event where the team presents the completed increment to stakeholders and gathers feedback is called the:
Answer: Sprint Review
The Sprint Review is a collaborative working session where the team demonstrates the Increment to stakeholders and adapts the Product Backlog based on feedback.
A project manager is transitioning a team from Waterfall to Agile. Which challenge is MOST likely to emerge first?
Answer: Resistance to frequent change and loss of predictability
Cultural resistance — especially from those accustomed to fixed plans and predictable waterfall phases — is consistently the most common and significant early challenge in Agile transitions.
Which of the following is a core practice in Extreme Programming (XP) that improves code quality by having two developers work at one workstation?
Answer: Pair programming
Pair programming is an XP practice where two programmers work together at one computer, with one writing code (driver) and the other reviewing (navigator) in real time.
In SAFe, what is the purpose of the Inspect and Adapt (I&A) event at the Program Increment level?
Answer: To demonstrate PI System Demo results and create improvement backlog items
The I&A workshop at the end of each PI includes a System Demo, quantitative measurement, and a structured problem-solving session to generate improvement stories for the next PI.
A team practicing Kanban wants to improve flow. They observe that the 'Testing' column consistently reaches its WIP limit while 'Development' is underutilized. What should they do?
Answer: Have some developers temporarily help with testing to relieve the bottleneck
When a downstream stage is the bottleneck, cross-functional collaboration — having developers assist with testing — addresses the root constraint rather than just hiding it.
What is 'technical debt' in Agile, and how does it typically accumulate?
Answer: The future cost of rework created by choosing quick, shortcuts over proper solutions
Technical debt is the implied cost of future rework resulting from choosing expedient shortcuts now rather than better approaches that would take longer initially.