SDLC & Agile Development Flashcards
7 cards from real CCP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 SDLC & Agile Development flashcards as text
What is the primary purpose of a Sprint Retrospective in Scrum?
Answer: To inspect and improve the team's process and collaboration
The Sprint Retrospective focuses on the team's internal processes, identifying what went well and what to improve in the next sprint.
In Extreme Programming (XP), what practice involves two developers working at a single workstation, with one writing code and the other reviewing in real time?
Answer: Pair Programming
Pair Programming is an XP practice where one developer writes code (driver) while the other reviews and guides (navigator), switching roles frequently.
Which phase of the SDLC involves converting the approved design into executable code?
Answer: Implementation
The Implementation (or Coding) phase is where developers translate design specifications into actual source code.
A Scrum Master notices the team frequently skips the Daily Scrum. What should the Scrum Master do first?
Answer: Facilitate a discussion to understand why the team skips it and address root causes
The Scrum Master serves the team by facilitating, not enforcing — understanding root causes helps address the real issue causing the team to skip standups.
In scaled Agile frameworks, what is the purpose of a Program Increment (PI) Planning event?
Answer: To align multiple Agile teams on a shared mission, objectives, and dependencies for an upcoming increment
PI Planning is a cadence-based event in SAFe where all Agile Release Train teams plan together to align on objectives and identify cross-team dependencies.
Which SDLC model is best described as a combination of iterative development and the systematic aspects of the Waterfall model?
Answer: Incremental Model
The Incremental Model delivers software in portions (increments), combining iterative delivery of functionality with structured Waterfall-style phases within each increment.
What is 'technical debt' in the context of Agile and SDLC?
Answer: The accumulated cost of shortcuts or suboptimal design decisions that must be addressed later
Technical debt refers to the implied future cost of rework caused by choosing quick, suboptimal solutions instead of better approaches that would take longer now.