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
Slide 3
Slide 3 text
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
Slide 4
Slide 4 text
Test Driven Development
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
Pivotal Tracker
Slide 7
Slide 7 text
Measurable Progress
Slide 8
Slide 8 text
100% Pairing
Slide 9
Slide 9 text
Challenges
Only 1 pair
• Familiary breeds contempt
• Ratholes
Personal Space
• Learning about your human
compatriot
Slide 10
Slide 10 text
Challenges (cont'd)
Product Owner also an Engineer
• Sometimes an anti-pattern
• Step away from the computer
Rapidly evolving requirements
• Regular planning helped
Slide 11
Slide 11 text
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
Slide 12
Slide 12 text
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
Slide 13
Slide 13 text
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
Slide 14
Slide 14 text
Technology Stack
Ruby 1.8.7
Rails 3
Postgres 9
Slide 15
Slide 15 text
Cloud
Tropo
• for telephony
Heroku
• for application hosting
Amazon S3
• for media storage
Panda Stream
• for media encoding