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
210
Agile, etc.
Penelope Phippen
October 21, 2015
Tweet
Share
More Decks by Penelope Phippen
See All by Penelope Phippen
Introducing Rubyfmt
penelope_zone
0
530
How RSpec Works
penelope_zone
0
6.4k
Quick and easy browser testing using RSpec and Rails 5.1
penelope_zone
1
75
Teaching RSpec to play nice with Rails
penelope_zone
2
120
Little machines that eat strings
penelope_zone
1
80
What is processor (brighton ruby edition)
penelope_zone
0
94
What is processor?
penelope_zone
1
340
extremely defensive coding - rubyconf edition
penelope_zone
0
250
Extremely Defensive Coding
penelope_zone
0
86
Other Decks in Technology
See All in Technology
クライアントサイドでよく使われる Debounce処理 をサーバサイドで3回実装した話
yoshiori
1
150
[JAWS-UG金沢支部×コンテナ支部合同企画]コンテナとは何か
furuton
3
240
CyberAgent 生成AI Deep Dive with Amazon Web Services / genai-aws
cyberagentdevelopers
PRO
1
480
Jr. Championsになって、強く連携しながらAWSをもっと使いたい!~AWSに対する期待と行動~
amixedcolor
0
190
いまならこう作りたい AWSコンテナ[本格]入門ハンズオン 〜2024年版 ハンズオンの構想〜
horsewin
9
2.1k
顧客が本当に必要だったもの - パフォーマンス改善編 / Make what is needed
soudai
24
6.7k
ExaDB-D dbaascli で出来ること
oracle4engineer
PRO
0
3.6k
コンテンツを支える 若手ゲームクリエイターの アートディレクションの事例紹介 / cagamefi-game
cyberagentdevelopers
PRO
1
130
20241031_AWS_生成AIハッカソン_GenMuck
tsumita
0
110
AWS CDKでデータリストアの運用、どのように設計する?~Aurora・EFSの実践事例を紹介~/aws-cdk-data-restore-aurora-efs
mhrtech
4
640
生成AIとAWS CDKで実現! 自社ブログレビューの効率化
ymae
2
330
グローバル展開を見据えたサービスにおける機械翻訳プラクティス / dp-ai-translating
cyberagentdevelopers
PRO
1
150
Featured
See All Featured
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
191
16k
The Art of Programming - Codeland 2020
erikaheidi
51
13k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
27
1.9k
Designing the Hi-DPI Web
ddemaree
280
34k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
364
22k
Rebuilding a faster, lazier Slack
samanthasiow
79
8.6k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
31
2.7k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
Git: the NoSQL Database
bkeepers
PRO
425
64k
Ruby is Unlike a Banana
tanoku
96
11k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
28
9.1k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
27
790
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]