PCA Property Condition Assessment Project

One of the outstanding issues is developers ignoring the signed requirements

specification document of the whole project. It means that the test cases set by following the
requirements documents would fail thus prompting the developers to go back to the code and
make the necessary changes. To curb the above issue, the project manager should distribute
the signed off requirements document to everyone (Torrens University Australia, 2023). The
impact of this change us that there would be smooth flow of the project process as developers
will adhere to all the signed requirements.

Another issue likely to affect the project is SMEs overstepping their role and going to
ask for changes on the project without following the due process of involving the change
control board. To curb this, a project plan document with policies to clearly outlines the role
of each project member (Torrens University Australia, 2023). The impact of having a detailed
project plan document is enabling organization. SMEs will know the right time to come in
and propose changes.

The third issue that is associated with the project is failing to have a shared vision. It
is important to note that each Departmental SME had its own idea of what should be included
in the final report, especially in terms of the data. To address this, it was important for all the
teams to have a clear vision of the final report and what was expected to be included in the
report (Boucher, 2023).

Dividing the project into small sprints ensures that developers are on track on their
tasks. Following the written procedures will eliminate time wastage by only making the
changes approved by the change control board. An agreed change by the change control
board is also unlikely to be rolled back later thus saving time and resources (Boucher, 2023).
Therefore, the impact of this change is promoting proper time management.

On approaching the introduction of sprints, use online tools like Kanban to monitor
daily activities. Focus on delivering the core functionality first even if it is not perfect. Then
now with the core functionality laid out, the developers can perfect and correct any bugs
encountered. On introducing project plan, have sections with change request forms where all
new changes or additional scope is well articulated. Include sectioned for all stakeholders to
approve and sign for the change to be implemented. Also, include the impact of the change to
the existing module of the system and the set test cases (Boucher, 2023).
 To ensure that stakeholders embrace the changes proposed above, I would have them
attend the daily standup meetings so as they can listen in and give their opinions and
suggestions (Mary Washburn, 2020). For instance, SMEs would have a chance to mention the
changes they would like in the system, and this would be the right time to share the change
request form with the SMEs team to fill. Once the changes request is filled, change control
stakeholders will review and approve or decline. I am confident that this is how logging every
change request would be adopted with ease.

The change model to be applied is Lewin’s Change model. The theory holds that
restraining forces have an impact on group and individual behavior, ultimately determining
whether or not change will occur (Deszca et al., 2019). This theory can be applied effectively
to ensure that these changes are successful. The first stage of Lewin’s change model is
unfreezing. During this stage, leaders work on preparing the employees and the organization
for the change (Burnes, 2020). In this case, the employees should be educated about the
change that is to take place and be equipped with the necessary knowledge and skills for the
change (Burnes, 2020).

The second stage in Lewin’s change model is change. During this stage, the project
manager and his team implement the change (Deszca et al., 2019). The project manager must
now take into account an agile and iterative strategy that incorporates employee feedback to
facilitate the change (Burnes, 2020). The third step of the model is refreezing. Notably,
during this stage, the stakeholders go from the transition phase to stabilization or acceptance.
Additionally, the project manager should regularly gather employee input and provide on-
demand staff support (Burnes, 2020).

References
Australia, T. U. (2023). PROJ6017: PCA Property Condition Assessment Project T3 2023
[case.
Boucher, M. (2023). Applying Change Management in an Agile Environment. Retrieved from
Changefolio: https://changefolio.com/articles/applying-change-management-in-an-
agile-environment#:~:text=It%20is%20also%20necessary%20to,the%20overall
%20vision%20and%20aim.
Burnes, B. (2020). The origins of Lewin’s three-step model of change. The Journal of
Applied Behavioral Science, 56(1), 32-59
Deszca, G., Ingols, C., & Cawsey, T. F. (2019). Organizational change: An action-oriented
toolkit. Sage Publications.
Mary Washburn, M. C. (2020). Change management 101: How knowing your stakeholders
can make or break your project. Cohen & Co. Retrieved from Cohen & Co:
https://www.cohencpa.com/knowledge-center/insights/december-2020/change-
management-101-how-knowing-your-stakeholders-can-make-or-break-your-project