CAPM Practice: Determine how to prepare and execute task management steps
Question 52 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: Restructuring existing code without changing its external behavior to improve quality, readability, and maintainability
Explanation
Refactoring improves code structure without changing behavior — renaming for clarity, extracting methods, reducing duplication. It's a continuous task management practice that prevents technical debt accumulation and keeps the codebase maintainable.
**Why not A:** Reassigning tasks among team members when progress stalls is a work-allocation or swarming decision, not refactoring. Refactoring concerns the internal structure of code, not who performs the work.
**Why not C:** Re-estimating story points after more detailed analysis is backlog refinement or re-estimation. It changes the team's understanding of size and effort, not the structure of existing code.
**Why not D:** Rebuilding the entire system from scratch on a different technology stack is a rewrite or re-platforming effort. Refactoring is incremental and deliberately preserves external behavior, whereas a rewrite replaces the system wholesale.
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