1

Reflective Journal 1 – Project Closure

Daniel Alejandro Lozano Rodriguez

Lambton College

2113- Project Closures Introduction to Agile Methodologies

Musediq Abdul

September 27, 2023

 2

Reflective Journal 1 – Project Closure

Normally, when a project is delivered by using the predictive approach, it goes through a

Lifecycle that is composed by Initiation, planning, Executing, controlling and closure. In the last

phase, the project comes to an end due to it has achieved all the objectives or deliverables or the

sponsor has decided to short-close the project, but to perform an effective closure, some

important steps must be addressed, in the class 2113- Project Closures Introduction to Agile

Methodologies we learned about these processes and applied them in real case scenario, in in the

next paragraphs the content of this class material and presentations were reflected.

What?

Talk about the process to closure the project in detail as it was taught and presented in class.

As it was mentioned before, a project is a temporary endeavor that must be closed when

the deliverables, products, or process are operative and totally completed. However, no matter

that everything has been achieved, it is still necessary some task and procedure to well-close the

project, these activities are grouped in 5 categories according to the material presented by the

group in the subject 2113. Firstly is to validate that the contract's acceptance criteria have been

satisfied. This involves doing a thorough evaluation to make sure that all requirements have been

met, including a rigorous validation of the project's scope and a rigorous quality control

procedure. Any remaining flaws or holes in the project's deliverables are then discovered

following the final scope validation, and immediate corrective actions are devised to resolve

these problems. Similar to this, following the project's final quality control validation, it is given

another thorough review to find any remaining issues with the deliverables' quality. Then,

prompt corrective action is designed to address these issues. Another crucial component is
 3

financial closure, which entails paying off all outstanding debts and rigorously adhering to all

legal procedures to guarantee not just the project's financial stability.

In addition to the Project closure process, the groups also presented, how they would

addressed certain issues in a Case study related with the implementation of a robot as fronk desk

in a office when it launched would be in two weeks, some of the issues included failures in the

robot’s behavior, complains from the company staff and inappropriate responses in some

situations, I will elaborate on this topic by giving my opinion in the next section.

So, What?

The first step is to validate that the contract's acceptance criteria have been satisfied. This

involves doing a thorough evaluation to make sure that all requirements have been met,

including a rigorous validation of the project's scope and a rigorous quality control procedure.

Any remaining flaws or holes in the project's deliverables are then discovered following the final

scope validation, and immediate corrective actions are devised to resolve these problems. Similar

to this, following the project's final quality control validation, it is given another thorough review

to find any remaining issues with the deliverables' quality. Then, prompt corrective action is

designed to address these issues. Another crucial component is financial closure, which entails

paying off all outstanding debts and rigorously adhering to all legal procedures to guarantee not

just the project's financial stability. However, when examining the case study presented by the

groups, it's clear that time constraints can present a significant challenge. My perspective is that

while the proposed remedial action plans were well-intentioned, the imminent robot launch in

two weeks posed a practical limitation. In such scenarios, prioritizing quality control to
 4

determine adherence to acceptance criteria becomes paramount. If the criteria are met, managing

stakeholder expectations might be the most prudent course. However, if discrepancies arise, a

concise action plan tailored to address the specific issue would be a more pragmatic approach,

ensuring a smoother project closure process. This adaptation emphasizes efficiency and agility in

resolving unforeseen challenges within a constrained timeframe.

Now what?

Moving ahead, it is critical to put these findings into practice in real-world circumstances.

When faced with project closures, I would prioritize quality control evaluations to ensure

adherence to acceptance standards, especially in time-sensitive scenarios. This strategy will aid

in the effective management of stakeholder expectations and the fast resolution of any

discovered differences. Furthermore, I will fight for a more simplified and adaptive action plan,

adapted to unique concerns, to ensure a speedier project completion process within tight

timescales. I hope to improve the efficacy of project closures and contribute to the overall

success of future endeavors by emphasising efficiency and agility in problem-solving. In

addition, I will look for ways to incorporate agile techniques and adaptative tactics into project

closing practices, recognizing their potential to improve results and reduce obstacles in dynamic

project contexts.

References

Emad, A. (2015). Project closing: the small process group with big impact. Retrieved from

Project Management Institute: https://www.pmi.org/learning/library/importance-of-closing-

process-group-9949
 5

Sharma, S. (2023, April 12). Practical aspects of a project closure. Retrieved from Project

Managment Institute: https://www.projectmanagement.com/blog-post/24710/practical-aspects-

of-a-project-closure#_=_