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.6k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
85
Teaching RSpec to play nice with Rails
penelope_zone
2
140
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
「AI駆動PO」を考えてみる - 作る速さから価値のスループットへ:検査・適応で未来を開発 / AI-driven product owner. scrummat2025
yosuke_nagai
2
490
組織観点からIAM Identity CenterとIAMの設計を考える
nrinetcom
PRO
1
150
“2件同時配達”の開発舞台裏 〜出前館PMが挑んだダブルピック実現に向けた体験設計〜
demaecan
0
180
実装で解き明かす並行処理の歴史
zozotech
PRO
1
270
非同期処理実行基盤 Delayed脱出 → Solid Queue完全移行への旅路。
srockstyle
3
1.6k
Findy Team+のSOC2取得までの道のり
rvirus0817
0
300
LLMアプリケーション開発におけるセキュリティリスクと対策 / LLM Application Security
flatt_security
7
1.7k
AIが書いたコードをAIが検証する!自律的なモバイルアプリ開発の実現
henteko
1
300
Windows で省エネ
murachiakira
0
150
非エンジニアのあなたもできる&もうやってる!コンテキストエンジニアリング
findy_eventslides
3
880
ユニットテストに対する考え方の変遷 / Everyone should watch his live coding
mdstoy
0
120
業務自動化プラットフォーム Google Agentspace に入門してみる #devio2025
maroon1st
0
180
Featured
See All Featured
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
For a Future-Friendly Web
brad_frost
180
9.9k
The Pragmatic Product Professional
lauravandoore
36
6.9k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
33
2.4k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
30
2.9k
How To Stay Up To Date on Web Technology
chriscoyier
791
250k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
890
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
188
55k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.2k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.6k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
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]