How to destroy a project in one month or less
-
Upload
helder-ferreira -
Category
Business
-
view
193 -
download
4
description
Transcript of How to destroy a project in one month or less
![Page 1: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/1.jpg)
1
How to destroy a project in one month… or less?
Seminars ∙ Post Graduation Project Management ∙ ISBB Helder Ferreira ∙ PMO Director, ISA ∙ [email protected]
13.04.2013
![Page 2: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/2.jpg)
2
• Experiência:
– 16 anos execução de projectos IT;
– 10 anos em Gestão de Programas e Projectos;
– 6 anos a liderar Gabinetes de Gestão de Projecto;
– PMBoK, SCRUM, CMMI5, Lean, 6-sigma e ITSM;
• Certificado em:
– Project Management Professional, PMP
– Scrum Master, CSM
– ITIL IT Service Management, ITSM
• Formação:
– Licenciado em Engª Electrotécnica, FEUP
– Mestrado em Engª Informática, FEUP
– Pós-Graduado em Gestão de Projectos, ISBB
Quem sou?
• Currently PMO Director at Intelligent Sensing Anywhere, SA; • Certifications: PMP - Project Management Professional, CSM – Certified Scrum Master and ITSM – ITIL v3 Service
Management; • License Degree in Electrotechnical Engineering, Masters in Computer Science and Post-Graduation in Project
Management; • 16 years executing projects; • 10 years doing Program/Project Management (Retail, IT, Production, Energy, Internet/Web, Usability, R&D); • 6 years leading Project Management Offices (PMO); • PMBoK, SCRUM, XP, CMMI5, Lean, 6-sigma and ITIL.
![Page 3: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/3.jpg)
3
Do you know what is
the current project’s
success rate?
![Page 4: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/4.jpg)
4
CHAOS Report
![Page 5: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/5.jpg)
5
CHAOS Report
Failed Delayed / Overbudget Success
Source:
![Page 6: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/6.jpg)
6
We keep doing
an awful job
managing
projects!
![Page 7: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/7.jpg)
7
CHAOS Report
• Projects with high budgets • Have success rates really low
• Projects with low budgets • Have success rates very high
![Page 8: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/8.jpg)
8
As more
money gets
involved,
more is the
tendency
(probability)
to do
mistakes!
![Page 9: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/9.jpg)
9
CHAOS Report
Average % of temporal delay in challenged projects
![Page 10: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/10.jpg)
10
When we get delayed,
we REALLY get
delayed!
![Page 11: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/11.jpg)
11
Conclusion:
67% of the worldwide projects
end up like this…
![Page 12: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/12.jpg)
12
So, what is causing
such big disasters on
our projects?
![Page 13: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/13.jpg)
13
35 reasons for these problems to happen
(by no special order or preference)
![Page 14: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/14.jpg)
14
#1 – The choice of the Project Manager
![Page 15: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/15.jpg)
15
The wrong person on the right project.
The choice should be made on the most proper resource to the project in question, having in mind: - Seniority; - Motivations; - Personality.
![Page 16: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/16.jpg)
16
Can a project manager with less “Soft/People Skills” be a good leader?
![Page 17: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/17.jpg)
17
Can a project manager with less “Soft/People Skills” be a good leader?
Sure. Specially in projects with very strong technical components. As technical guru, will lead by example and
peers will respect him/her.
![Page 18: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/18.jpg)
18
But pay attention: Just because someone excels at technical lead, that doesn’t mean it can be as good as a manager or vice-versa.
Hallo Effect
![Page 19: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/19.jpg)
19
#2 – Frequent and uncontrolled scope
changes
![Page 20: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/20.jpg)
20
The expectation gap between: the scope that the project manager believes he/she has to fulfill and the scope from the client side, causes a phenomenon of frequent and continuous changes in the project that at the end will cause huge deviations from the original vision.
Scope Creep
![Page 21: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/21.jpg)
21
The expectation gap between: the scope that the project manager believes he/she has to fulfill and the scope from the client side, causes a phenomenon of frequent and continuous changes in the project that at the end will cause huge deviations from the original vision.
Scope Creep
What causes this behavior?
![Page 22: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/22.jpg)
22
Some probable causes: - Missing the identification of an important stakeholder; - The project need or the problem is not clear; - Sometimes, the client doesn’t know what he/she wants; - Bad requirements definition.
![Page 23: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/23.jpg)
23
Some probable causes: - Missing the identification of an important stakeholder; - The project need or the problem is not clear; - Sometimes, the client doesn’t know what he/she wants; - Bad requirements definition.
Are all changes bad?
![Page 24: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/24.jpg)
24
Not all changes are bad, as long as they contribute positively for the project goal, and as long as there is a control mechanism in place.
Change Control Board
![Page 25: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/25.jpg)
25
The scope change control system also helps to avoid unecessary work in the project.
Gold Plating
![Page 26: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/26.jpg)
26
#3 – Effort Estimation Errors
![Page 27: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/27.jpg)
27
Why do we do
so many errors
estimating?
![Page 28: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/28.jpg)
28
Some of the common causes: - One-time estimate; - Padding; - Forget past history; - Don’t use a WBS; - Don’t validate scope with stakeholders; - Lack of buy-in from the team.
![Page 29: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/29.jpg)
29
Some of the common causes: - One-time estimate; - Padding; - Forget past history; - Don’t use a WBS; - Don’t validate scope with stakeholders; - Lack of buy-in from the team.
How can we
improve?
![Page 30: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/30.jpg)
30
- Create a WBS with the team and the client;
- Use 3-point estimate;
- Use Delphi Technique;
- Use the historical data;
- Apply reserves.
![Page 31: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/31.jpg)
31
- Create a WBS with the team and the client;
- Use 3-point estimate;
- Use Delphi Technique;
- Use the historical data;
- Apply reserves.
Estimating will always be a Guessing Game.
But it should be an Educated Guess.
![Page 32: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/32.jpg)
32
#4 – Lack of communication or
miscommunication
![Page 33: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/33.jpg)
33
![Page 34: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/34.jpg)
34
Why does this
happen so
often?
![Page 35: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/35.jpg)
35
Why does this
happen so
often?
Communication is a complex subject.
![Page 36: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/36.jpg)
36
The human being communicates: - 7% through words; - 38% with voice; - 55% with the body.
Each one of us has 3 communication channels: - Auditive; - Visual; - Kinesthetic; And one of them is dominant…
![Page 37: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/37.jpg)
37
65% of the world population retains Visual information better than Auditive information.
![Page 38: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/38.jpg)
38
Any communication system has one transmitter, one receiver and a channel, through which the transmitter sends a message that should be perceived by the receiver.
![Page 39: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/39.jpg)
39
Any communication system has one transmitter, one receiver and a channel, through which the transmitter sends a message that should be perceived by the receiver. But there is noise.
![Page 40: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/40.jpg)
40
Noise can be caused by: - Nº of transmitters and receivers; - Usage of the wrong communication channel; - Environment where we are; - Attitude of the transmitter and the receiver; - Lack of communication skills; - Culture; - Level of expertise about the message contents.
![Page 41: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/41.jpg)
41
Noise can be caused by: - Nº of transmitters and receivers; - Usage of the wrong communication channel; - Environment where we are; - Attitude of the transmitter and the receiver; - Lack of communication skills; - Culture; - Level of expertise about the message contents.
How can we improve
the communication?
![Page 42: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/42.jpg)
42
Pay attention! Observe. Learn. Imitate. Act.
![Page 43: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/43.jpg)
43
#5 – Lack of risk management
![Page 44: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/44.jpg)
44
Not managing your risks is like walking with your eyes closed.
![Page 45: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/45.jpg)
45
And those that do not see…
![Page 46: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/46.jpg)
46
Common problems in risk management: - Ignore that risks exist; - Don’t consult all the
stakeholders; - Unknowing the risk
tolerances; - Not adding contingency and
management reserves; - Not using the risk register
frequently; - Ignore common sense; - Trust in luck.
![Page 47: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/47.jpg)
47
#6 – Resources are scarce, shared or stolen
![Page 48: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/48.jpg)
48
Sharing is difficult, especially when the resources are scarce and there are opposing
interests. Matrix Organizations
![Page 49: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/49.jpg)
49
Most organizations in the world follow a matrix hierarchy, where resources deal daily with conflict of interests between project management and functional managers.
![Page 50: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/50.jpg)
50
Most organizations in the world follow a matrix hierarchy, where resources deal daily with conflict of interests between project management and functional managers.
Depending on the matrix organization, we might have: - Resources that give priority to their department tasks
instead of project tasks; - Project Managers negotiating for the best resources with
functional managers or other project managers; - Masked costs; - Delays caused by low / shared availability; - Low morale in Projects.
![Page 51: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/51.jpg)
51
Deal for the best resources. Meet with the functional managers. Make your project their project too.
![Page 52: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/52.jpg)
52
#7 – Scope isn’t clear
![Page 53: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/53.jpg)
53
![Page 54: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/54.jpg)
54
Frequently, the client doesn’t really know what he/she wants. What should we do?
![Page 55: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/55.jpg)
55
Frequently, the client doesn’t really know what he/she wants. What should we do?
We should help the client define the requirements and guarantee that everyone has the same understanding on the scope.
WBS, WBS Dictionary Traceability Matrices
Focus Groups, Brainstorming, Interviews …
![Page 56: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/56.jpg)
56
![Page 57: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/57.jpg)
57
#8 – A poor business proposal
![Page 58: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/58.jpg)
58
Some of the common problems are: - Communication Gaps between business, project managers and technical team; - Wrong assumptions made from unclear bid documents; - Bad estimations without risk reserves; - Risks not identified and quantified; - Anxiety to sell at any cost; - Wrong type of contract; - Some ingenuity.
![Page 59: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/59.jpg)
59
Some of the common problems are: - Communication Gaps between business, project managers and technical team; - Wrong assumptions made from unclear bid documents; - Bad estimations without risk reserves; - Risks not identified and quantified; - Anxiety to sell at any cost; - Wrong type of contract; - Some ingenuity.
BETTER
![Page 60: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/60.jpg)
60
When you have good bidding documents and the contract is well structured and documented… … in case of doubt, always read well the documents, your answer is usually there.
![Page 61: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/61.jpg)
61
Any business proposal should be seen as a project.
The team is the commercial, project manager and technical resources.
Don’t ignore the business proposal!
![Page 62: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/62.jpg)
62
#9 – The absent project manager
![Page 63: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/63.jpg)
63
If the project manager doesn’t follow up with the team and the project…
![Page 64: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/64.jpg)
64
Do you know the symptoms: “no time”, “not now”, “I’ll catch you up later”, “send me in an email”, “just speak with…”?
![Page 65: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/65.jpg)
65
Do you know the symptoms: “no time”, “not now”, “I’ll catch you up later”, “send me in an email”, “just speak with…”?
A project manager needs to ensure availability to: - Follow the team; - Control the project; - Do regular meetings; - Collect status; - Manage expectations; - Update the plan; - Do forecasts; - Observe.
![Page 66: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/66.jpg)
66
A project without project manager is like a ship on high sea without its commander.
![Page 67: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/67.jpg)
67
And when there’s no commander…
![Page 68: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/68.jpg)
68
#10 – Lack of sponsor commitment
![Page 69: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/69.jpg)
69
Organizations run several projects, all the time, and not all of them have the same priority or attention from the Sponsor.
![Page 70: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/70.jpg)
70
Organizations run several projects, all the time, and not all of them have the same priority or attention from the Sponsor.
Lack of attention from the sponsor leads to: - Delays on decisions; - Favoring other projects; - Lack of support to
project management; - Lost of motivation.
![Page 71: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/71.jpg)
71
Keep the sponsor on your side. Keep him updated. Protect your project.
![Page 72: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/72.jpg)
72
#11 – Roles and Responsibilities are not
clear
![Page 73: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/73.jpg)
73
Several roles exist on a project team. Being able to clearly define the roles and responsibilities on the project is a determinant factor on the project success.
![Page 74: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/74.jpg)
74
The lack of responsibilities definition causes: - Increase of conflicts; - Lack of commitment from the team actions; - Decrease of productivity;
![Page 75: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/75.jpg)
75
Clearly define the roles and responsibilities of all persons associated to the project.
RACI Matrices Stakeholder Register & Analysis
![Page 76: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/76.jpg)
76
#12 – Ignore the corporate culture
![Page 77: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/77.jpg)
77
Each organization has its own culture, according to its vision and mission.
![Page 78: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/78.jpg)
78
Ignoring the corporate culture can cause some problems, such us: - Resources alienation; - Resistance to change; - Impact on task execution; - Boycotting the project.
![Page 79: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/79.jpg)
79
![Page 80: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/80.jpg)
80
Identify the corporate culture and use it as benefict for your project.
Experimentation & Piloting Lead by Example
![Page 81: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/81.jpg)
81
#13 – Dealing with complex work without
decomposition
![Page 82: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/82.jpg)
82
Let’s build the starship Enterprise.
![Page 83: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/83.jpg)
83
How can I estimate a task of 50 months?
![Page 84: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/84.jpg)
84
How can I estimate a task of 50 months? How can I assess the work progress on a task with 1100 days duration?
![Page 85: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/85.jpg)
85
How can I estimate a task of 50 months? How can I assess the work progress on a task with 1100 days duration? I can’t. At least not in an efficient and realistic way.
![Page 86: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/86.jpg)
86
All complex work needs to be decomposed on smaller tasks, estimated and controllable. These decomposition should roll-out through the project execution.
Decomposition & Progressively Elaborated
![Page 87: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/87.jpg)
87
#14 – “Quick Shot” decisions
![Page 88: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/88.jpg)
88
Taking “on-the-fly” or “quick shot” decisions without first assessing the impact of those actions or with little information, usually end up in: - Conflicts; - Additional delays and costs; - Stakeholders dissatisfaction.
![Page 89: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/89.jpg)
89
Always judge first the impact before get into action.
Ask for more information. Run a simulation. Impact Analysis.
Forecasting (Monte Carlo, EVM)
![Page 90: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/90.jpg)
90
#15 – Not managing expectations
![Page 91: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/91.jpg)
91
What’s the first thing that comes to your mind when someone mentions nuns?
![Page 92: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/92.jpg)
92
Was this your expectation?
![Page 93: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/93.jpg)
93
Aligning the stakeholder's expectations with the project reality bring us some benefits: - No surprises; - Prevention instead of
reaction; - Commitment; - Adjusted and Realistic Goals.
![Page 94: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/94.jpg)
94
Always do expectation’s management. Communication Plan
Stakeholders Register
![Page 95: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/95.jpg)
95
#16 – Bureaucracy and useless meetings
![Page 96: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/96.jpg)
96
Do you know that: - Most company workers participate on 62
monthly meetings; - Half of those meetings are considered waste of
time; - In average, in one month, they spend 31h in non
productive meetings;
* Based on a study made to hundreds of north-american companies.
![Page 97: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/97.jpg)
97
Do you know that: - Most company workers participate on 62
monthly meetings; - Half of those meetings are considered waste of
time; - In average, in one month, they spend 31h in non
productive meetings; - And, in average, the participants of those
meetings: - 91% are day dreaming; - 96% skipped the meeting; - 39% slept during the meeting; - 45% are stunned with the quantity of
meetings they have; - 73% worked on other tasks during the
meeting; - 47% complained it was a pure waste of time.
* Based on a study made to hundreds of north-american companies.
![Page 98: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/98.jpg)
98
Be Agile. Focus the team on what is really important for the project.
Work Performance Information
Tailoring
![Page 99: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/99.jpg)
99
#17 – Lack of documentation
![Page 100: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/100.jpg)
100
![Page 101: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/101.jpg)
101
How did you feel with the “non” explanation on the previous slide?
![Page 102: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/102.jpg)
102
How did you feel with the “non” explanation on the previous slide?
The absence of documentation in the project usually translates into: - Requirements not documented or updated; - Lack of decision records; - No commitment from the team; - Lack of control on the triple constraint; - Additional delays and costs; - Lack of information for customer support; - Frustration.
![Page 103: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/103.jpg)
103
Use common sense but document your project.
Project Charter Project Scope Statement
Risk Register Stakeholders Register
Project Meeting Minutes
![Page 104: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/104.jpg)
104
#18 – No recognition or reward system
![Page 105: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/105.jpg)
105
Every human being needs motivation.
![Page 106: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/106.jpg)
106
Every human being needs motivation. Without motivation the effective and efficient collaboration of a team member is an illusion.
![Page 107: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/107.jpg)
107
One way to increase motivation is the existence of a reward or recognition system, focusing each team member individually.
![Page 108: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/108.jpg)
108
One way to increase motivation is the existence of a reward or recognition system, focusing each team member individually.
Simple systems could be: - Saying “Thank you”; - Give monetary prizes; - Recommend for raises; - Laud in public; - Celebrate milestones; - Give training on a certain
technology.
![Page 109: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/109.jpg)
109
Work with your organization in the sense to reward your team.
Human Resource Management Plan
![Page 110: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/110.jpg)
110
#19 – Intentional decrease of quality
![Page 111: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/111.jpg)
111
Quality – degree to which we fullfill the specified requirements
![Page 112: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/112.jpg)
112
Decreasing quality on the project deliverables usually translates into: - Customer dissatisfaction; - Increase on rework costs; - Delays on releases; - Team with low morale; - Added risks to the project.
![Page 113: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/113.jpg)
113
Define the acceptable quality. Collect metrics. Adjust.
Quality Management Plan Inspection. Audits. Fishbone. Control Charts.
![Page 114: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/114.jpg)
114
#20 – Tendency to “Make” instead of “Buy”
![Page 115: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/115.jpg)
115
It’s Human! We like to reinvent the wheel.
![Page 116: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/116.jpg)
116
It’s Human! We like to reinvent the wheel.
This tendency bring us consequences: - More effort to achieve the
results; - Not reusing existing
products; - Introducing new problems; - Added costs to the project.
![Page 117: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/117.jpg)
117
Do an analysis on what is important or strategic to the project.
Keep the strategic parts in-house. Outsource the rest.
Procurement Management Plan
![Page 118: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/118.jpg)
118
#21 – Making wrong assumptions
![Page 119: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/119.jpg)
119
It’s normal that 2 persons have different interpretations over the same artifact.
![Page 120: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/120.jpg)
120
It’s normal that 2 persons have different interpretations over the same artifact. However assuming only our interpretation without validation usually lead us to costly mistakes.
![Page 121: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/121.jpg)
121
Don’t assume! Read the business proposal. Talk to the stakeholders. Get requirements confirmation.
![Page 122: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/122.jpg)
122
#22 – “One size fits all”
![Page 123: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/123.jpg)
123
All projects are, by nature and definition, different. One methodology or technique that worked well on a certain project might not have application on a different one.
![Page 124: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/124.jpg)
124
Reuse techniques that had produced good results in the past, but be self-critic to
recognize you might need to re-adjust.
Continuous Improvement
![Page 125: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/125.jpg)
125
#23 – Plan by using resources with 100%
availability
![Page 126: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/126.jpg)
126
Did you knew that, in average: - Each worker is interrupted 56 times along the
day; - Work 3 minutes in one task and then change
context to another one; - Spend 2h per day just to recover focus from
distractions; - 80% of the interruptions are considered trivial
and without necessity.
* Based on a study made to hundreds of north-american companies.
![Page 127: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/127.jpg)
127
Did you knew that, in average: - Each worker is interrupted 56 times along the
day; - Work 3 minutes in one task and then change
context to another one; - Spend 2h per day just to recover focus from
distractions; - 80% of the interruptions are considered trivial
and without necessity.
No resource works at 100%. Only 60% ou less from the working schedule is spent productively.
* Based on a study made to hundreds of north-american companies.
![Page 128: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/128.jpg)
128
Plan for less than 100% available resources. It will be more realistic.
Estimating Durations. Project Planning.
![Page 129: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/129.jpg)
129
#24 – Ignoring dependencies
![Page 130: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/130.jpg)
130
Projects are complex and have multiple dependencies between tasks, resources and other projects.
![Page 131: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/131.jpg)
131
Projects are complex and have multiple dependencies between tasks, resources and other projects.
Not respecting these dependencies will cause additional costs and delays and could cause the whole project to be at risk.
![Page 132: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/132.jpg)
132
Discuss the dependencies with the project team. Ask for help and identify risks.
Sequence Activities. Estimate Activity Resources.
![Page 133: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/133.jpg)
133
#25 - Micromanaging
![Page 134: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/134.jpg)
134
Some micromanagement is accepted by junior teams. But it will never be tolerated by more mature teams.
![Page 135: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/135.jpg)
135
Some micromanagement is accepted by junior teams. But it will never be tolerated by more mature teams.
![Page 136: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/136.jpg)
136
Delegate. Do Mentoring and Coaching. Develop Project Team.
![Page 137: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/137.jpg)
137
#26 – Ignoring the problems
![Page 138: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/138.jpg)
138
Hiding or ignoring the problems solves nothing, and can even increase the problem’s impact. The responsibility for the project outcome is always from the Project Manager.
![Page 139: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/139.jpg)
139
Face the problems. Don’t be scare. It’s an opportunity to improve.
Problem Solving.
![Page 140: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/140.jpg)
140
#27 – Managing without a defined
methodology or process
![Page 141: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/141.jpg)
141
Managing a project without a project management methodology is like conducting an orchestra without a stave or baton. Nothing will come out harmonious.
![Page 142: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/142.jpg)
142
Choose the methodology that best applies to the project in question and apply it!
PMBoK SCRUM
![Page 143: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/143.jpg)
143
#28 – Not learning from mistakes
![Page 144: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/144.jpg)
144
Doing mistakes is only human. Important is to recognize it and try again.
![Page 145: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/145.jpg)
145
Doing mistakes is only human. Important is to recognize it and try again.
![Page 146: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/146.jpg)
146
Study project’s historical data. Do lesson learned sessions and distribute them.
Lessons Learned. Historical Data.
![Page 147: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/147.jpg)
147
I also do mistakes and I will keep doing them in the future. This presentation is a portion of my lesson learned data base!
![Page 148: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/148.jpg)
148
#29 – 9 pregnant women conceive and give
birth to a child in 1 month
![Page 149: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/149.jpg)
149
X 9 When project execution delays, some schedule compression techniques are applied. One of the project manager’s tendency is to inject as many resources as possible to try to recover the delay.
![Page 150: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/150.jpg)
150
X 9 When project execution delays, some schedule compression techniques are applied. One of the project manager’s tendency is to inject as many resources as possible to try to recover the delay. However, every time we inject more and more effort into a task, the more complex it gets to manage. Efficiency and productivity decrease.
![Page 151: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/151.jpg)
151
Pay attention to the impact of injecting too many resources in a task to recover delays.
Don’t always pays-off. Law of Diminishing Returns.
Crashing.
![Page 152: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/152.jpg)
152
#30 – I have a plan but I don’t follow it
![Page 153: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/153.jpg)
153
No plan is executed as it is originally described on the business proposal. The need for adjustments is constant. However not doing regular updates to the project plan will lead to project failure.
![Page 154: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/154.jpg)
154
Consequences from not using or updating the project plan: - Team discredit face to planning; - Difficulty doing forecasts; - Stakeholders frustration; - Probably there’s no other project documentation; - Project’s deviations are not calculated.
![Page 155: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/155.jpg)
155
![Page 156: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/156.jpg)
156
#31 – Being vulnerable to top management
interference
![Page 157: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/157.jpg)
157
![Page 158: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/158.jpg)
158
What went wrong
here?
![Page 159: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/159.jpg)
159
The refuge in the “comfort” of the top management’s decisions is an illusion and it’s temporary.
![Page 160: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/160.jpg)
160
The refuge in the “comfort” of the top management’s decisions is an illusion and it’s temporary. The decision must be questioned and assessed, as if it was any other stakeholder. The project manager should do: - Impact analysis; - Validate this impact with the top management; - Redefine project goals in case it’s a go for
execution.
![Page 161: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/161.jpg)
161
The refuge in the “comfort” of the top management’s decisions is an illusion and it’s temporary. The decision must be questioned and assessed, as if it was any other stakeholder. The project manager should do: - Impact analysis; - Validate this impact with the top management; - Redefine project goals in case it’s a go for
execution. The YES-MAN/WOMAN behavior does not lead to commitment, autonomy or even the personal development of the project manager and its team.
![Page 162: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/162.jpg)
162
Avoid YES-MAN/WOMAN behvior. Always assess impacts.
Keep the top management up-to-date. Managing Stakeholders Expectations.
![Page 163: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/163.jpg)
163
#32 – Poor outsourcing control
![Page 164: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/164.jpg)
164
It’s frequent to perform outsourcing to execute a project. However not following up the work of these outsourcers will lead to project failure.
![Page 165: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/165.jpg)
165
Outsourcing is not synonymous of lack of responsibilities.
Define rules and milestones for your partners, and then follow up.
Monitoring & Control Processes.
![Page 166: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/166.jpg)
166
#33 – Reaction instead of prevention
![Page 167: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/167.jpg)
167
Bad planning associated with a weak risk identification are facts that lead project managers to spend most time reacting instead of preventing those issues.
![Page 168: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/168.jpg)
168
Bad planning associated with a weak risk identification are facts that lead project managers to spend most time reacting instead of preventing those issues.
Do Risk Management! Avoiding most problems is a way to get more time to perform other tasks in the project.
![Page 169: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/169.jpg)
169
It’s always better to prevent. Expert Judgement.
Risk Management Processes.
![Page 170: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/170.jpg)
170
#34 – Allowing team conflicts
![Page 171: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/171.jpg)
171
The perfect world
with no conflicts
and everyone is
happy!
![Page 172: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/172.jpg)
172
Conflicts can rarely be avoided. They will naturally pop-up, as a result of the several interactions within the organization. However we should solve them as quickly as we can before they affect the whole project team.
But the perfect
world doesn’t
existe…
![Page 173: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/173.jpg)
173
There are several factors that can contribute to the conflits appearance in projects: - Scheduling tasks; - Projects priorities; - Resources; - Technical opinions; - Administrative procedures; - Money; - Personality.
![Page 174: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/174.jpg)
174
Keep the team harmony. Quickly resolve any conflits.
Conflict Management Techniques
![Page 175: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/175.jpg)
175
#35 – Courage to cancel a project
![Page 176: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/176.jpg)
176
When a project is headed into the abyss, we must assess the capacity and the necessity to keep it running for a bit longer. In extreme cases, we must have the courage to take the tough decision and cancel it.
![Page 177: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/177.jpg)
177
Be able to predict the future, recognize the mistakes, and take the hard decisions.
Expert Judgment.
![Page 178: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/178.jpg)
178
19. Intentional decrease of quality
20. Tendency to “Make” instead of “Buy”
21. Making wrong assumptions
22. “One size fits all”
23. Plan by using resources with 100% availability
24. Ignoring dependencies
25. Micromanaging
26. Ignore the problems
27. Managing without a defined methodology or process
28. Not learning from mistakes
29. 9 pregnant women conceive and give birth to a child in 1 month
30. I have a plan but I don’t follow it
31. Being vulnerable to top management interference
32. Poor outsourcing control
33. Reaction instead of prevention
34. Allowing team conflicts
35. Courage to cancel a project
1. The choice of the project manager
2. Frequent and uncontrolled scope changes
3. Effort estimation errors
4. Lack of communication or miscommunication
5. Lack of risk management
6. Resources are scarce, shared or stolen
7. Scope isn’t clear
8. A poor business proposal
9. The absent project manager
10. Lack of Sponsor commitment
11. Roles and Responsibilities are not clear
12. Ignore the corporate culture
13. Dealing with complex work without decomposition
14. “Quick Shot” decisions
15. Not managing expectations
16. Bureaucracy and useless meetings
17. Lack of documentation
18. No recognition or reward system
Summary
* My top10.
![Page 179: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/179.jpg)
179
Before ending: daily business on projects
http://www.youtube.com/watch?v=HDu5Wo8Yh1k
![Page 180: How to destroy a project in one month or less](https://reader031.fdocuments.in/reader031/viewer/2022020206/5481e44fb47959050d8b4642/html5/thumbnails/180.jpg)
“Operations keeps the lights on, strategy provides a light at the end of the tunnel, but project management is the train engine that moves the organization forward.”
– Joy Gumz, PMI Technology Advisory Member
Thank you for your attention!