$30 off During Our Annual Pro Sale. View Details »

Organising BlaBlaTech @ Lean IT Summit

Organising BlaBlaTech @ Lean IT Summit

This is the story of Christian and Nicolas, two Tech Managers at BlaBlaTech, who shaped the engineering team of the highly successful ridesharing startup. The team has grown from one single French five-person team to a dozen distributed and fully agile teams with 30+ people in only two years. Their main responsibility?

Building and scaling the development team by constantly improving
engineering processes, integrating and training new talents, and anticipating tomorrow’s organization. Their challenges? Delivering the same level of quality software and services in an ever-growing business where customer feedback is instantaneous and shared all over the web.

Christian Jennewein

October 08, 2015
Tweet

More Decks by Christian Jennewein

Other Decks in Technology

Transcript

  1. BlaBlaCar
    BlaBlaTech
    @
    8 October 2015

    View Slide

  2. Organising
    BlaBlaTech
    8 October 2015
    BlaBlaCar

    View Slide

  3. What it’s not about
    ● Not about fundraising
    ● Not about going to new markets
    ● Not about the story from the founders

    View Slide

  4. Christian
    Jennewein
    Nicolas
    Tricot
    @cestcri
    https://github.com/cestcri
    @sholine42
    https://github.com/sholine

    View Slide

  5. BlaBlaWhat?

    View Slide

  6. 30€ 30€
    120 €
    30€ 30€

    View Slide

  7. 30€ 30€
    120 €
    30€ 30€

    View Slide

  8. 20M
    15M
    10M
    5M
    2009 2010 2011 2012 2013 2014 2015
    20 million
    members in 2015

    View Slide

  9. ...in 19 countries

    View Slide

  10. ...with 14 offices

    View Slide

  11. View Slide

  12. Build the biggest
    international transportation
    network

    View Slide

  13. From BlaBlaCar to
    BlaBlaTech

    View Slide

  14. BlaBlaTech missions
    + Experts...

    View Slide

  15. BlaBlaTech culture

    View Slide

  16. Internal hackathons

    View Slide

  17. Loving beer

    View Slide

  18. Common set of values

    View Slide

  19. Common set of values

    View Slide

  20. Common set of values

    View Slide

  21. Common set of values

    View Slide

  22. Common set of values

    View Slide

  23. Common set of values

    View Slide

  24. View Slide

  25. Warsaw
    Bucharest
    Paris
    People

    View Slide

  26. Servers

    View Slide

  27. Case study

    View Slide

  28. Being Lean by nature!
    ● From the very beginning
    ○ Iterative product development
    ○ business-hypothesis-driven
    ○ validated learning
    ● True startup spirit
    ● Tech & product share one table

    View Slide

  29. No real idea about lean,
    we just did it

    View Slide

  30. View Slide

  31. 2012

    View Slide

  32. Hyper-growth at BlaBlaCar

    View Slide

  33. How to stay efficient?

    View Slide

  34. How to handle a growing team?
    Let’s try scrum, it’s cool
    (what we did instead: stand-ups only…)

    View Slide

  35. View Slide

  36. Scrum implementation
    ● Lack of knowledge
    ● Lack of legitimacy
    ● No added value
    ● No leader

    View Slide

  37. ● Introducing notions of agility
    ● Preparing the next steps
    Fail? Learn!

    View Slide

  38. Privilege member requests

    View Slide

  39. 2012

    View Slide

  40. 2013

    View Slide

  41. Obtain knowledge + legitimacy
    ● had to prepare the transition
    ● met external lean coach with philosophy
    ● but we needed tools & structure

    View Slide

  42. “Brainstormed in June,
    applied in July”

    View Slide

  43. Change requires time + preparation
    ● Sell scrum internally
    ● Break resistance to change
    ● Define + communicate the new rules
    ● Onboard product team

    View Slide

  44. Mr. Scrum, tear down this wall
    tech product

    View Slide

  45. Scrum by the book
    ● Split tasks into small units
    ● Iterations & feedback loops
    ○ Sprints of 1 or 2 weeks
    ● Quick newbie integration
    ● Coaching vs. directing

    View Slide

  46. ScrumGuide says...
    ScrumGuide says...
    TURN LEFT NOW!
    TURN LEFT NOW!

    View Slide

  47. View Slide

  48. 2013

    View Slide

  49. 2014

    View Slide

  50. Integrating remote teams
    ● Faster growth difficult only in Paris
    ● We integrate 5 remote developers
    ● Shift all communication to English
    ● Generate face time
    ● Have a dedicated scrum master & PO

    View Slide

  51. Fully data driven

    View Slide

  52. PINK
    DB
    ADMIN
    OPS
    INFRA
    DEVOPS
    WHITE
    DEV
    ARCHI
    DATA
    RED
    BLUE
    GREEN
    YELLOW
    PURPLE
    ORANGE

    View Slide

  53. 2014

    View Slide

  54. The age of maturity

    View Slide

  55. View Slide

  56. The teams liked it
    Worse than before

    View Slide

  57. The management liked it
    ● Organisation copes with team growth
    ● Stay productive
    ● Maintain high visibility
    ● Allow for responsibility & commitment

    View Slide

  58. Becoming agile: it works!
    ● Another good reason to join
    ● Clarify the roles
    ● Small and efficient teams
    ● Self-assigning tasks

    View Slide

  59. The dark side

    View Slide

  60. Some problems...
    ● (too much) focus on tickets, lack of big picture
    ● One big remote team working together
    ● Perception of being controlled by metrics
    ● Rigid sprints vs. prod issues vs. roadmap

    View Slide

  61. 2014

    View Slide

  62. 2015

    View Slide

  63. Quarterly roadmap
    prioritisation by founders
    and monitoring of progress

    View Slide

  64. Kanban without knowing it...
    More scrumban than scrum…
    ● Continuous delivery
    ● Limited work in progress
    ● Sprint backlog challenged by
    new demands

    View Slide

  65. Full kanban
    “Scrum does not
    suit all teams”
    ● More flexibility regarding the backlog
    ● No need for micro-project management
    ● Less time wasted in ceremonies

    View Slide

  66. Member voice team

    View Slide

  67. Going fully international
    ● Our choice Warsaw, Poland
    ● Strong Tech community
    ● Few pure players
    ● Existing BlaBlaOffice
    ● Developers integrated in existing teams

    View Slide

  68. It’s time to evolve further
    Why?
    ● Founders cannot define whole roadmap
    ● Developers became more executors than actors
    How?
    ● Assign missions not tasks

    View Slide

  69. Testing a project-oriented team
    + one big feature for one ephemeral team
    + all the required skills inside the team
    + high commitment
    - solution not from the team
    - need for skill group sync

    View Slide

  70. Testing a goal-oriented team
    + all the required skills inside the team
    + high commitment
    + solution defined by the team
    - need for skill group sync
    - ???

    View Slide

  71. 2015

    View Slide

  72. 2016

    View Slide

  73. Future evolutions?
    ● Founders focus on vision, mission & goals
    ● Having more goal-oriented teams
    ● Define & organise skill groups

    View Slide

  74. Build

    View Slide

  75. Measure

    View Slide

  76. Learn

    View Slide

  77. Repeat

    View Slide

  78. Build

    View Slide

  79. Measure

    View Slide

  80. Learn

    View Slide

  81. Repeat

    View Slide

  82. Build

    View Slide

  83. Measure

    View Slide

  84. Learn

    View Slide

  85. Repeat

    View Slide

  86. Build. Measure. Learn. Repeat.
    Questions?

    View Slide