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
PHPCon Poland : 10 warning signs in IT projects
Search
Yann Larrivée
September 30, 2016
Technology
1
94
PHPCon Poland : 10 warning signs in IT projects
Yann Larrivée
September 30, 2016
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
62
Vagrant Up: your environment
ylarrivee
0
190
Vagrant Up: your environment
ylarrivee
0
280
10 warning signs in IT projects
ylarrivee
0
210
confoo-2015-beyond-agility.pdf
ylarrivee
0
520
NZ-PHP :10 Warning signs in IT projects
ylarrivee
1
130
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
ジョブマッチングサービスにおける相互推薦システムの応用事例と課題
hakubishin3
3
620
スクラムチームを立ち上げる〜チーム開発で得られたもの・得られなかったもの〜
ohnoeight
1
280
コンテナのトラブルシューティング目線から AWS SAW についてしゃべってみる
kazzpapa3
1
120
リンクアンドモチベーション ソフトウェアエンジニア向け紹介資料 / Introduction to Link and Motivation for Software Engineers
lmi
4
300k
Deno+JSRでパッケージを作って公開する
askua
0
110
Datachain会社紹介資料(2024年11月) / Company Deck
datachain
4
17k
利きプロセススケジューラ
sat
PRO
4
2.6k
マルチモーダルデータ基盤の課題と観点
neonankiti
1
110
"君は見ているが観察していない"で考えるインシデントマネジメント
grimoh
4
1k
Microsoft Intune アプリのトラブルシューティング
sophiakunii
1
390
ISUCONに強くなるかもしれない日々の過ごしかた/Findy ISUCON 2024-11-14
fujiwara3
3
170
これまでの計測・開発・デプロイ方法全部見せます! / Findy ISUCON 2024-11-14
tohutohu
3
170
Featured
See All Featured
For a Future-Friendly Web
brad_frost
175
9.4k
Being A Developer After 40
akosma
86
590k
A better future with KSS
kneath
238
17k
Designing for Performance
lara
604
68k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
4
360
Happy Clients
brianwarren
97
6.7k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
700
Facilitating Awesome Meetings
lara
49
6.1k
Practical Orchestrator
shlominoach
186
10k
Raft: Consensus for Rubyists
vanstee
136
6.6k
Building Adaptive Systems
keathley
38
2.3k
Code Reviewing Like a Champion
maltzj
520
39k
Transcript
foolab.ca | @foolabca 10 warning signs in IT projects. PHPCon
Poland – October 1st, 2016
2 Some statistics • 70% of IT projects fail •
66% of projects go over budget • 33% go over schedule • 17 % under deliver value
3 Yann Larrivée • Consultant at FooLab • Project rescue
& bring projects to success • Twitter: @ylarrivee • Email :
[email protected]
4 Presentation objectives • Identify project threats early • Reduce
the number of failures • Reduce stress, anxiety, headaches • More time with your family
5 Vocabulary • Objectives • Metrics • Success • Failure
6 Objectives - Signs • Stakeholders don't agree on business
objectives • Goals are not communicated • Goals are not understood • Poorly defined goals
7 Objectives - Solutions Ask these questions: • What are
we trying to accomplish? • Why are we doing this? • What are we trying to improve?
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 is too far
10 Deadline - Solutions • Use simple solutions & technologies
you master • Negotiate the delivery date • Plan time for the unexpected • Prioritize features based on objectives • Negotiate deliverables based on objectives
11 Progress - Signs • No demo within the first
month • Missed demos • You don't even have 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 to 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 • Pick up the phone!
17 Focus – Signs • Methodologies & Architecture • Tools
and framework • Adding cool features • Gold platting • Last minute changes
18 Focus – Solutions • Plan time for R&D outside
of your 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 • Poor technical and functional analysis
20 Documentation – Solutions • Plan time for analysis •
Centralize all documentation in source control • Keep it straight to the point • Write readable code
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 • How many users at peak hours • Have QA before each demo
23 Metrics - Signs • No way to measure the
expected outcome
24 Metrics – Solutions • Level of business success •
Level of quality • Level of performance
25 Presentation take-away • A project fails one day at
a time • How does it bring us closer to the objective? • Plan for the unexpected • Don't underestimate the power of beer.
26 Questions? Twitter: @ylarrivee E-mail:
[email protected]
Website: foolab.ca You see
many of these warning signs in your project? Get advice from an unbiased external source.