ROJECT DOCUMENTATION

LESSONS LEARNED REPORT

Project: vSphere Monitoring

Tool

Release: March 2020

Date: 03/15/2020

PRINCE2

Author: Saira Balachandran

Owner: Dr. Yasas Jayaweera

Client: Dhanujaya Praveen

Document Ref: Lesson Learned Report V1.0

Version No: V1.0

 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
1 Lessons Learned Report History

1.1 Document Location

This document is only valid on the day it was printed.
The source of the document will be found on the project's PC in location

1.2 Revision History

Date of this revision:
Date of Next revision:

Revision Previous Summary of Changes Changes marked

date revision date
03/15/202 First issue
0

1.3 Approvals
This document requires the following approvals.
Signed approval forms are filed in the Management section of the project files.

Name Signature Title Date of Issue Versio

n
Dr. Y. Jayaweera Project Executive 03/15/2020 V1.0
J.A.A Sajid Project Manager 03/15/2020 V1.0
Dhanujaya Client 03/15/2020 V1.0
Praveen

1.4 Distribution
This document has been distributed to:

Name Title Date of Issue Versio

n
Dr. Y. Jayaweera Project Executive 03/15/2020 V1.0
Dhanujaya Praveen Client 03/15/2020 V1.0

Page 2
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
2 Table of Contents

Page

1 Lessons Learned Report History 2

1.1 Document Location 2
1.2 Revision History 2
1.3 Approvals 2
1.4 Distribution 2

2 Table of Contents 3

3 Purpose 4

4 Management/Quality Process Assessment 4

5 Deviations 4

6 Method/Tool Assessment 5

7 Project Issues 5

8 Recommendations 5

9 Measurements of Effort 5

10 Statistics 6

Page 3
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
Lessons Learned Log

3 Purpose
The purpose of this document is to serve as a repository of any lessons learned during
the duration of this project that can be usefully applied to other projects in future. But
sensibly a note should be made in it of any good or bad point that arises in the use of the
management and specialist products and tools at the time of the experience. The
PRINCE2 approach was thoroughly followed for documentation and all the documents
were submitted well on time before deadlines with the project owner’s approval.

4 Management/Quality Process Assessment

The project manager made sure all the team members were present at every board
meeting since the beginning of the project
• The coordination and supportiveness among team members were consistent throughout
the project

• The business analyst made sure to study the client’s business thoroughly and get the
client requirements

• All the documents produced throughput the project were kept consistent and formatted
by the technical writer whenever needed

• The developer made sure to stick to the project schedule and to deliver required
milestones successfully on time

• The quality assurance engineer made sure to carry out the testing required on the
system well

Even though the documents were submitted by the deadline, preparing them had delays
at times due to other commitments.

5 Deviations
The project did not take any major turns. A small deviation would be the lack of a
notification system that was identified after the prototype development and was later
added to the final system.

Page 4
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
6 Method/Tool Performance
The project was managed by using the PRINCE2 project management methodology so
that the project can be clearly monitored. The project team used several online tools to
coordinate and work on the project. The project manager made sure to monitor that every
member used the suggested tools.
The software tools used by the project team are:
• Docker Hub - Deployment Managing
• GitHub – used to share code and version control.
• Trello- online project management tool
• Microsoft Office – used throughout the project, including MS Word, Excel and Project.
• draw.io – online drawing tool used to create wireframes and required diagrams.

7 Project Issues
The project team had issues with keeping up with time when delivering documents and
sprints as planned. However, with extreme effort and overtime working, the team was
able to have everything submitted on time. The communication among the team was
most reliable during board meetings and at other times virtually communicating with all
the members through online group calls was not practical at all times. The project
manager had to monitor every member that they strictly adhere to the recommended
online project sharing methods. The project manager had to keep an eye on the
developer to make sure the work was going smooth even though the sprints weren’t near.
The technical writer had to always make sure all the documents produced by every
member of the team as per their role were according to the PRINCE2 templates. Certain
documents that had any mistake had to be fixed and re-uploaded with newer versions.
The business analyst had to make sure any technical details discussed with the client
was made understandable.
Since the team had a single developer, the sprints had to be made in a convenient way
so that the developer would not have to rush through his work and also would have some
reasonable amount of time as contingency.

8 Recommendations
vSphere Monitoring Tool was developed as a feasible solution for a organizations that
manage enterprise grade virtualized environments. With further analysis of the metrics
provided, there were some considerations to be analysed during the requirement analysis
phase, which acquired the most time within the project timeline. furthermore; the team
had to make compensations when suggestions were made for the additional features
which were introduced to the system.

Therefore it would be helpful in terms of project management to invest more time to

evaluate requirements at each level of potential users to ensure minimal changes and
even faster progress.

Furthermore, strategic planning for maintenance and system recognition workshops (for
the client team) may prove useful in the long run for both the project team and the
organization when considering post delivery of the final product. (In the current scope of

Page 5
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
the project, however, we are not concerned regarding this justifying the inclusion of the
concept in the Recommendations section.)

9 Measurements of Effort
Team Members No. of hours per week
Sajid Jazook 30
Jonathan Wesidagama 35
Saira Balachandran 28
Dulanjan Wettewa 28
Dilshaath Ashroff Ali 28

Lessons Learned Table

N Manage Description Impact Analysis Improvement

o ment (Lesson Leaned)
Category
0 Commun At project start, Any of the principal The client was Made sure the
1 ication customer input on aspects of the not aware of the client knows the
manage the main features project was slightly exact metrics and latest
ment such as monitoring delayed needed further development
metrics of the clarification. progress and
system were what metrics are
required appropriate for
monitoring
purposes

0 Commun Promotional The plan and the Timeline and Assets must be
2 ication content must have definition of the roadblocks would identified earlier,
manage been engaged from scope were late in affect completion and included in
ment the outset of the the project where of the project the project. The
project there was a deliverables must
potential risk. be included in the
schedule to
ensure the
timetable for the
successful
implementation
of the project
0 Time Time allocation for Delays of Time in Development
3 manage some reports were completing certain performing test efforts were
ment insufficient milestones were cases and prioritized in
visible and acceptance order to produce

Page 6
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
expected. testing were a workable
impacted and product ahead of
delayed minorly. the time frame.
0 Quality Additional system Since a usable This showcased
4 manage features were system is released a positive impact
ment introduced knowing every sprint as by doing so
their requirement feedback was used the end product
within the clients for rectification was refined for
software purposes. the given
specification and specification.
system
maintainability.
0 Roles QA was not given Testing was Developer QA user account
5 and testing credentials delayed slightly. provided was provided for
responsi and knowledge credentials ASAP proper testing
bilities transfer sessions once informed and validation.
Manage ahead of time for about the
ment Selenium Testing. scenario.
0 Roles Clients Team Since the Team Minor features User manual was
6 and (Virtualization was aware the main were not known updated with
responsi Team ) was not function operations by the client detailed manner.
bilities aware of some was not heavily team.
Manage features of the impacted
ment system,

10 Statistics
The Product was integrated with several virtualized datacenters and was supporting and
handling all email queues seamlessly although it came across an issue decoding a
header from newer versions of the virtualization software suite apart from that all
expectations were met as maintained by the sprint releases.

Documents such as the quality plan, risk plan, test cases, test plan, risk log, issue log,
acceptance criteria have been uploaded for evidence and to get a full idea of the system
built and can be used for future changes and modifications.

The client and the project executive have been monitoring the developments by having
weekly meetings and to have a better understanding of the project status and get
feedback on the development process. Through meeting minutes, it was shown that the
product was successfully presented as the client’s requirements and all the requirements
have been met without any complication to the product or the cost.

The product met the deadline and went live without any issues. Even with the recently
emerged crisis everything went smooth as predicted with any compromise to the quality
of the project.

Page 7
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020

The developers work hard to achieve the deadlines even though the scope was bigger
than anticipated. Development process started and ended according to the sprints and
the QA had the unit tests every sprint and the tests were successfully passed without any
failure. QA’s positive feedback led the team to be on the right time limit and wasn’t
deviated from the original time framework. PM and the Technical writer had fair shares on
the documentations and were verified and cross checked before the documentation was
finalized. BA was ensuring that the communication between the client was strong and
kept the client updated with the latest updates and changes.

Statistics information’s
Strongly Slightly Normal Slightly Strongly
Disagree Disagree Agree Agree
This group project 0.0% 0.0% 0.3% 0.0% 97%
helped me
understand /
statistics are useful
for my main career
and future career.
This group project 0.0% 0.0% 0.0% 0.0% 99%
helped me to
become more
confident in project
management and
understanding of
career paths

Page 8
 Insert Project Name
Lessons Learned Report
Date: 16 March 2020
In this group 0.0% 0.0% 0.0% 0.2% 98%
project increased
my confidence in
my ability to learn
new, more
advanced future
techniques.
Enjoyed the 0.0% 0.0% 0.2% 0.1% 97%
opportunity to work
in a group project
In this project 0.0% 0.0% 0.1% 0.0% 98%
Learned about
customer
relationships.
Had a good team 0.0% 0.0% 0.1% 0.1% 98%
work with proper
Documentations
Overall, I feel that 0.0% 0.0% 0.0% 0.2% 98%
the group project
was valuable to the
course.

Page 9