Which phase explicitly recognizes ongoing maintenance as part of some projects?

Which phase explicitly recognizes ongoing maintenance as part of some projects?

• A. Maintenance phase
• B. Planning phase
• C. Design phase
• D. Implementation phase

Answer: (A)

The concept being tested is whether a project lifecycle includes a distinct phase for ongoing upkeep after the initial delivery. The maintenance phase is the one that explicitly recognizes ongoing maintenance as part of some projects, because its purpose is to handle ongoing support, updates, bug fixes, and enhancements after the product is deployed. This contrasts with planning, design, and implementation, which focus on defining goals, outlining how the solution will be built, and actually creating and delivering the product. Those phases don’t inherently include long-term maintenance as a formal phase, whereas the maintenance phase does, making it the best fit for projects that foresee continued care after rollout.

The concept being tested is whether a project lifecycle includes a distinct phase for ongoing upkeep after the initial delivery. The maintenance phase is the one that explicitly recognizes ongoing maintenance as part of some projects, because its purpose is to handle ongoing support, updates, bug fixes, and enhancements after the product is deployed. This contrasts with planning, design, and implementation, which focus on defining goals, outlining how the solution will be built, and actually creating and delivering the product. Those phases don’t inherently include long-term maintenance as a formal phase, whereas the maintenance phase does, making it the best fit for projects that foresee continued care after rollout.