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
Agile, etc.
Search
Penelope Phippen
October 21, 2015
Technology
2
230
Agile, etc.
Penelope Phippen
October 21, 2015
Tweet
Share
More Decks by Penelope Phippen
See All by Penelope Phippen
Introducing Rubyfmt
penelope_zone
0
570
How RSpec Works
penelope_zone
0
6.7k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
86
Teaching RSpec to play nice with Rails
penelope_zone
2
150
Little machines that eat strings
penelope_zone
1
110
What is processor (brighton ruby edition)
penelope_zone
0
120
What is processor?
penelope_zone
1
360
extremely defensive coding - rubyconf edition
penelope_zone
0
270
Extremely Defensive Coding
penelope_zone
0
100
Other Decks in Technology
See All in Technology
Data Hubグループ 紹介資料
sansan33
PRO
0
2.2k
Bill One 開発エンジニア 紹介資料
sansan33
PRO
4
14k
20251014_Pythonを実務で徹底的に使いこなした話
ippei0923
0
200
RDS の負荷が高い場合に AWS で取りうる具体策 N 連発/a-series-of-specific-countermeasures-available-on-aws-when-rds-is-under-high-load
emiki
1
270
Node.js 2025: What's new and what's next
ruyadorno
0
320
AWS Top Engineer、浮いてませんか? / As an AWS Top Engineer, Are You Out of Place?
yuj1osm
2
210
技育祭2025【秋】 企業ピッチ/登壇資料(高橋 悟生)
hacobu
PRO
0
100
防災デジタル分野での官民共創の取り組み (2)DIT/CCとD-CERTについて
ditccsugii
0
290
『バイトル』CTOが語る! AIネイティブ世代と切り拓くモノづくり組織
dip_tech
PRO
1
130
プレーリーカードを活用しよう❗❗デジタル名刺交換からはじまるイベント会場交流のススメ
tsukaman
0
160
React19.2のuseEffectEventを追う
maguroalternative
0
240
やる気のない自分との向き合い方/How to Deal with Your Unmotivated Self
sanogemaru
0
510
Featured
See All Featured
Navigating Team Friction
lara
190
15k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
140
34k
KATA
mclloyd
32
15k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
252
21k
Unsuck your backbone
ammeep
671
58k
Building a Modern Day E-commerce SEO Strategy
aleyda
44
7.8k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Why Our Code Smells
bkeepers
PRO
340
57k
Visualization
eitanlees
149
16k
Being A Developer After 40
akosma
91
590k
What’s in a name? Adding method to the madness
productmarketing
PRO
24
3.7k
Documentation Writing (for coders)
carmenintech
75
5.1k
Transcript
Agile, etc
a!/samphippen
None
None
This is not a Judgement
Everyone always screws up all of their software projects
All software projects are always late
No customer ever gets everything they want
No software is ever done
Your primary objective should be to still like everyone
Let’s have some questions !!/samphippen
[email protected]
Let’s have some questions !!/samphippen
[email protected]
Let’s have some questions !!/samphippen
[email protected]
None
The most important lesson
If you pay attention to nothing else
All computer problems are people problems
All computer problems are people problems
No software project ever failed for technical reasons
Not one
“They made us use the wrong database!”
Communication is of dire importance
Communicate with your clients
Communicating with clients
You are already commercially proficient as a developer
Make your clients believe it
Managing clients is its own, separate, complex, skill
In the client’s mind the scope is always changing
In the client’s mind the scope is infinite
You cannot deliver infinite software
You cannot deliver to wildly changing goals
Establish clear scopes with your client
Adjust scopes over time
You are allowed to say no to features
You are allowed to say no to platforms
Hands up time
Mobile apps?
Both android and iOS?
That expectation is unreasonable
Strike it now
Aim for small, working, and complete
Aim for one platform, technology, and framework
Explain that aim to your client
Be reasonable about what you can achieve
Explain what you can achieve reasonably
No client can fault you for that
Technicals
How to not fuck up your project
Do not adopt an “Agile” methodology
Fixed practises
Fixed practises
Agile is a toolbox
Use the tools that work for you, don’t use the
ones that don’t
“Works for you” has multiple definitions
I find you can intuit when process is slowing you
down
Watch how much you ship
Your process is allowed to change over time
Aggressively limit scope
Iterate towards client’s goals
Minimum viable product?
Sign up Login 1 feature
Build this to an absolutely rock solid standard
Give the client something they can show
It is reasonable to assume you will produce an MVP
in this project
More is bonus points!
How to get there?
Work with clients to get high level tasks
You all have an intuition about how to go from
zero to a client’s goals
Communicate with your team
Form a plan
Work out the big tasks
Break tasks down
Break tasks down to really small units
Break tasks down to really small units like really hilariously
small
Gather the team
Turn everything into tasks that will take at most one
person day
That everyone thinks won’t take more than a day
Then take a week to do them
Do two if you’re feeling adventurous
Show work at the end of two weeks
If you can’t break down a task it means two
things
Client hasn’t explained it well enough
Your project isn’t in a state where it can be
done yet
Focus on things that can immediately be done
Two week cycle
Meeting with client on monday
Read the Backlog
Pull items from backlog to be done this cycle
Work out if that’s too much work
Work out if that’s too much work (it is)
Assign work
Aim to have work done by end of week
Team meeting at end of week
Test Find Bugs Refactor
Finish features if they’re not done
Meeting on friday with client
Show work done
Reprioritise backlog
Repeat
You get enough of these cycles to ship something
Progress is measurable
Client can adjust
No “mega features”
“Client acceptance”
Don’t wait until the end of the project
Get it literally every two weeks.
Tools
Trello
Backlog Next up In Progress Done
GitHub
Do pull requests
Don’t merge master unless you’re sure stuff works
Two final suggestions
Use Java
Steer the fuck away from C++
Let’s have some questions a!/samphippen
[email protected]