CAPM Practice: Determine how to prepare and execute task management steps
Question 59 of 60 in Determine how to prepare and execute task management steps
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: A timeboxed investigation task to reduce uncertainty about a technical approach before committing to implementation — the result is knowledge, not a product feature
Explanation
Technical spikes are bounded research tasks: 'Can we integrate with the legacy API in 3 days?' The team runs the spike, gains the answer, and uses the result to make informed decisions about implementation approach — reducing the risk of embarking on a wrong technical path.
**Why not A:** A production incident is an unplanned failure handled through incident management. A spike is a deliberately planned, timeboxed task the team chooses to run.
**Why not B:** A spike does not describe complexity growing within an iteration. It is a specific task the team adds to reduce uncertainty.
**Why not D:** A spike is not a measurement tool for technical debt. Its output is knowledge that informs an implementation decision, not a metric tracked per iteration.
Key Concept
This question covers Determine how to prepare and execute task management steps under Determine how to prepare and execute task management steps (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free