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
130
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
330
ConFoo Vancouver - 10 warning signs in IT projects.
ylarrivee
0
60
PHPCon Poland : 10 warning signs in IT projects
ylarrivee
1
94
Vagrant Up: your environment
ylarrivee
0
190
Vagrant Up: your environment
ylarrivee
0
270
10 warning signs in IT projects
ylarrivee
0
210
confoo-2015-beyond-agility.pdf
ylarrivee
0
510
10 warning signs in IT projects
ylarrivee
0
180
Montreal.rb: 10 warning signs in IT projects
ylarrivee
0
69
Other Decks in Technology
See All in Technology
Oracle Exadata Database Service(Dedicated Infrastructure):サービス概要のご紹介
oracle4engineer
PRO
0
9.5k
20240911_New_Relicダッシュボード活用例
speakerdeckfk
0
100
不動産売買取引におけるAIの可能性とプロダクトでのAI活用
zabio3
0
210
忙しい人のためのLangGraph概要まとめ
__ymgc__
1
150
四国クラウドお遍路 2024 in 高知 エンディング
yukataoka
0
190
プログラム検証入門
riru
1
470
DuckDB雑紹介(1.1対応版)@DuckDB座談会
ktz
5
1.2k
AWSを始めた頃に陥りがちなポイントをまとめてみた
oshanqq
1
3.4k
エンジニア視点で見る、 組織で運用されるデザインシステムにするには
shunya078
1
300
SORACOMで実現するIoTのマルチクラウド対応 - IoTでのクリーンアーキテクチャの実現 -
kenichirokimura
0
350
20240912 JJUGナイトセミナー
mii1004
0
130
Road to Single Activity
yurihondo
1
190
Featured
See All Featured
GraphQLとの向き合い方2022年版
quramy
43
13k
What’s in a name? Adding method to the madness
productmarketing
PRO
21
3k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
36
1.9k
The Art of Programming - Codeland 2020
erikaheidi
48
13k
Embracing the Ebb and Flow
colly
83
4.4k
Building Applications with DynamoDB
mza
89
6k
Product Roadmaps are Hard
iamctodd
PRO
48
10k
Documentation Writing (for coders)
carmenintech
65
4.3k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.2k
Web development in the modern age
philhawksworth
204
10k
Code Review Best Practice
trishagee
62
16k
Optimizing for Happiness
mojombo
375
69k
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.