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 Development at Orange Labs
Search
zlu
May 10, 2011
Technology
0
150
Agile Development at Orange Labs
A presentation on agile development in a research environment.
zlu
May 10, 2011
Tweet
Share
More Decks by zlu
See All by zlu
from good to great
zlu
1
150
Demystifing Postgres - Heroku Edition
zlu
1
180
For Yoga Garden Teacher Training
zlu
0
110
Telephony In Rails
zlu
0
83
OpenVoice
zlu
0
120
Status Voicemail
zlu
0
76
Other Decks in Technology
See All in Technology
データ基盤の成長を加速させる:アイスタイルにおける挑戦と教訓
tsuda7
3
650
Datadogとともにオブザーバビリティを布教しよう
mego2221
0
130
7日間でハッキングをはじめる本をはじめてみませんか?_ITエンジニア本大賞2025
nomizone
2
1.4k
High Performance PHP
cmuench
0
140
Developer Summit 2025 [14-D-1] Yuki Hattori
yuhattor
19
5.1k
まだ間に合う! エンジニアのための生成AIアプリ開発入門 on AWS
minorun365
PRO
4
580
Ask! NIKKEIの運用基盤と改善に向けた取り組み / NIKKEI TECH TALK #30
kaitomajima
1
450
Culture Deck
optfit
0
330
ハッキングの世界に迫る~攻撃者の思考で考えるセキュリティ~
nomizone
12
4.5k
依存関係があるコンポーネントは Barrel ファイルでまとめよう
azukiazusa1
3
530
PL900試験から学ぶ Power Platform 基礎知識講座
kumikeyy
0
110
これからSREになる人と、これからもSREをやっていく人へ
masayoshi
6
4.1k
Featured
See All Featured
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
31
2.1k
Bootstrapping a Software Product
garrettdimon
PRO
305
110k
Site-Speed That Sticks
csswizardry
3
370
RailsConf 2023
tenderlove
29
1k
jQuery: Nuts, Bolts and Bling
dougneiner
63
7.6k
Facilitating Awesome Meetings
lara
51
6.2k
What's in a price? How to price your products and services
michaelherold
244
12k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.7k
Fireside Chat
paigeccino
34
3.2k
4 Signs Your Business is Dying
shpigford
182
22k
Optimizing for Happiness
mojombo
376
70k
How to Ace a Technical Interview
jacobian
276
23k
Transcript
Agile @ Orange Labs Zhao Lu & Abhi Hiremaglur
We practiced ~ 100% Pairing Test Driven Development Run all
tests before every commit Regular planning • Around twice a week Frequent deploys • Several times a day, average twice Even more frequent, tiny, commits
We practiced (cont'd) Spikes • Experiment to reduce technical risk • Throwaway
code, not a feature • Precedes a related feature! • Timeboxed Balance • 8hrs of pairing => 8hrs of rest
Test Driven Development
None
Pivotal Tracker
Measurable Progress
100% Pairing
Challenges Only 1 pair • Familiary breeds contempt • Ratholes Personal Space
• Learning about your human compatriot
Challenges (cont'd) Product Owner also an Engineer • Sometimes an anti-pattern
• Step away from the computer Rapidly evolving requirements • Regular planning helped
Serendipity Warm up on the way to work • vs Standups
Plan the day over coffee • vs Standups Brainstorm over lunch • vs Retrospectives/Planning Reflect on the way home • vs Retrospectives
We skipped Continuous Integration • But we wish we hadn't Standups
• Didn't make sense for us Retrospectives • We may still do one Pairing at Pivotal's office • Hive mind & company standups
Ergonimics Shared Computer • 27" iMac • 2 Keyboards + 2 Mice
Wide desk Swap sides frequently • Or you neck will hurt Put away your laptops • 1 pair = 1 computer
Technology Stack Ruby 1.8.7 Rails 3 Postgres 9
Cloud Tropo • for telephony Heroku • for application hosting Amazon S3
• for media storage Panda Stream • for media encoding
Questions?