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
70
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
250
confoo-2015-beyond-agility.pdf
ylarrivee
0
570
10 warning signs in IT projects
ylarrivee
0
200
Montreal.rb: 10 warning signs in IT projects
ylarrivee
0
77
Other Decks in Technology
See All in Technology
RemoteFunctionを使ったコロケーション
mkazutaka
1
130
様々なファイルシステム
sat
PRO
0
260
入院医療費算定業務をAIで支援する:包括医療費支払い制度とDPCコーディング (公開版)
hagino3000
0
110
DSPy入門
tomehirata
3
360
Okta Identity Governanceで実現する最小権限の原則
demaecan
0
150
abema-trace-sampling-observability-cost-optimization
tetsuya28
0
220
頭部ふわふわ浄酔器
uyupun
0
230
猫でもわかるAmazon Q Developer CLI 解体新書
kentapapa
1
110
Zero Trust DNS でより安全なインターネット アクセス
murachiakira
0
110
現場の壁を乗り越えて、 「計装注入」が拓く オブザーバビリティ / Beyond the Field Barriers: Instrumentation Injection and the Future of Observability
aoto
PRO
1
640
もう外には出ない。より快適なフルリモート環境を目指して
mottyzzz
13
11k
SOTA競争から人間を超える画像認識へ
shinya7y
0
600
Featured
See All Featured
Scaling GitHub
holman
463
140k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.2k
The Pragmatic Product Professional
lauravandoore
36
7k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
132
19k
Stop Working from a Prison Cell
hatefulcrawdad
272
21k
Building an army of robots
kneath
305
46k
Being A Developer After 40
akosma
91
590k
Bash Introduction
62gerente
615
210k
BBQ
matthewcrist
89
9.9k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.7k
Building Flexible Design Systems
yeseniaperezcruz
329
39k
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.