1. What is a post-implementation assessment (PIA)?
A post-implementation assessment is a formal evaluation conducted after an
IT project or system has been deployed to determine whether it met its
objectives, delivered expected benefits, and to identify lessons learned for
future projects.
2. What is the primary purpose of a post-implementation assessment in IT
project management?
The primary purpose is to evaluate project outcomes against original
objectives, measure the success or failure of the implementation, identify
areas for improvement, capture lessons learned, and ensure the system is
delivering the intended business value.
3. When should a post-implementation assessment typically be
conducted?
A PIA is typically conducted 3-6 months after go-live, allowing enough time for
the system to stabilize, users to adapt, and meaningful performance data to
accumulate. Some organizations conduct multiple reviews at different
intervals.
4. Who are the key stakeholders involved in a post-implementation
assessment?
Key stakeholders include project sponsors, end users, IT staff, business unit
managers, the project team, executive leadership, vendors, and any other
parties who were affected by or involved in the implementation.
5. What are the main components of a post-implementation assessment
report?
, Main components include an executive summary, project overview, evaluation
of objectives, performance metrics analysis, financial analysis (budget vs.
actual), risk assessment review, lessons learned, user satisfaction results,
technical performance, and recommendations.
6. What is the difference between a post-implementation review and a post-
implementation assessment?
These terms are often used interchangeably. However, a review may be a
narrower evaluation focused on specific aspects, while an assessment tends
to be a more comprehensive evaluation covering all dimensions of the project
including strategic alignment, financial performance, and user adoption.
7. How does a post-implementation assessment support organizational
learning?
It documents what worked and what did not, creating a knowledge base that
future project teams can reference. It helps organizations avoid repeating
mistakes and replicate successes, improving the overall maturity of project
management practices.
8. What role does the project charter play in a post-implementation
assessment?
The project charter provides the original objectives, scope, budget, timeline,
and success criteria against which the actual outcomes are measured. It
serves as the baseline for evaluating whether the project delivered its
intended results.
9. What is the significance of capturing lessons learned in a post-
implementation assessment?
Lessons learned document insights about what succeeded, what failed, and
what could be improved. They are stored in organizational knowledge
repositories and used to guide future projects, ultimately improving project
success rates.
10. How does a post-implementation assessment differ from project
closure?
Project closure formally ends the project and transfers ownership to
operations. A post-implementation assessment occurs after closure and
evaluates whether the deployed solution is achieving its intended outcomes in
the production environment.
11. What is the balanced scorecard approach in a post-implementation
assessment?
, The balanced scorecard approach evaluates the project from four
perspectives: financial (cost/ROI), customer (user satisfaction), internal
processes (efficiency improvements), and learning and growth (knowledge
gained). This ensures a holistic assessment.
12. Why is user adoption a critical metric in a post-implementation
assessment?
User adoption determines whether the system is actually being used as
intended. Low adoption can indicate poor training, resistance to change,
usability issues, or inadequate change management, all of which reduce the
system's ROI.
13. What is meant by 'benefits realization' in the context of a post-
implementation assessment?
Benefits realization refers to the process of ensuring that the anticipated
benefits identified during project planning have actually been achieved after
implementation. The PIA measures whether promised benefits (cost savings,
efficiency gains, etc.) have materialized.
14. What is a benefits realization plan?
A benefits realization plan is a document that identifies the expected benefits
of a project, assigns ownership for each benefit, defines how benefits will be
measured, and establishes a timeline for when benefits should be realized
post-implementation.
15. What is the role of KPIs in a post-implementation assessment?
Key Performance Indicators (KPIs) are measurable values that demonstrate
how effectively the project is achieving key objectives. In a PIA, KPIs
established before implementation are tracked to determine actual vs.
expected performance.
16. How should an organization prioritize issues discovered during a post-
implementation assessment?
Issues should be prioritized based on their impact on business operations, risk
to data integrity or security, cost to remediate, frequency of occurrence, and
number of users affected. High-impact, high-frequency issues should be
addressed first.
17. What is the purpose of a gap analysis in a post-implementation
assessment?
, A gap analysis identifies the differences between the expected state (as
defined in project requirements) and the actual state after implementation. It
highlights areas where the system or processes fall short of intended goals.
18. How do you measure the success of an IT implementation?
Success is measured by comparing actual outcomes to predefined success
criteria across multiple dimensions: on-time delivery, on-budget delivery,
achievement of functional requirements, user satisfaction, system
performance, and business benefit realization.
19. What is the importance of objectivity in a post-implementation
assessment?
Objectivity ensures the assessment is credible and actionable. Without
objectivity, assessors may unconsciously overlook failures or attribute
problems to external factors. An objective assessment provides accurate data
for organizational learning and accountability.
20. Who should conduct the post-implementation assessment?
Ideally, the assessment should be conducted by an independent party
(internal audit, PMO, or third-party consultant) to avoid bias. Some
organizations have the project team conduct it with oversight from a steering
committee to maintain objectivity.
Section 2: Project Objectives & Requirements (Q21–50)
21. What are functional requirements and how are they evaluated in a PIA?
Functional requirements define what a system must do. In a PIA, each
functional requirement is evaluated to determine whether it was implemented
correctly, is working as expected, and is being used by end users.
22. What are non-functional requirements and why are they important in a
post-implementation assessment?
Non-functional requirements define how a system performs (e.g., speed,
security, scalability, reliability). They are important in a PIA because they
affect user experience and system viability even when all functional
requirements are met.
23. What is scope creep and how should it be addressed in a post-
implementation assessment?
Scope creep is the uncontrolled expansion of project scope. In a PIA, it should
be documented as a contributing factor to budget overruns or delays, and
A post-implementation assessment is a formal evaluation conducted after an
IT project or system has been deployed to determine whether it met its
objectives, delivered expected benefits, and to identify lessons learned for
future projects.
2. What is the primary purpose of a post-implementation assessment in IT
project management?
The primary purpose is to evaluate project outcomes against original
objectives, measure the success or failure of the implementation, identify
areas for improvement, capture lessons learned, and ensure the system is
delivering the intended business value.
3. When should a post-implementation assessment typically be
conducted?
A PIA is typically conducted 3-6 months after go-live, allowing enough time for
the system to stabilize, users to adapt, and meaningful performance data to
accumulate. Some organizations conduct multiple reviews at different
intervals.
4. Who are the key stakeholders involved in a post-implementation
assessment?
Key stakeholders include project sponsors, end users, IT staff, business unit
managers, the project team, executive leadership, vendors, and any other
parties who were affected by or involved in the implementation.
5. What are the main components of a post-implementation assessment
report?
, Main components include an executive summary, project overview, evaluation
of objectives, performance metrics analysis, financial analysis (budget vs.
actual), risk assessment review, lessons learned, user satisfaction results,
technical performance, and recommendations.
6. What is the difference between a post-implementation review and a post-
implementation assessment?
These terms are often used interchangeably. However, a review may be a
narrower evaluation focused on specific aspects, while an assessment tends
to be a more comprehensive evaluation covering all dimensions of the project
including strategic alignment, financial performance, and user adoption.
7. How does a post-implementation assessment support organizational
learning?
It documents what worked and what did not, creating a knowledge base that
future project teams can reference. It helps organizations avoid repeating
mistakes and replicate successes, improving the overall maturity of project
management practices.
8. What role does the project charter play in a post-implementation
assessment?
The project charter provides the original objectives, scope, budget, timeline,
and success criteria against which the actual outcomes are measured. It
serves as the baseline for evaluating whether the project delivered its
intended results.
9. What is the significance of capturing lessons learned in a post-
implementation assessment?
Lessons learned document insights about what succeeded, what failed, and
what could be improved. They are stored in organizational knowledge
repositories and used to guide future projects, ultimately improving project
success rates.
10. How does a post-implementation assessment differ from project
closure?
Project closure formally ends the project and transfers ownership to
operations. A post-implementation assessment occurs after closure and
evaluates whether the deployed solution is achieving its intended outcomes in
the production environment.
11. What is the balanced scorecard approach in a post-implementation
assessment?
, The balanced scorecard approach evaluates the project from four
perspectives: financial (cost/ROI), customer (user satisfaction), internal
processes (efficiency improvements), and learning and growth (knowledge
gained). This ensures a holistic assessment.
12. Why is user adoption a critical metric in a post-implementation
assessment?
User adoption determines whether the system is actually being used as
intended. Low adoption can indicate poor training, resistance to change,
usability issues, or inadequate change management, all of which reduce the
system's ROI.
13. What is meant by 'benefits realization' in the context of a post-
implementation assessment?
Benefits realization refers to the process of ensuring that the anticipated
benefits identified during project planning have actually been achieved after
implementation. The PIA measures whether promised benefits (cost savings,
efficiency gains, etc.) have materialized.
14. What is a benefits realization plan?
A benefits realization plan is a document that identifies the expected benefits
of a project, assigns ownership for each benefit, defines how benefits will be
measured, and establishes a timeline for when benefits should be realized
post-implementation.
15. What is the role of KPIs in a post-implementation assessment?
Key Performance Indicators (KPIs) are measurable values that demonstrate
how effectively the project is achieving key objectives. In a PIA, KPIs
established before implementation are tracked to determine actual vs.
expected performance.
16. How should an organization prioritize issues discovered during a post-
implementation assessment?
Issues should be prioritized based on their impact on business operations, risk
to data integrity or security, cost to remediate, frequency of occurrence, and
number of users affected. High-impact, high-frequency issues should be
addressed first.
17. What is the purpose of a gap analysis in a post-implementation
assessment?
, A gap analysis identifies the differences between the expected state (as
defined in project requirements) and the actual state after implementation. It
highlights areas where the system or processes fall short of intended goals.
18. How do you measure the success of an IT implementation?
Success is measured by comparing actual outcomes to predefined success
criteria across multiple dimensions: on-time delivery, on-budget delivery,
achievement of functional requirements, user satisfaction, system
performance, and business benefit realization.
19. What is the importance of objectivity in a post-implementation
assessment?
Objectivity ensures the assessment is credible and actionable. Without
objectivity, assessors may unconsciously overlook failures or attribute
problems to external factors. An objective assessment provides accurate data
for organizational learning and accountability.
20. Who should conduct the post-implementation assessment?
Ideally, the assessment should be conducted by an independent party
(internal audit, PMO, or third-party consultant) to avoid bias. Some
organizations have the project team conduct it with oversight from a steering
committee to maintain objectivity.
Section 2: Project Objectives & Requirements (Q21–50)
21. What are functional requirements and how are they evaluated in a PIA?
Functional requirements define what a system must do. In a PIA, each
functional requirement is evaluated to determine whether it was implemented
correctly, is working as expected, and is being used by end users.
22. What are non-functional requirements and why are they important in a
post-implementation assessment?
Non-functional requirements define how a system performs (e.g., speed,
security, scalability, reliability). They are important in a PIA because they
affect user experience and system viability even when all functional
requirements are met.
23. What is scope creep and how should it be addressed in a post-
implementation assessment?
Scope creep is the uncontrolled expansion of project scope. In a PIA, it should
be documented as a contributing factor to budget overruns or delays, and
