What it’s not about
Not about fundraising
Not about going to new markets
Not about the story from the founders
Christian Jennewein
Nicolas Tricot
@cestcri
https://github.com/cestcri
@sholine4
2https://github.com/sholine
Being Lean by nature!
From the very beginningIterative product developmentbusiness-hypothesis-driven
validated learning
True startup spirit
Tech & product share one table
Obtain knowledge + legitimacy
had to prepare the transition
met external lean coach with philosophy
but we needed tools & structure
Change requires time + preparation
Sell scrum internally
●Break resistance to change
●Define + communicate the new rules
●Onboard product team
Scrum by the book
●Split tasks into small units
● Iterations & feedback loops○ Sprints of 1 or 2 weeks
●Quick newbie integration
●Coaching vs. directing
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
The management liked it
●Organisation copes with team growth
●Stay productive
●Maintain high visibility
●Allow for responsibility & commitment
Becoming agile: it works!
● Another good reason to join
● Clarify the roles
● Small and efficient teams
● Self-assigning tasks
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
Kanban without knowing it...
More scrumban than scrum…
Continuous delivery
Limited work in progress
Sprint backlog challenged by new demands
Full kanban
“Scrum does notsuit all teams”
More flexibility regarding the backlog
No need for micro-project management
Less time wasted in ceremonies
Going fully international
Our choice Warsaw, Poland
Strong Tech community
Few pure players
Existing BlaBlaOffice
Developers integrated in existing teams
It’s time to evolve further
Why?
Founders cannot define whole roadmap
Developers became more executors than actors
How?
Assign missions not tasks
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
Testing a goal-oriented team
+ all the required skills inside the team+ high commitment+ solution defined by the team
- need for skill group sync
- ???
Future evolutions?
Founders focus on vision, mission & goals
Having more goal-oriented teams
Define & organise skill groups