PAPER TOWER PROJECT

Submitted By
Fasiha Hamid F2020171017

Zara Khan F2020171013

Arslan Bin Muhammad Saeed F2020171007

Muhammad Arfan F2020171006

Syed Hassan F2020171022

Imran Yousaf

Submitted to:
Sir Bilal Ahmed Sheikh

UNIVERSITY OF MANAGEMENT & TECHNOLOGY

JOHAR TOWN, LAHORE

December, 2020
 TABLE OF CONTENTS

CHAPTER-1 INTRODUCTION...............................................................................1
CHAPTER-2 PAPER TOWER PROJECT................................................................1
2.1 Initiate.............................................................................................................1
2.2 Project Charter................................................................................................1
2.2.1 Scope........................................................................................................1
2.2.2 Resources.................................................................................................1
2.2.3 Constraint / Challenge.............................................................................1
2.3 Planning Phase................................................................................................1
2.4 Execution:.......................................................................................................2
CHAPTER-3 PROJECT INTEGRATION MANAGEMENT...................................1
3.1 PROJECT CHARTER....................................................................................1
3.2 DEVELOP PROJECT MANAGEMENT PLAN...........................................1
3.2.1 INPUT......................................................................................................1
3.2.2 Tool and Techniques................................................................................2
3.2.3 OUTPUT..................................................................................................1
3.3 DIRECT AND MANAGE PROJECT WORK...............................................1
3.3.1 INPUT......................................................................................................1
3.3.2 TOOLS AND TECHNIQUES.................................................................2
3.3.3 OUTPUTS...............................................................................................2
3.4 MANAGE PROJECT KNOWLEGE............................................................34
3.4.1 INPUT......................................................................................................4
3.4.2 TOOLS AND TECHNIQUES.................................................................5
3.4.3 OUTPUT..................................................................................................6
3.5 MONITOR AND CONTROL PROJECT WORK.........................................7
3.5.1 Monitoring...............................................................................................7
3.5.2 Control.....................................................................................................7
3.5.3 Tools and Techniques..............................................................................7
3.5.4 Documents update...................................................................................8
3.6 INTEGRATED CHANGE CONTROL..........................................................9
3.6.1 INPUT......................................................................................................9
3.6.2 Tools and Techniques:...........................................................................10
3.6.3 Outputs:..................................................................................................12
 CHAPTER-1

INTRODUCTION

As instructed by Sir Bilal Ahmed Sheikh, a paper tower activity has been performed
in the class to understand the processes and activities involved in the phases of project
management for the accomplishment of the project.

It was a great relevant practical example for better understanding of the students
about the lifecycle, process groups and knowledge area.

Project charter was given by Sir Bilal Ahmed Sheikh i.e. “Highest Paper Tower in
the Class”.

The purpose of this report is to relate the relevant activities during the project phase.
All activities are being discussed in the relevant section of the report.
 CHAPTER-2

PAPER TOWER PROJECT

2.1 Initiate
It was decided between team members that we will make a 6 level paper
tower, each level have a single module, single module consist of 4 vertical
support and 2 horizontal bracing at top of each module.

2.2 Project Charter

Highest paper tower in the class

2.2.1 Scope
Making Highest tower in the class by utilizing the available resources,
manpower and time.

2.2.2 Resources
 A4 size page (46 Nos.), 40 Nos. provided at initial stage + 6 Nos. paper
were provided during execution phase
 Glue stick
 Tape

2.2.3 Constraint / Challenge

 Paper tower should be stable in fan
 Base of the tower should not be stick on floor

2.3 Planning Phase

Total 15 minutes were provided for planning stage, several ideas were shared
and discussed between the group members during planning phase including
ParamidPyramid structure, Eiffel tower etc. Finally, 6 level paper tower were
planned as per available resources, budget, manpower and within the available
time i.e. 45 minutes. As planned we need 24 vertical supports (round shape)
 and 12 horizontal bracing (Flat). Vertical support mouldedmolded longer
direction and both edge will be connected with glue. Horizontal bracing will
be joined with vertical support with the help of tape. Each module will be
connected with tape.

2.4 Execution:
 Making Vertical Support (round shape)
 Making Horizontal Bracing (Flat)
 Assembling the vertical support with horizontal bracing to complete single
module
 Assembling the module over the other module
 CHAPTER-3

PROJECT INTEGRATION MANAGEMENT

In this chapter we are correlating the processes fall under project integration
management knowledge area.

3.1 PROJECT CHARTER

Project Charter was provided by CEO.

3.2 DEVELOP PROJECT MANAGEMENT PLAN

3.2.1 INPUT
3.2.1.1 Develop Project Charter
We studied the project charter given by CEO thoroughly to understand the
project’s key goals, objective, scope of work and role and responsibilities of
stakeholders and the project team.

3.2.1.2 Enterprise environment factors

3.2.2 Tool and Techniques
3.2.2.1 Expert Judgement
Relevant field experts are available in our team, we discussed
internally during planning phase. Which is very helpful for whole
team to understand the requirement of the project.

3.2.2.2 Data gathering

3.2.2.2.1 Brainstorming
Multiple options regarding type of tower, shapes,
execution and stability of tower have been shared and
discussed with the whole team
3.2.2.2.2 Checklist
Checklist were developed as per our planned activities
for the project deliverable and to ensure that the
execution of paper tower as required.
3.2.2.3 Interpersonal and team skills
3.2.2.3.1 Conflict Management
Conflicts between team members were discussed and
resolved.
3.2.2.3.2 Facilitation
It has been ensured that effective participation, mutual
understanding among team member, facilitation to the
team members and follow up on action and to achieve
the goal.
3.2.2.3.3 Meeting Management
Several meetings have been conducted during the
planning and execution phase to ensure that the project
should be done as per mutual understanding of the
team.
3.2.2.4 Meetings
A kick-off meeting has been conducted before execution of the
project to discuss the project approach, accomplish of project
object and establish the monitoring and controlling system during
execution.
3.2.3 OUTPUT
3.2.3.1 Project Management Plan
3.3 DIRECT AND MANAGE PROJECT WORK

3.3.1 INPUT
3.3.1.1 Project Management Plan
Above project management plan were studied in detail and prepare the
sequence of work activities
3.3.1.2 Project document
3.3.1.2.1 Change Log
No “change requests” were made of any kind, and no changes were
made.
3.3.1.2.2 Lesson learned register
Planning phase must get enough time
3.3.1.2.3 Milestone list
Milestone list were prepared as mentioned above in project
management plan. This was a useful document to know about the
time of all deliverables.
3.3.1.2.4 Project communication
Communication was among all members throughout the project
from initiating till closure.
3.3.1.2.5 Project schedule
According to the project management plan, activities, duration,
resources and start and finish time were identified.
3.3.1.2.6 Requirements traceability matrix
Traceability matrix were adopted to ensure that all deliverable
must be checked and verified at each phase to meet the
requirement.
3.3.1.2.7 Risk Register
While studying the activities of project, the stability of tower was
suspected and mentioned in risk register.
3.3.1.3 Approved change request
 No changes were made, so no approved request was generated

3.3.1.4 Enterprise environmental factors

Defined constraints, pressure of market (other groups), competitive strategies
3.3.1.5 Organizational process assets
Very first project was done by organization, no history was there of previous
projects. However, the points were noted throughout the project duration that
will be OPA of the organization.

3.3.2 TOOLS AND TECHNIQUES

3.3.2.1 Expert judgement
Organization’s Internal expert judgement was provided, by project manager
and staff as well
3.3.2.2 Project management information system
No such tools were used
3.3.2.3 Meeting
The project was one timer, so “no” additional meeting was done.
3.3.3 OUTPUTS
3.3.3.1 Deliverables
 Cylinders and braces before assembling
 Prototype of paper tower, every organization had its different design,
scheduling, implementation for this.
3.3.3.2 Work performance data
Work “project” of paper tower was completed within the scheduled date and
time assigned, resources allocated were properly engaged contained
management reserves and contingency reserves as well. All phases of project
were aligned turn by turn.

3.3.3.3 Issue log

 Design of the project especially the base(core) wasn’t smooth enough to
lift the weight of the tower
  Team members suggested to work on the base, just because of time limit,
suggestion gone overlooked

3.3.3.4 Change requests

No changes were made, neither in design nor in implementation

3.3.3.5 Project management plan updates

No changes were made; hence no updated project management plans were
required.

3.3.3.6 Project document updates

3.3.3.6.1 Activity list
Activity list were updated.
3.3.3.6.2 Assumption log
Assumption log were compared with actual log
3.3.3.6.3 Lesson learned register
Lesson learned register were updated.
3.3.3.6.4 Risk register
Monitoring of risk register were updated
3.3.3.6.5 Stakeholder register
Monitoring the deliverable of stakeholder were updated
3.3.3.6.6 Organizational process updates
Point were noted.
3.4 MANAGE PROJECT KNOWLEGE

3.4.1 INPUT
3.4.1.1 Project Management Plan
Our team had executed the project management plan and then we monitored
and controlled the project deliverables as decided in the planning phase.
3.4.1.2 Project document
3.4.1.2.1 Lesson learned register
We used the effective practices for the accomplishment of the
project.
3.4.1.2.2 Project team assignment
Available team experts (within the organization) provided the
project activities based on their prior knowledge. Activities were
assigned to the team members according to their expertise.
3.4.1.2.3 Resource breakdown structure
After assigning the tasks to relative team members, we found that
our team composition and expertise were satisfactory.
3.4.1.2.4 Stakeholder register

3.4.1.3 Deliverables
All deliverables i.e. 24 Nos. vertical cylindrical supports, 12 horizontal flat
bracing, assembling the module with the help of vertical support and
horizontal bracing were identified at planning stage and managed as per the
requirement.
3.4.1.4 Enterprise Environmental Factors
Our organizational culture was trustful and understandable that helped us in
managing knowledge. Due to the same location of resources and distribution
of facilities we were able to convey expert knowledge to each other easily.
3.4.1.5 Organizational Process Assets
OPA’s were noted during the project
 3.4.2 TOOLS AND TECHNIQUES
3.4.2.1 Expert Knowledge
Our team had executed the project management plan and then we monitored
and controlled the project deliverables as decided in the planning phase.
3.4.2.2 Knowledge management
Our team shared knowledge with each other during execution, effectively and
efficiently.
3.4.2.3 Information management
We communicated actively within the team members to achieve the set goal.
3.4.2.4 Interpersonal and Team Skills
3.4.2.4.1 Active Listening
Active listening was adopted to reduce the misunderstandings and
increased communication between group members.
3.4.2.4.2 Facilitation
Effective guidance and facilitation been provided to make the
decision and solution.
3.4.2.4.3 Leadership
Leadership was used to communicate the vision and inspire our
project team to focus on the appropriate knowledge and knowledge
objectives.
3.4.2.4.4 Networking
Informal connections and relations among project stakeholders
were established.
3.4.2.4.5 Political awareness
The project manager planned to communicate with the team
members to create better environment for the project.
 3.4.3 OUTPUT
3.4.3.1 Lesson learned register
Challenges and problems were recorded and mentioned on lesson learned
register.
3.4.3.2 Project management plan update
Project management plan was updated as per performed activities.
3.4.3.3 Organizational Process Asset
On the basis of gathered project knowledge and Organizational Process Asset
updated accordingly.
3.5 MONITOR AND CONTROL PROJECT WORK
Monitoring and control of project work is a process of continuously
evaluating the progress and quality of the project and comparing in with the
original scope as stipulated in the project charter and project management
plan.

3.5.1 Monitoring
Our paper tower project was monitored throughout the execution phase. The
progress was tracked against the stringent timeline (which was 45 minutes)
and consumption of resources (papers) was also being monitored so that in
case of any shortage, contingency reserves could be utilized.
3.5.1.1 Milestone List
Our milestone list contained the timeline schedule we had set for each
construction phase e.g. folding of papers, taping and gluing them together to
make modules, and joining of modules etc. We were monitoring the progress
continuously against our set milestones.

3.5.2 Control
3.5.2.1 Risk Register
In order to control the quality of the project, risk register was consulted time
to time, in case any preventive or corrective action was required. Risk register
contained all the anticipated risks that could affect the quality or progress of
our paper tower project. For example, one risk was the wind/fan, if wind blew
before properly stabilizing the papers, it could have a catastrophic impact on
our structure.

3.5.3 Tools and Techniques

Different Tools and Techniques were utilized in order to carefully monitor
and control the progress and quality of works.
3.5.3.1 Root Cause Analysis
When our first module failed to stand properly, we tried to analyzed the root
cause of its failure before proceeding further. The lesson that we learned was
that the columns were not wide enough and tape was not properly placed.
Identifying the root cause of instability helped us with fore coming modules.
3.5.3.2 Earned Value Analysis
This technique was used in order to forecast that whether additional resources
(contingency reserves) were required for our project or not. This was done by
comparing the planned amount of work with the completed work. The
analysis implied that we were on right track and did not require any additional
resources.

3.5.4 Documents update

We updated our lessons learned and risk registers as the result of monitoring
and control process.
3.6 INTEGRATED CHANGE CONTROL

3.6.1 INPUT
3.6.1.1 Project Management Plan:
3.6.1.1.1 Change Management Plan
First of all, we decided to make our tower in pyramid shape but
after the discussion with the team we change our plan and decide
to make modular structure based on cylinders and beams.
3.6.1.1.2 Configuration Management Plan
Paper Tower was based on the Cylinders and the beams we use
papers for making cylinders and beams after that we assemble in
such a way that two beams are connecting four cylinders in cross
way.
3.6.1.1.3 Scope Baseline
Firstly, we decided to make cylinders and beams first and then
came to assembling those but we change it to division of team one
team in assembling and the other is making cylinders and beams. It
was really helpful because project was time limited.
3.6.1.1.4 Cost Baseline
There is no impact of change on cost because there are limited
resources to manage.

3.6.1.2 Project Documents

Project documents that can be considered as inputs for this process
3.6.1.2.1 Basis of Estimates
Paper Tower project was based on 45 minutes and the limited
resources are already given by CEO so during the planning we
plan to manage these resources in given time for avoiding any
problem regarding time or resources.
 3.6.1.2.2 Risk Report
The risks during the project was the air of the fans because we are
using papers so air was the risk.

3.6.1.3 Work Performance Report:

We have folded the paper 4.5cm from both sides and the diameter for the
cylinders are 4.5cm. We make total of 24 cylinders and 12 beams and we
connect these cylinders and beams in such a way that 2 beams are connecting
4 cylinders in cross way so one story is built by using 4 cylinders and 2 beams
and we built the tower based on 6 stories.
3.6.1.4 Change Requests:
As the change requests are normally proceeds as the output so there was no
further impact of the change made in the planning phase to change the tower
from pyramid to story base because at the end tower was unable to stand even
without wind. This was due to lack of support after every story so we decided
to make our bases for every story strong for future projects.

3.6.2 Tools and Techniques:

3.6.2.1 Expert Judgement
Relevant field experts are available in our team, we discussed internally
during planning phase. Which is very helpful for whole team to understand
the requirement of the project.
3.6.2.2 Change Control Tools
3.6.2.2.1 Identifying Configuration Item
Paper Tower was based on the Cylinders and the beams we use
papers for making cylinders and beams after that we assemble in
such a way that two beams are connecting four cylinders in cross
way
 3.6.2.2.2 Record and report configuration item status
We have folded the paper 4.5cm from both sides and the diameter
for the cylinders are 4.5cm. We make total of 24 cylinders and 12
beams and we connect these cylinders and beams in such a way
that 2 beams are connecting 4 cylinders in cross way so one story
is built by using 4 cylinders and 2 beams and we built the tower
based on 6 stories.
3.6.2.2.3 Perform configuration item verification and audit
This was the responsibility of Project Manager and he was auditing
the configuration at each and every step.
3.6.2.2.4 Identify changes
Plan was to make all the cylinders and beams first then to assemble
but when the project start change was made in way of making
teams, one for making beams and cylinders and other for
configuration of tower.
3.6.2.2.5 Document changes
Proper document was made for the change during the
configuration. Document contains all the changings regarding the
configurations and schedule.
3.6.2.2.6 Track changes
All the team members are working at the same place so changes
are made and track at sudden at configuration place.

3.6.2.3 Data Analysis:

3.6.2.3.1 Alternatives analysis
As the change was made firstly in planning phase from Pyramid to
modular structure and then change of making teams was accepted
by the Project Manager.
 3.6.2.3.2 Cost-benefit analysis
The Change was really helpful at the end because 2 different teams
works aside which leads to the configuration in time.
3.6.2.4 Decision Making:
3.6.2.4.1 Voting
Voting was performed during the planning phase for changing the
structure of Tower from pyramid to modular.
3.6.2.4.2 Autocratic decision making
The change of making teams was done by the Project Manager
individually and perform Autocratic decision making.
3.6.2.5 Meetings
A kick-off meeting has been conducted before execution of the project to
discuss the project approach, accomplish of project object and establish the
monitoring and controlling system during execution.

3.6.3 Outputs:
3.6.3.1 Approved Change Requests
Changes are need to be made because of limited time so the need was to
change the schedule from individual working into the formation of teams and
this change was approved by Project Manager to implemented there.
3.6.3.2 Project Management Plan updates
After the complete configuration of the tower, it was failed to stand there the
main thing was to change the plans at the sudden time firstly in case of shape
of the tower and then team managements, these updates in plan can’t lead us
to achieve the goal. But this must be helpful for further projects to manage
these updates.
3.6.3.3 Project Document Updates
Every step during the configuration was documented but the main thing was
change log, Change log updated the document because the changes made
during the configuration was important to documented so the Project
document was updated there after every change.