CAPM Practice: Determine how to prepare and execute task management steps
Question 17 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: Automatically building, testing, and integrating code changes to maintain a working product at all times
Explanation
Continuous Integration is a technical practice where code changes are automatically built and tested when committed, maintaining a consistently working product. This enables adaptive teams to: integrate work frequently without integration risk, detect defects immediately when introduced, and always have a potentially shippable increment. CI reduces the 'integration hell' that occurs when work is merged infrequently.
**Why not A:** Continuously revising the plan based on new requirements describes adaptive planning and backlog refinement, not continuous integration. CI is a technical practice focused on building and testing code changes, not on updating the project plan.
**Why not B:** Bringing new team members into the project is onboarding, a resource management activity. The 'integration' in continuous integration refers to merging code changes into a shared codebase, not integrating people into the team.
**Why not D:** Combining predictive and adaptive approaches describes a hybrid delivery approach, not continuous integration. CI is a specific engineering practice for automatically building and testing code, not a way of blending methodologies.
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