Difficulty: Easy
Correct Answer: review
Explanation:
Introduction / Context:
Project success is not fully known until the system runs in production. A structured post-implementation evaluation checks whether objectives were met, users are satisfied, controls are effective, and value is realized. This feedback informs optimization and future projects.
Given Data / Assumptions:
Concept / Approach:
A post-implementation review (sometimes called PIR) evaluates benefits realization, cost variances, incident patterns, and user adoption. Maintenance is the ongoing process of changes and fixes; planning and batch processing are unrelated to the appraisal activity itself.
Step-by-Step Solution:
Verification / Alternative check:
Governance frameworks (e.g., PRINCE2, PMBOK) require post-project reviews to capture lessons learned and benefits realization.
Why Other Options Are Wrong:
Maintenance: Execution of updates, not evaluation.
Planning/Batch processing: Different lifecycle activities.
None: Incorrect because “review” is the standard term.
Common Pitfalls:
Skipping the review leads to repeated mistakes and unverified benefits in subsequent initiatives.
Final Answer:
review
Discussion & Comments