Agile and Hybrid Methodologies Flashcards
7 cards from real Project Management 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 and Hybrid Methodologies flashcards as text
In Scrum, who is responsible for maximizing the value of the product and managing the Product Backlog?
Answer: Product Owner
The Product Owner is solely responsible for ordering and managing the Product Backlog to maximize value.
Which Kanban practice limits the amount of work in progress to improve flow efficiency?
Answer: WIP limits
WIP (Work In Progress) limits constrain the number of items in each workflow stage, reducing bottlenecks and improving throughput.
A hybrid project approach combines predictive and agile methods. Which scenario best justifies using a hybrid approach?
Answer: Some deliverables are fixed while others need iterative development
Hybrid approaches work best when parts of the project have stable, well-defined requirements while other parts benefit from iterative discovery.
What does the term 'velocity' measure in Scrum?
Answer: The amount of work completed per sprint, used for forecasting
Velocity measures story points (or other units) completed per sprint, helping teams forecast future sprint capacity.
In the SAFe (Scaled Agile Framework), what is a Program Increment (PI)?
Answer: A timebox during which an Agile Release Train delivers incremental value
A PI is typically an 8–12 week timebox used in SAFe to align multiple agile teams on shared objectives.
Which agile principle emphasizes delivering working software frequently over comprehensive documentation?
Answer: Working software over comprehensive documentation
The Agile Manifesto explicitly values working software over comprehensive documentation as a primary measure of progress.
A team practicing Extreme Programming (XP) uses pair programming. What is the primary benefit of this practice?
Answer: Increasing code quality and knowledge sharing in real time
Pair programming improves code quality through continuous review and simultaneously transfers knowledge between team members.