This presentation was created as an assignment for the subject "Projection Techniques." It defines what the Wasa Project was, how it was implemented and what lead to its failure eventually.

1. TOPIC: WASA PROJRCT
Presented to: Ma’aM Rakshanda
Presented by: Syed Ali Roshan
MA. EPM III Evening

2. Outline
 Concept of the project
 Reasons for the collapse
 Lessons Learnt
 Best Lesson

3. Concept of the project:
 The Vasa was a Swedish war ship built between
1625 and 1628.
 After so many defeats in the early 1620s, it was
the requirement to represent the revival of the
Swedish navy and to show the power of the
country. In January 1625, the Swedish king signed
a contract with the Dutch master shipwright
Henrik Hybertsson

4. The king wanted the ship, Wasa, built as
large as possible and richly decorated as a
symbol of the king's ambitions for Sweden
and himself.
 Upon completion the ship would be one of
the most powerfully armed vessels in the
world.
Unfortunately, as grand as Wasa was, it
was dangerously unstable too and it
collapsed after sailing only around 1,300
m.

5. Reasons for the collapse :
 The king kept demanding changes in the designs,
increasing the size of the ship and adding more
weights by adding more cannons and decorations to
the ship. Even though Henrik knew this was dangerous
and that this way the project would not meet the
deadline, he was under pressure because he could not
deny the king and so he kept agreeing to the changes.
 Near the completion of the project Henrik died of a
heart attack and his assistant, Hein, took over the
project

6. lessons Learnt about project Management and
Project Control
 Don’t change specifications halfway through the project
 Changes are good, but not in the middle of any project
 Discuss problems with whole team
 When things are getting worse then take a step forward
and take immediate action to make your project or plan
functional.
 Test a lot and practice a lot.

7. Best lesson from this can be learned:
 Constant changes in project’s scope, pressure of tight
deadlines, lack of technical specification and innovation
without proper tests can lead any project to failure
 If the project managers are being pressured by a higher
authority, they should not stray too far away from initial
designs and scope and if they have safety concerns or if
they believe what the clients are asking is simply not
possible in due deadline, they should speak up before the
project because if they don’t speak up, now they will get
more trouble later on when the project fails.

8. Thank you