Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
NZ-PHP :10 Warning signs in IT projects
Search
Yann Larrivée
August 27, 2014
Technology
1
140
NZ-PHP :10 Warning signs in IT projects
Yann Larrivée
August 27, 2014
Tweet
Share
More Decks by Yann Larrivée
See All by Yann Larrivée
The hidden secrets of project rescue
ylarrivee
0
360
ConFoo Vancouver - 10 warning signs in IT projects.
ylarrivee
0
69
PHPCon Poland : 10 warning signs in IT projects
ylarrivee
1
100
Vagrant Up: your environment
ylarrivee
0
200
Vagrant Up: your environment
ylarrivee
0
320
10 warning signs in IT projects
ylarrivee
0
240
confoo-2015-beyond-agility.pdf
ylarrivee
0
560
10 warning signs in IT projects
ylarrivee
0
190
Montreal.rb: 10 warning signs in IT projects
ylarrivee
0
75
Other Decks in Technology
See All in Technology
サービスロボット最前線:ugoが挑むPhysical AI活用
kmatsuiugo
0
200
AIドリブンのソフトウェア開発 - うまいやり方とまずいやり方
okdt
PRO
9
640
実践アプリケーション設計 ①データモデルとドメインモデル
recruitengineers
PRO
3
330
Preferred Networks (PFN) とLLM Post-Training チームの紹介 / 第4回 関東Kaggler会 スポンサーセッション
pfn
PRO
1
240
Evolution on AI Agent and Beyond - AGI への道のりと、シンギュラリティの3つのシナリオ
masayamoriofficial
0
190
ECS モニタリング手法大整理
yendoooo
1
120
現場が抱える様々な問題は “組織設計上” の問題によって生じていることがある / Team-oriented Organization Design 20250827
mtx2s
6
1.3k
AIとTDDによるNext.js「隙間ツール」開発の実践
makotot
6
710
microCMS 最新リリース情報(microCMS Meetup 2025)
microcms
0
110
知られざるprops命名の慣習 アクション編
uhyo
11
2.6k
あとはAIに任せて人間は自由に生きる
kentaro
3
1.1k
Webアクセシビリティ入門
recruitengineers
PRO
1
330
Featured
See All Featured
It's Worth the Effort
3n
187
28k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
283
13k
Speed Design
sergeychernyshev
32
1.1k
How to Ace a Technical Interview
jacobian
279
23k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.8k
Automating Front-end Workflow
addyosmani
1370
200k
KATA
mclloyd
32
14k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
61k
Why Our Code Smells
bkeepers
PRO
338
57k
Navigating Team Friction
lara
189
15k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Transcript
foolab.ca | @foolabca 10 warning signs in IT projects. PHP
New Zealand, Wellington – August 28, 2014
foolab.ca | @foolabca Lessons learned from my journey through Mordor.
3 Some statistics • 70% of IT projects fail •
66% of projects go over budget • 33% go over schedule • 17 % under deliver value
4 Yann Larrivée • Developer & consultant at FooLab •
I specialize in project rescue • Writing a book: 10 warning signs in IT projects • Twitter: @ylarrivee
5 Presentation objectives • Identify project threats early • Reduce
the number of failures • Reduce stress, anxiety, headaches • More time with your family
6 Vocabulary • Objectives • Metrics • Success • Failure
7 Objectives - Signs • Stakeholders don't agree on business
objectives • Goals are not communicated • Goals are not understood • Poorly defined goals
8 Objectives - Solutions • Get stakeholders to agree and
sign a contract • Kickoff meeting to explain the goals • Print the goals on a poster hang them in your office • Communicate them to all team members
9 Deadline - Signs • Deadline too tight • Trying
to make a project fit • Working overtime • Deadline too far
10 Deadline - Solutions • Negotiate the delivery date •
Negotiate deliverables based on objectives • Prioritize features based on objectives • Get more skilled developers • Plan time for the unexpected
11 Progress - Signs • No demo within the first
month • Missed demos
12 Progress - Solutions • Weekly release and demo •
Request developers to give development URL • Follow the GIT commits • Yellow-flag task at 50% of completion time • Red-flag task at 75% of completion
13 Team Spirit - Signs • Pointing fingers • Poor
or no collaboration • Negative attitude
14 Team Spirit - Solutions • Break negative conversations •
Change the focus on solutions • Meet team members with negative attitude • Remove bad team members • Get to know your team members
15 Communication – Signs • No one ever reports problem
• People provide excuses for the road blocks • People forward you to the documentation • Languages • Timezones
16 Communication – Solutions • Find the root cause •
Have someone bilingual • Re adjust your schedule • Talk one on one to get the real information
17 Focus – Signs • Methodologies & Architecture • Tools
and framework • Adding cool features • Last minute changes
18 Focus – Solutions • Plan time for R&D outside
of your project • Do R&D before project • Focus Delivering value, not feature • How does it bring us closer to the objective?
19 Documentation – Signs • 50 pages+ novel style documentation
• No documentation • No 10,000 foot view of the project • No or Poor Documentation technical and functional analysis
20 Documentation – Solutions • Plan time for analysis •
Centralize all documentation in source control • Write readable code • Have good tool to write documentation and specs • Keep it straight to the point
21 Quality – Signs • The ghosts problem • Endless
bugs list • No time for quality assurance • No time for performance testing
22 Quality – Solutions • Have staging and product ready
env. • Determine mission critical components • Write test for mission critical components • Have QA before each demo
23 Metrics - Signs • No way to measure the
expected outcome
24 Metrics – Solutions • Level of success (business) •
Level of quality • Level of performance
25 Presentation take-away #1 • Situation appraisal • Objectives •
Metrics • Joint accountability
26 Presentation take-away #2 • How does it bring us
closer to the objective • Break your projects into smaller ones • Socialize with your co-worker • Stay alert
27 Questions? Twitter: @ylarrivee E-mail:
[email protected]
Website: foolab.ca Through powerful
advice, I help businesses maximize their investment and ship projects ahead of time.