Building A Cloud Foundry Dojo
A Model For Open Source Communities
Brian Gallagher, EMC Corporation
Building A Cloud Foundry Dojo
Cloud Foundry  Gaining Momentum in Enterprise
Scaling Contributors  Primary Goal
Scaling OSS Too Fast = Stability, Quality ⬇
The Dojo Approach Works  A Model For All OSS!
Follow The ‘Way’  Learn By Doing
CF  Best Choice for Cloud Native Enterprise Apps
Cloud Native Apps
Architecture
Technology
Methodology
Brand Consumer
Service
Organization
You !
Building A Dojo  7 Months In 15 Minutes
People  Selecting The BEST Talent
Java, Ruby, Go
XP, TDD, Agile
Collaborative
Open minded
Change World!
2300+  120+
Phone / Skype
Skill validation
120+  60+
In-person / Skype
Programming test
Speed, aptitude &
empathy
Must score >92
60+  30+
Full day on-site
2 half day pairs
30+  15+
RPI >92
Pairing:
•Yes / Yes = Yes
•Yes / Maybe = Yes
•No = No
15+  11+
6 week onsite Dojo
Daily pairing
The 3rd Day
3/6 wk retrospective
People  EMC Cloud Foundry Team
Yu XuebinVictorThinh
ScottPaulNancyMeganLuke
JeffIdit
CTO
Eric
Recruiting
Emily
Finance
Marie H
HR
Brian RBrian G
Yuval
People  EMC Team Experience
Main reason to join team?
• Fell in love with DevOps culture
• Cloud native is the future
• Test driven team = high quality product
• Executive support for XP, finally
First impressions of Labs?
• So loud. How can work get done?
• Wow, I'd love to work here!.
• Like walking into a dream.
• Looked like an agile startup
How do you like your job?
• Revolutionary coding culture
• Best experience to date.
• Sets bar for now & future
• Like it a lot, Areas to improve NPS
33
How was interview experience?
• Best ever, Really loved it.
• Felt motivated and alive
• Actually *LEARNED* in interview
• Committed code in interview NPS
100
People  Building A Collaborative
Environment
A Tale Of Two Cities
Toilet paperRearview
Mirror
BeeHive of
Energy
Creative
Messaging
Anatomy Of A Dojo – Cambridge, MA
PAIR PROGRAMMING STATIONS
96 Developers
COLLABORATION
SPACE
COLLABORATION
SPACE
TEAM
ROOMS
TEAM
ROOMS
TEAM
ROOMS
TEAM
ROOMS
HIPPO
OFFICES
HIPPO
OFFICES
HIPPO
OFFICES
HIPPO
OFFICES
MEETUP
& SOCIAL
AREA
FOOD !!
PING PONG !!
Process  Combining The Best Of The Best
CI CD
Xtreme
Software
Innovation
Process  Methodology Built In Daily
PAIR PROGRAMMING
Productivity / Innovation / Quality ⬆
Regular pair / team rotations
Risk of attrition ⬇
Rapid scale up / down of teams
Density / Communication ⬆
TEST DRIVEN DEVELOPMENT
Shorter bug cycles
Improves quality - lower CoPQ
Decreases capital & inventory
Improved QA : Dev ratio
DevOPS CI/CD
Rapid release cycles
Reduces technical risk
Increased customer adoption / c-sat
Facilitates ‘fail fast’
Risk
Time between releases
LEAN / AGILE
Improves backlog – 90% features
Decreases sustaining costs
Real time retrospectives
Continual improvements
Improved morale – small chunks
Technology  How Did We Contribute?
E M C C L O U D F O U N D R Y
T E C H N I C A L C O M M U N I T Y
CLOUD FOUNDRY
CONTRIBUTORS
CLOUD FOUNDRY
CONTRIBUTIONS
DOJO OUTSIDE OF PIVOTAL
ANNOUNCED 19 MAR 2015
MAIN AREAS OF
CONTRIBUTION
SPONSORED
CF MEETUPS
8 900+
3
1st
BOSH / CPI
UAA / CC
Technology  Areas Of Future Contribution
E M C C F C O M M U N I T Y
C H A N G I N G T H E W O R L D
C L O U D N A T I V E I N F R A S T R U C T U R E
PERSISTENCE
BARE METAL
DATA PROTECTION
SECURITY
Building A Cloud Foundry Dojo
Cloud Foundry  Gaining Momentum in Enterprise
Scaling Contributors  Primary Goal
Scaling OSS Too Fast = Stability, Quality ⬇
The Dojo Approach Works  A Model For All OSS!
Follow The ‘Way’  Learn By Doing
CF  Best Choice for Cloud Native Enterprise Apps
Cloud Foundry Summit Berlin Keynote

Cloud Foundry Summit Berlin Keynote

  • 2.
    Building A CloudFoundry Dojo A Model For Open Source Communities Brian Gallagher, EMC Corporation
  • 3.
    Building A CloudFoundry Dojo Cloud Foundry  Gaining Momentum in Enterprise Scaling Contributors  Primary Goal Scaling OSS Too Fast = Stability, Quality ⬇ The Dojo Approach Works  A Model For All OSS! Follow The ‘Way’  Learn By Doing CF  Best Choice for Cloud Native Enterprise Apps
  • 4.
  • 5.
    Building A Dojo 7 Months In 15 Minutes
  • 6.
    People  SelectingThe BEST Talent Java, Ruby, Go XP, TDD, Agile Collaborative Open minded Change World! 2300+  120+ Phone / Skype Skill validation 120+  60+ In-person / Skype Programming test Speed, aptitude & empathy Must score >92 60+  30+ Full day on-site 2 half day pairs 30+  15+ RPI >92 Pairing: •Yes / Yes = Yes •Yes / Maybe = Yes •No = No 15+  11+ 6 week onsite Dojo Daily pairing The 3rd Day 3/6 wk retrospective
  • 7.
    People  EMCCloud Foundry Team Yu XuebinVictorThinh ScottPaulNancyMeganLuke JeffIdit CTO Eric Recruiting Emily Finance Marie H HR Brian RBrian G Yuval
  • 8.
    People  EMCTeam Experience Main reason to join team? • Fell in love with DevOps culture • Cloud native is the future • Test driven team = high quality product • Executive support for XP, finally First impressions of Labs? • So loud. How can work get done? • Wow, I'd love to work here!. • Like walking into a dream. • Looked like an agile startup How do you like your job? • Revolutionary coding culture • Best experience to date. • Sets bar for now & future • Like it a lot, Areas to improve NPS 33 How was interview experience? • Best ever, Really loved it. • Felt motivated and alive • Actually *LEARNED* in interview • Committed code in interview NPS 100
  • 9.
    People  BuildingA Collaborative Environment A Tale Of Two Cities Toilet paperRearview Mirror BeeHive of Energy Creative Messaging
  • 10.
    Anatomy Of ADojo – Cambridge, MA PAIR PROGRAMMING STATIONS 96 Developers COLLABORATION SPACE COLLABORATION SPACE TEAM ROOMS TEAM ROOMS TEAM ROOMS TEAM ROOMS HIPPO OFFICES HIPPO OFFICES HIPPO OFFICES HIPPO OFFICES MEETUP & SOCIAL AREA FOOD !! PING PONG !!
  • 11.
    Process  CombiningThe Best Of The Best CI CD Xtreme Software Innovation
  • 12.
    Process  MethodologyBuilt In Daily PAIR PROGRAMMING Productivity / Innovation / Quality ⬆ Regular pair / team rotations Risk of attrition ⬇ Rapid scale up / down of teams Density / Communication ⬆ TEST DRIVEN DEVELOPMENT Shorter bug cycles Improves quality - lower CoPQ Decreases capital & inventory Improved QA : Dev ratio DevOPS CI/CD Rapid release cycles Reduces technical risk Increased customer adoption / c-sat Facilitates ‘fail fast’ Risk Time between releases LEAN / AGILE Improves backlog – 90% features Decreases sustaining costs Real time retrospectives Continual improvements Improved morale – small chunks
  • 13.
    Technology  HowDid We Contribute? E M C C L O U D F O U N D R Y T E C H N I C A L C O M M U N I T Y CLOUD FOUNDRY CONTRIBUTORS CLOUD FOUNDRY CONTRIBUTIONS DOJO OUTSIDE OF PIVOTAL ANNOUNCED 19 MAR 2015 MAIN AREAS OF CONTRIBUTION SPONSORED CF MEETUPS 8 900+ 3 1st BOSH / CPI UAA / CC
  • 14.
    Technology  AreasOf Future Contribution E M C C F C O M M U N I T Y C H A N G I N G T H E W O R L D C L O U D N A T I V E I N F R A S T R U C T U R E PERSISTENCE BARE METAL DATA PROTECTION SECURITY
  • 15.
    Building A CloudFoundry Dojo Cloud Foundry  Gaining Momentum in Enterprise Scaling Contributors  Primary Goal Scaling OSS Too Fast = Stability, Quality ⬇ The Dojo Approach Works  A Model For All OSS! Follow The ‘Way’  Learn By Doing CF  Best Choice for Cloud Native Enterprise Apps