Lessons Learned Report 2022

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjkl
zxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmrtyuiopasdfghjklzxcv
Lessons Learned
University Mobile Applications
8/26/2019

Lessons Learned
Table of Contents
INTRODUCTION..........................................................................................................................................2
LESSONS LEARNED APPROACH......................................................................................................................2
LESSONS LEARNED FROM THIS PROJECT..........................................................................................................2
LESSONS LEARNED KNOWLEDGE BASE / DATABASE..........................................................................................3
LESSONS LEARNED APPLIED FROM PREVIOUS PROJECTS.....................................................................................3
PROCESS IMPROVEMENT RECOMMENDATIONS.................................................................................................4
References.............................................................................................................................................5
1

Lessons Learned
INTRODUCTION
The lessons learned during the project of University mobile applications have been
documented and the purpose of the activity is to keep a track of the lessons acquired. Also,
the activity will make sure that the strengths, weaknesses, and the areas of improvement are
identified so that the future results are better.
LESSONS LEARNED APPROACH
The lessons learned approach was to comprise of the list of the lessons from the beginning of
every phase and the documentation of the same at the end of the phase. The discussion with
the fellow team members along with one-on-one discussion with the Project Manager were
also done to verify and validate the same.
LESSONS LEARNED FROM THIS PROJECT
Category Issue Name Problem/Success Impact Recommendation
Communication
Management
Non-
availability of
the members
The communication
plan was defined in
the beginning with
the sharing of the
discussion and
meeting schedule in
advance to ensure
that availability of the
members (Tavan &
Hosseini, 2016).
The presence rate in
the meetings and
discussions was good
and the stakeholder
communications
could also be
facilitated using the
same approach.
The communication
processes shall be
streamlined and
there shall be use of
automated
communication
handling tools done
so that the
associated risks are
avoided.
Performance
Management
Tracking of
the resource
performance
There were gaps in
the schedule and
budget of the project
but the timely
detection could make
sure that the
associated risks were
avoided.
The completion of the
project activities
could be done on
time and within the
budget that was
defined.
The use of adequate
estimation and
tracking techniques
shall be done.
Resource Lack of The resources showed The deteriorated The Project
2

Lessons Learned
Management motivation deteriorated
productivity and
efficiency levels at
various instances
during the project.
levels had poor
impacts on the other
project areas, such as
project schedule and
budget (Al-Freidi,
2015).
Manager shall
conduct the one-on-
one discussions with
the resources to
determine the
issues.
Stakeholder
Management
Stakeholder
Interest levels
The stakeholders
showed deteriorated
interest levels at
various instances
during the project.
The deteriorated
levels had poor
impacts on the other
project areas, such as
project schedule and
budget.
The Project
Manager shall
conduct the one-on-
one discussions with
the stakeholders to
determine the
issues.
Risk Handling Schedule and
Budget Risks
The schedule and
budget risks emerged
during the early
phases of
implementation but
could be controlled
well in time (Fanning,
2014).
The project could be
completed on time
and within the budget
defined.
The tracking of the
schedule and budget
levels shall be done
regularly with risk
management in
place.
LESSONS LEARNED KNOWLEDGE BASE / DATABASE
The use of the previous projects completed by the project team especially in the domain of
education and web development were used to acquire the lessons. The use of numerous web
sources was also done.
LESSONS LEARNED APPLIED FROM PREVIOUS PROJECTS
The previous projects showed the issues of schedule and budget overrun in such projects and
the lessons obtained from those projects were utilized in this one to keep the schedule and
budget on track (Hairul Nizam Md Nasir, Sahibuddin, Ahmad & Sanim Mohd Fauzi, 2015).
3

Lessons Learned
PROCESS IMPROVEMENT RECOMMENDATIONS
The improvements could be made in the project as the various project areas had a few issues
during the project timeline.
Frequent tracking of the project areas should have been done to improve on the processes.
4

Lessons Learned
References
Al-Freidi, S. (2015). A Unified Project Management Methodology (UPMM) based on
PMBOK and PRINCE2 protocols: foundations, principles, structures and benefits of
the integrated approach. International Journal Of Business Policy And Strategy
Management, 2(1), 27-38. doi: 10.21742/ijbpsm.2015.2.03
Fanning, F. (2014). Adapting PMBoK Guidance to Public Sector Projects. Organization,
Technology And Management In Construction: An International Journal, 6(3). doi:
10.5592/otmcj.2014.3.3
Hairul Nizam Md Nasir, M., Sahibuddin, S., Ahmad, R., & Sanim Mohd Fauzi, S. (2015).
How the PMBOK Addresses Critical Success Factors for Software Projects: A Multi-
round Delphi Study. Journal Of Software, 10(11), 1283-1300. doi:
10.17706//jsw.10.11.1283-1300
Tavan, F., & Hosseini, M. (2016). Comparison and analysis of PMBOK 2013 and ISO
21500. Journal Of Project Management, (10), 27-34. doi: 10.5267/j.jpm.2017.1.002
5