SlideShare una empresa de Scribd logo
1 de 36
Descargar para leer sin conexión
An Agile Journey
How we evolved our Agile organization
from a Feature Factory to Business Teams driven by OKR
My name is Frédéric Rivain, CTO of Dashlane.
We build a Password Manager, to
help you manage your identity
and your payments in a simple
and secure way everywhere.
A bit of context
Funded in 2009 by Bernard Liautaud and 3 Centrale students
110 employees in Paris and New York
• Product & Engineering in Paris
• Marketing & Sales in New York
4 business lines:
• Consumer product (B2C)
• Enterprise offer (B2B)
• Financial Partners
• API and Dev Ecosystem
• 7 “production” teams
Agile timeline
• Iterative evolution.
• Learning as we grow.
• Adapt to our needs and scale.
• Various states of maturity.
Garage Mode
2014
Move to Agile.
Scrum by the Book.
Roadmap &
Portfolio
2015
OKR
Feature
Teams
2016
2017
Half-Baked Agility*
Operations
Tactics
Strategy
Culture
Agile Development
Scrum, Kaban…
Lean
Goals / OKR
1
2
3
4
* As quoted from Felipe Castro
Becoming Agile
1. Agile methodology at the team operational level
• We started from Scrum. A lot by the book.
• Today we evolved into more of a Scrumban mode in many
teams.
• Key shared principles between all teams:
• 2-week cadence for all teams
• 3 clearly identified roles
• Product Owner
• Scrum Master (possibly rotating among team members)
• Business Stakeholders
• Regular stand-ups
• Review at the end of each cycle, with team + stakeholders + everybody
interested
2. Tactics
• Scrum is about operational agility. A methodology for day-to-day organization.
• Wrap the Scrum cycle with a Lean process, to improve Alignement and Visibility
at Company level.
Formalize the
Project
Collaborative
Specifications
Development
Validation
Release to
Production
Assess
results
Evaluate and
prioritize
AGILE PRODUCTION
Stakeholder
Lean overall approach
Agile production cycle
2. Roadmap & Portfolio
• Introducing 2 tools, inspired from SAFe framework, influenced by Lean approach
• A portfolio = a high-level view of all our projects at Dashlane. Live board in Jira. At any
point in time, you can know everything that is being worked on by the teams.
• A quarterly Roadmap = a view by team, by quarter, by objective. Linked dynamically
to the Portfolio. Provides vision, consistency and alignement.
2. The perfect Feature Factory
• Build Project-driven roadmaps
• Track feature delivery
• Only Agile at the Operations level and
partially at the Tactics level.
• Strategy is based on annual goals with
overall top-down planning.
3. Strategy
• How to build an Agile Strategy?
• How do we move to Full-Stack Agility?
• Move away from waterfall / top-down goals.
• Introducing OKR…
Operations
Tactics
Strategy
Culture
Agile Development
Scrum, Kaban…
Lean
Goals / OKR
1
2
3
4
3. OKR – Objective & Key Results
• A framework of defining and tracking objectives
and their outcomes
• Created by Intel, in the 1970s
• Made popular by John Doerr and Google
• Adopted by most Silicon Valley companies
3. OKR Components
• O = Objective:
• Aspirational.
• Memorable – Simpler, shorter, remarkable.
• Qualitative.
• KR = Key Results:
• 2-5 per Objective.
• Quantitative & Measurable.
• Metrics (recommended) or Milestones.
OKR Example
• Objective: Delight our customers
• Key Results:
• Increase average weekly visits from 3.1 to 3.3 per active user
• Improve Net Promoter Score from 46% to 52%.
• Increase non paid (organic) traffic from 70% to 80%.
• Increase engagement (users that complete a full profile) from 60% to 75%.
• Objective: Taming the Autofill Dragon
• Key Results:
• Achieve successful autologin on the top 50 Chinese websites
• Achieve successful autologin on the top 50 Korean websites
O can be fun!
3. Dashlane OKR
• Yearly Company OKR – High-Level Strategy
• KR can be reviewed and adapted every quarter or as needed.
• But O should theoretically remain stable in time
• Team Quarterly OKR – Tactical Short Term
• Impacting Company OKR
• No individual OKR, by choice.
3. The move to OKR
• It is hard, for everybody but especially for engineering.
• Big change of mindset:
• Focus on business impact and value first
• Projects come second.
• In theory, delivering a feature does not really count for success.
• Need to be very data-driven.
• Need to accelerate massively the cycle time and release process.
• Need experimentation tooling such as strong A/B Test Engine and Feature-Flipping.
• Need to shift to a more bottom-up process (~60% bottom-up, ~40% top-down).
3. Our first Fails
• Too many OKRs per team.
• Way way too ambitious. Aim for roofshots, not moonshots.
• Team not capable of measuring a KR.
• We should decide faster in a Quarter to drop a KR.
• Bottom-up is hard also for the teams.
• Several quarterly cycles before it starts becoming easier.
• Need to manage the feeling that OKR are bullshit.
3. Link between OKR & Roadmap
• We still have projects and features.
• But they are mostly defined to achieve goals as set by OKR.
• Not all projects are associated to OKR.
Quarterly OKR  Quarterly Roadmap
3. Slice the Elephant
• With OKR, it is even clearer that you need to split big projects.
• Ship fast, Experiment, iterate. MVP / Skateboard approach.
• For big projects, adapt KR to be more technical KR or learning KR.
3. Our OKR-Roadmap process today
• One month before beginning of the quarter, the Lead Stakeholder & Product Owner kick off the OKR & Roadmap process:
• Get input from the team
• Get input from the stakeholder(s)
• Get input from the exec team
• Agree on the MUST HAVE of the quarter so that specs can be ready from D1 of the quarter.
• PO & Lead Stakeholder prepare high level guidelines that are validated by exec team
• Last 2 weeks of the previous quarter are dedicated to OKR & Roadmap definition for each team:
• PO needs to provision some sprint time to allow the teams to focus on the process
• Drafting is documented on Confluence to allow iteration / back & forth with stakeholders etc.
• OKR are ready at the end of the 2 weeks:
• Both O & KR properly worded
• Metrics baseline & target are agreed upon
• Tracking & reporting enabled
• Mapping with Company OKR done
• Feedback from stakeholders has been taken into account
• Roadmap at the end of the 2 weeks:
• all teams prepare a confluence page summarizing their OKR and the related portfolio projects for the quarter
• Exec team meets and goes over each team's OKR/Roadmap page to challenge teams and sign off on the Quarter's
program
• During the Quarter teams report on their OKR in a standardized way at each sprint review
3. OKR learnings
• Don’t be too ambitious, else teams get frustrated with unreachable goals.
Roofshots rather than Moonshots.
• Have fewer O and KR rather than too many. Otherwise you loose focus.
• Not all projects/initiatives are related to OKR.
• Allow for different types of KR:
• Learning metrics
• Business metrics
• Possibly technical metrics
• Time those KR based on the current progress and based on the outcome you are
looking for. Learning first before optimizing and impacting business for instance.
Team Organization
Legacy Platform Teams
• Originally, platform teams:
• Desktop, iOs, Android, Web Product, Server,
Semantic Engine
• Works well for small teams. With one line
of business.
• Starts hurting as you grow the team and as
you diversify:
• Synchronization issues between platforms
• Inconsistency in product
• Technical focus > Business focus
Moving to Business/Feature Teams
• Inspired by the Feature Teams model (a la Spotify)
• Applied to the Dashlane context
• Cross-functional teams including:
• Product, Development, QA + Design, Analytics, Product Marketing, User Support
• « Mini Startup » inside the company, with end-to-end responsibility on their business
scope. Associated closely to business stakeholders.
• 7 teams including
• 3 focused on end-user: Acquisition, Conversion, Retention
• 2 focused on B2B
• 1 for Partnerships
• 1 to make use of our semantic engine
Managing change
• Work closely with all team members to define the target, when and how
• Do it when you have enough of each skill to make it sustainable.
• We decided for a Big-Bang switch between 2 quarters. 1 full week dedicated
to the switch.
• Take your time to prepare.
• Use the opportunity for team building, training.
• Communicate, communicate, communicate…
• Listen, listen, listen…
Side impacts
• Thinking Platforms + Teams
• Manage platform organization:
• Need more communication
• Organizing tech work in « Platform Days »
• Adaptations to the Release Process and the way all teams coordinate.
• New management style for Tech Leads, with engineers distributed in various
teams.
• Changing the way we think about resource allocation and roadmap
definition.
Mobility, Flexibility and Taskforces
• Mobility: allow for developers to change teams from time to time.
• Flexibility: adapt resource allocation based on needs.
• Taskforces:
• Some projects don’t fit in a team.
• Plan it from the start as part of the process.
• Create short-lived taskforces with a clear project goal.
Then what ?
• The easy part is the switch. Fun and exciting time.
• The hard part follows: making it work.
• Changing our way of working to optimize the new organization.
• Be patient. It takes time.
• Inspect and adapt.
The Future
Tuning time
• We are still learning as we do.
• Tuning OKR to make them more efficient.
• Identifying friction points.
• Overcoming obstacles
• Improving the foundations that support our organization
• Data: stronger and more real-time analytics
• Product: adapting the way we design product
• Technical: strengthening and accelerating our release pipeline. Industrializing and
automating.
Future experiments
• Nothing planned yet, but interested in looking into:
• Design Sprint
• Holacracy and other different types of organizations
Final Words of Advice
Tips and Tricks
• Invest time to get support from both the Top and the Bottom: from Execs to Team
members. Convince before doing.
• Each change is hard as it is. You need everybody to be on board.
• There are strong prerequisites to all these evolutions
• Data: strong analytics
• Product: each change has an impact in the way you design product
• Technical: having a smooth and fast release pipeline is key
• Culture: be ready for change.
• Learn as you go and adapt to your company maturity.
• Adapt to your own context.
Questions ?
References
• OKR
• http://felipecastro.com/en/okr/what-is-okr/
• https://www.slideshare.net/meetfelipe/slides-agile2016-stop-using-agile-with-waterfall-
goals-goal-agility-with-okr
• https://medium.com/the-alignment-shop/the-okr-journey-a-guide-for-okr-adoption-
beb775ca2a5a
• Feature Teams
• https://www.slideshare.net/JoakimSunden/agile-at-spotify
• https://www.slideshare.net/ashlychrstn/full-stackagile-squads-chapters-tribes-and-
guilds
• https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
Thank you
© 2017 Dashlane, Inc

Más contenido relacionado

La actualidad más candente

Introduction to scaled agile framework
Introduction to scaled agile frameworkIntroduction to scaled agile framework
Introduction to scaled agile frameworkKAVITHA KRISHNAN
 
Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Анна Мамаєва: When SAFe is safe. Agile для дорослих компанійАнна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Анна Мамаєва: When SAFe is safe. Agile для дорослих компанійLviv Startup Club
 
Scaling Agile: SAFe with Visual Studio Team Foundation Server
Scaling Agile: SAFe with Visual Studio Team Foundation Server Scaling Agile: SAFe with Visual Studio Team Foundation Server
Scaling Agile: SAFe with Visual Studio Team Foundation Server InCycle Software
 
Relieveing the Testing Bottle Neck - Webinar
Relieveing the Testing Bottle Neck - WebinarRelieveing the Testing Bottle Neck - Webinar
Relieveing the Testing Bottle Neck - WebinarCprime
 
W4 0245 agility_v1
W4 0245 agility_v1W4 0245 agility_v1
W4 0245 agility_v1colleenfry
 
Building Quality In in SAFe – The Testing Organization’s Perspective
Building Quality In in SAFe – The Testing Organization’s Perspective	  Building Quality In in SAFe – The Testing Organization’s Perspective
Building Quality In in SAFe – The Testing Organization’s Perspective Yuval Yeret
 
Pricing Pitfalls...and How to Counter Them
Pricing Pitfalls...and How to Counter ThemPricing Pitfalls...and How to Counter Them
Pricing Pitfalls...and How to Counter ThemGus Prestera
 
The Roles and Responsibilities in an Agile Project and Organization
The Roles and Responsibilities in an Agile Project and OrganizationThe Roles and Responsibilities in an Agile Project and Organization
The Roles and Responsibilities in an Agile Project and OrganizationToivo Vaje
 
DevOps, SAFe and critical information bearers: A practical approach for plann...
DevOps, SAFe and critical information bearers: A practical approach for plann...DevOps, SAFe and critical information bearers: A practical approach for plann...
DevOps, SAFe and critical information bearers: A practical approach for plann...Bosnia Agile
 
10 Essential SAFe(tm) patterns you should focus on when scaling Agile
10 Essential SAFe(tm) patterns you should focus on when scaling Agile10 Essential SAFe(tm) patterns you should focus on when scaling Agile
10 Essential SAFe(tm) patterns you should focus on when scaling AgileYuval Yeret
 
Agile: Not Just for Sofware
Agile: Not Just for SofwareAgile: Not Just for Sofware
Agile: Not Just for SofwareJohn Carter
 
Kanban testing
Kanban testingKanban testing
Kanban testingCprime
 
Agile foundation and agile myths
Agile foundation and agile mythsAgile foundation and agile myths
Agile foundation and agile mythsDennis Stevens
 
Agile methodology v 4.5 s
Agile methodology   v 4.5 sAgile methodology   v 4.5 s
Agile methodology v 4.5 sJames Sutter
 
How to measure the outcome of agile transformation
How to measure the outcome of agile transformationHow to measure the outcome of agile transformation
How to measure the outcome of agile transformationRahul Sudame
 
Agile Transformation: People, Process and Tools to Make Your Transformation S...
Agile Transformation: People, Process and Tools to Make Your Transformation S...Agile Transformation: People, Process and Tools to Make Your Transformation S...
Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony
 
Євген Лабунський: Agile in Enterprise. How do we do it
Євген Лабунський: Agile in Enterprise. How do we do itЄвген Лабунський: Agile in Enterprise. How do we do it
Євген Лабунський: Agile in Enterprise. How do we do itLviv Startup Club
 

La actualidad más candente (20)

Scaling Agile
Scaling Agile Scaling Agile
Scaling Agile
 
Introduction to scaled agile framework
Introduction to scaled agile frameworkIntroduction to scaled agile framework
Introduction to scaled agile framework
 
An Overview of SAFe
An Overview of SAFeAn Overview of SAFe
An Overview of SAFe
 
Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Анна Мамаєва: When SAFe is safe. Agile для дорослих компанійАнна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній
 
Scaling Agile: SAFe with Visual Studio Team Foundation Server
Scaling Agile: SAFe with Visual Studio Team Foundation Server Scaling Agile: SAFe with Visual Studio Team Foundation Server
Scaling Agile: SAFe with Visual Studio Team Foundation Server
 
Relieveing the Testing Bottle Neck - Webinar
Relieveing the Testing Bottle Neck - WebinarRelieveing the Testing Bottle Neck - Webinar
Relieveing the Testing Bottle Neck - Webinar
 
W4 0245 agility_v1
W4 0245 agility_v1W4 0245 agility_v1
W4 0245 agility_v1
 
Building Quality In in SAFe – The Testing Organization’s Perspective
Building Quality In in SAFe – The Testing Organization’s Perspective	  Building Quality In in SAFe – The Testing Organization’s Perspective
Building Quality In in SAFe – The Testing Organization’s Perspective
 
Pricing Pitfalls...and How to Counter Them
Pricing Pitfalls...and How to Counter ThemPricing Pitfalls...and How to Counter Them
Pricing Pitfalls...and How to Counter Them
 
The Roles and Responsibilities in an Agile Project and Organization
The Roles and Responsibilities in an Agile Project and OrganizationThe Roles and Responsibilities in an Agile Project and Organization
The Roles and Responsibilities in an Agile Project and Organization
 
DevOps, SAFe and critical information bearers: A practical approach for plann...
DevOps, SAFe and critical information bearers: A practical approach for plann...DevOps, SAFe and critical information bearers: A practical approach for plann...
DevOps, SAFe and critical information bearers: A practical approach for plann...
 
10 Essential SAFe(tm) patterns you should focus on when scaling Agile
10 Essential SAFe(tm) patterns you should focus on when scaling Agile10 Essential SAFe(tm) patterns you should focus on when scaling Agile
10 Essential SAFe(tm) patterns you should focus on when scaling Agile
 
Agile: Not Just for Sofware
Agile: Not Just for SofwareAgile: Not Just for Sofware
Agile: Not Just for Sofware
 
Agile for Business
Agile for BusinessAgile for Business
Agile for Business
 
Kanban testing
Kanban testingKanban testing
Kanban testing
 
Agile foundation and agile myths
Agile foundation and agile mythsAgile foundation and agile myths
Agile foundation and agile myths
 
Agile methodology v 4.5 s
Agile methodology   v 4.5 sAgile methodology   v 4.5 s
Agile methodology v 4.5 s
 
How to measure the outcome of agile transformation
How to measure the outcome of agile transformationHow to measure the outcome of agile transformation
How to measure the outcome of agile transformation
 
Agile Transformation: People, Process and Tools to Make Your Transformation S...
Agile Transformation: People, Process and Tools to Make Your Transformation S...Agile Transformation: People, Process and Tools to Make Your Transformation S...
Agile Transformation: People, Process and Tools to Make Your Transformation S...
 
Євген Лабунський: Agile in Enterprise. How do we do it
Євген Лабунський: Agile in Enterprise. How do we do itЄвген Лабунський: Agile in Enterprise. How do we do it
Євген Лабунський: Agile in Enterprise. How do we do it
 

Similar a The Dashlane Agile Journey

Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...
Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...
Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...Scrum Bangalore
 
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...Business of Software Conference
 
Understanding-Agile &Scrum.pdf
Understanding-Agile &Scrum.pdfUnderstanding-Agile &Scrum.pdf
Understanding-Agile &Scrum.pdfSwapnikaReddy6
 
Dashlane Mission Teams
Dashlane Mission TeamsDashlane Mission Teams
Dashlane Mission TeamsDashlane
 
Emptying Your Cup an Agile Primer
Emptying Your Cup an Agile Primer Emptying Your Cup an Agile Primer
Emptying Your Cup an Agile Primer Todd Shelton
 
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...admford
 
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...Maurizio Mancini
 
Methodology lean IT transformation mission
Methodology   lean IT transformation missionMethodology   lean IT transformation mission
Methodology lean IT transformation missionJean-François Nguyen
 
Agile methodology and Scrum Framewwork
Agile methodology and Scrum FramewworkAgile methodology and Scrum Framewwork
Agile methodology and Scrum Framewworksalmanahmed368
 
Code Yellow: Helping operations top-heavy teams the smart way
Code Yellow: Helping operations top-heavy teams the smart wayCode Yellow: Helping operations top-heavy teams the smart way
Code Yellow: Helping operations top-heavy teams the smart wayMichael Kehoe
 
Scrum Process For Offshore Team
Scrum Process For Offshore TeamScrum Process For Offshore Team
Scrum Process For Offshore TeamPaul Nguyen
 
Agile Adoption - What's the Payoff?
Agile Adoption - What's the Payoff? Agile Adoption - What's the Payoff?
Agile Adoption - What's the Payoff? Sparkhound Inc.
 

Similar a The Dashlane Agile Journey (20)

Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...
Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...
Scrum Bangalore 14th MeetUp 05 September 2015 - Scaling Agile - Saikat Das - ...
 
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
BoS2015 Jeff Szczepanski – COO, Stack Exchange - Stack Overflow. Scaling a Te...
 
Journey toagile published
Journey toagile publishedJourney toagile published
Journey toagile published
 
Understanding-Agile &Scrum.pdf
Understanding-Agile &Scrum.pdfUnderstanding-Agile &Scrum.pdf
Understanding-Agile &Scrum.pdf
 
State of Agile 2017
State of Agile 2017State of Agile 2017
State of Agile 2017
 
Dashlane Mission Teams
Dashlane Mission TeamsDashlane Mission Teams
Dashlane Mission Teams
 
Emptying Your Cup an Agile Primer
Emptying Your Cup an Agile Primer Emptying Your Cup an Agile Primer
Emptying Your Cup an Agile Primer
 
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
When Management Asks You: “Do You Accept Agile as Your Lord and Savior?” - Ci...
 
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...
Getting Agile Right - Rebooting an Agile Organization in 100 days - Agile Tou...
 
Methodology lean IT transformation mission
Methodology   lean IT transformation missionMethodology   lean IT transformation mission
Methodology lean IT transformation mission
 
Agile India 2014 - Venkatraman L on Scaling Agile
Agile India 2014 - Venkatraman L on Scaling AgileAgile India 2014 - Venkatraman L on Scaling Agile
Agile India 2014 - Venkatraman L on Scaling Agile
 
Agile tutorial
Agile tutorialAgile tutorial
Agile tutorial
 
Agile methodology and Scrum Framewwork
Agile methodology and Scrum FramewworkAgile methodology and Scrum Framewwork
Agile methodology and Scrum Framewwork
 
Code Yellow: Helping operations top-heavy teams the smart way
Code Yellow: Helping operations top-heavy teams the smart wayCode Yellow: Helping operations top-heavy teams the smart way
Code Yellow: Helping operations top-heavy teams the smart way
 
Effective Scrum
Effective ScrumEffective Scrum
Effective Scrum
 
Project to Product roadmap
Project to Product roadmapProject to Product roadmap
Project to Product roadmap
 
An approach to scaling Agile in Mid size Enterprise Application Stack/ Products
An approach to scaling Agile in Mid size Enterprise Application Stack/ Products An approach to scaling Agile in Mid size Enterprise Application Stack/ Products
An approach to scaling Agile in Mid size Enterprise Application Stack/ Products
 
Scrum Process For Offshore Team
Scrum Process For Offshore TeamScrum Process For Offshore Team
Scrum Process For Offshore Team
 
Agile Methodologies
Agile MethodologiesAgile Methodologies
Agile Methodologies
 
Agile Adoption - What's the Payoff?
Agile Adoption - What's the Payoff? Agile Adoption - What's the Payoff?
Agile Adoption - What's the Payoff?
 

Más de Dashlane

Dashlane Engineering Culture Book
Dashlane Engineering Culture BookDashlane Engineering Culture Book
Dashlane Engineering Culture BookDashlane
 
The State of Digital Identity
The State of Digital IdentityThe State of Digital Identity
The State of Digital IdentityDashlane
 
Continuous Learning
Continuous LearningContinuous Learning
Continuous LearningDashlane
 
U2F in Dashlane
U2F in DashlaneU2F in Dashlane
U2F in DashlaneDashlane
 
Using TypeScript at Dashlane
Using TypeScript at DashlaneUsing TypeScript at Dashlane
Using TypeScript at DashlaneDashlane
 
Scaling an Engineering Team
Scaling an Engineering TeamScaling an Engineering Team
Scaling an Engineering TeamDashlane
 
Stop Starting Start Finishing
Stop Starting Start FinishingStop Starting Start Finishing
Stop Starting Start FinishingDashlane
 
Dashlane Engineering Meeting Extract
Dashlane Engineering Meeting ExtractDashlane Engineering Meeting Extract
Dashlane Engineering Meeting ExtractDashlane
 

Más de Dashlane (8)

Dashlane Engineering Culture Book
Dashlane Engineering Culture BookDashlane Engineering Culture Book
Dashlane Engineering Culture Book
 
The State of Digital Identity
The State of Digital IdentityThe State of Digital Identity
The State of Digital Identity
 
Continuous Learning
Continuous LearningContinuous Learning
Continuous Learning
 
U2F in Dashlane
U2F in DashlaneU2F in Dashlane
U2F in Dashlane
 
Using TypeScript at Dashlane
Using TypeScript at DashlaneUsing TypeScript at Dashlane
Using TypeScript at Dashlane
 
Scaling an Engineering Team
Scaling an Engineering TeamScaling an Engineering Team
Scaling an Engineering Team
 
Stop Starting Start Finishing
Stop Starting Start FinishingStop Starting Start Finishing
Stop Starting Start Finishing
 
Dashlane Engineering Meeting Extract
Dashlane Engineering Meeting ExtractDashlane Engineering Meeting Extract
Dashlane Engineering Meeting Extract
 

Último

Boost Efficiency: Sabre API Integration Made Easy
Boost Efficiency: Sabre API Integration Made EasyBoost Efficiency: Sabre API Integration Made Easy
Boost Efficiency: Sabre API Integration Made Easymichealwillson701
 
renewable energy renewable energy renewable energy renewable energy
renewable energy renewable energy renewable energy  renewable energyrenewable energy renewable energy renewable energy  renewable energy
renewable energy renewable energy renewable energy renewable energyjeyasrig
 
Technical improvements. Reasons. Methods. Estimations. CJ
Technical improvements.  Reasons. Methods. Estimations. CJTechnical improvements.  Reasons. Methods. Estimations. CJ
Technical improvements. Reasons. Methods. Estimations. CJpolinaucc
 
Leveling Up your Branding and Mastering MERN: Fullstack WebDev
Leveling Up your Branding and Mastering MERN: Fullstack WebDevLeveling Up your Branding and Mastering MERN: Fullstack WebDev
Leveling Up your Branding and Mastering MERN: Fullstack WebDevpmgdscunsri
 
MUT4SLX: Extensions for Mutation Testing of Stateflow Models
MUT4SLX: Extensions for Mutation Testing of Stateflow ModelsMUT4SLX: Extensions for Mutation Testing of Stateflow Models
MUT4SLX: Extensions for Mutation Testing of Stateflow ModelsUniversity of Antwerp
 
Enterprise Content Managements Solutions
Enterprise Content Managements SolutionsEnterprise Content Managements Solutions
Enterprise Content Managements SolutionsIQBG inc
 
8 Steps to Build a LangChain RAG Chatbot.
8 Steps to Build a LangChain RAG Chatbot.8 Steps to Build a LangChain RAG Chatbot.
8 Steps to Build a LangChain RAG Chatbot.Ritesh Kanjee
 
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...Maxim Salnikov
 
MinionLabs_Mr. Gokul Srinivas_Young Entrepreneur
MinionLabs_Mr. Gokul Srinivas_Young EntrepreneurMinionLabs_Mr. Gokul Srinivas_Young Entrepreneur
MinionLabs_Mr. Gokul Srinivas_Young EntrepreneurPriyadarshini T
 
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...Splashtop Inc
 
Mobile App Development process | Expert Tips
Mobile App Development process | Expert TipsMobile App Development process | Expert Tips
Mobile App Development process | Expert Tipsmichealwillson701
 
Building Generative AI-infused apps: what's possible and how to start
Building Generative AI-infused apps: what's possible and how to startBuilding Generative AI-infused apps: what's possible and how to start
Building Generative AI-infused apps: what's possible and how to startMaxim Salnikov
 
Einstein Copilot Conversational AI for your CRM.pdf
Einstein Copilot Conversational AI for your CRM.pdfEinstein Copilot Conversational AI for your CRM.pdf
Einstein Copilot Conversational AI for your CRM.pdfCloudMetic
 
Revolutionize Your Field Service Management with FSM Grid
Revolutionize Your Field Service Management with FSM GridRevolutionize Your Field Service Management with FSM Grid
Revolutionize Your Field Service Management with FSM GridMathew Thomas
 
Practical Advice for FDA’s 510(k) Requirements.pdf
Practical Advice for FDA’s 510(k) Requirements.pdfPractical Advice for FDA’s 510(k) Requirements.pdf
Practical Advice for FDA’s 510(k) Requirements.pdfICS
 
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...telebusocialmarketin
 
User Experience Designer | Kaylee Miller Resume
User Experience Designer | Kaylee Miller ResumeUser Experience Designer | Kaylee Miller Resume
User Experience Designer | Kaylee Miller ResumeKaylee Miller
 
Large Scale Architecture -- The Unreasonable Effectiveness of Simplicity
Large Scale Architecture -- The Unreasonable Effectiveness of SimplicityLarge Scale Architecture -- The Unreasonable Effectiveness of Simplicity
Large Scale Architecture -- The Unreasonable Effectiveness of SimplicityRandy Shoup
 
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdf
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdfFlutter the Future of Mobile App Development - 5 Crucial Reasons.pdf
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdfMind IT Systems
 

Último (20)

Boost Efficiency: Sabre API Integration Made Easy
Boost Efficiency: Sabre API Integration Made EasyBoost Efficiency: Sabre API Integration Made Easy
Boost Efficiency: Sabre API Integration Made Easy
 
renewable energy renewable energy renewable energy renewable energy
renewable energy renewable energy renewable energy  renewable energyrenewable energy renewable energy renewable energy  renewable energy
renewable energy renewable energy renewable energy renewable energy
 
Technical improvements. Reasons. Methods. Estimations. CJ
Technical improvements.  Reasons. Methods. Estimations. CJTechnical improvements.  Reasons. Methods. Estimations. CJ
Technical improvements. Reasons. Methods. Estimations. CJ
 
Leveling Up your Branding and Mastering MERN: Fullstack WebDev
Leveling Up your Branding and Mastering MERN: Fullstack WebDevLeveling Up your Branding and Mastering MERN: Fullstack WebDev
Leveling Up your Branding and Mastering MERN: Fullstack WebDev
 
MUT4SLX: Extensions for Mutation Testing of Stateflow Models
MUT4SLX: Extensions for Mutation Testing of Stateflow ModelsMUT4SLX: Extensions for Mutation Testing of Stateflow Models
MUT4SLX: Extensions for Mutation Testing of Stateflow Models
 
Enterprise Content Managements Solutions
Enterprise Content Managements SolutionsEnterprise Content Managements Solutions
Enterprise Content Managements Solutions
 
8 Steps to Build a LangChain RAG Chatbot.
8 Steps to Build a LangChain RAG Chatbot.8 Steps to Build a LangChain RAG Chatbot.
8 Steps to Build a LangChain RAG Chatbot.
 
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...
If your code could speak, what would it tell you? Let GitHub Copilot Chat hel...
 
MinionLabs_Mr. Gokul Srinivas_Young Entrepreneur
MinionLabs_Mr. Gokul Srinivas_Young EntrepreneurMinionLabs_Mr. Gokul Srinivas_Young Entrepreneur
MinionLabs_Mr. Gokul Srinivas_Young Entrepreneur
 
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...
Splashtop Enterprise Brochure - Remote Computer Access and Remote Support Sof...
 
Mobile App Development process | Expert Tips
Mobile App Development process | Expert TipsMobile App Development process | Expert Tips
Mobile App Development process | Expert Tips
 
Building Generative AI-infused apps: what's possible and how to start
Building Generative AI-infused apps: what's possible and how to startBuilding Generative AI-infused apps: what's possible and how to start
Building Generative AI-infused apps: what's possible and how to start
 
20140812 - OBD2 Solution
20140812 - OBD2 Solution20140812 - OBD2 Solution
20140812 - OBD2 Solution
 
Einstein Copilot Conversational AI for your CRM.pdf
Einstein Copilot Conversational AI for your CRM.pdfEinstein Copilot Conversational AI for your CRM.pdf
Einstein Copilot Conversational AI for your CRM.pdf
 
Revolutionize Your Field Service Management with FSM Grid
Revolutionize Your Field Service Management with FSM GridRevolutionize Your Field Service Management with FSM Grid
Revolutionize Your Field Service Management with FSM Grid
 
Practical Advice for FDA’s 510(k) Requirements.pdf
Practical Advice for FDA’s 510(k) Requirements.pdfPractical Advice for FDA’s 510(k) Requirements.pdf
Practical Advice for FDA’s 510(k) Requirements.pdf
 
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...
Telebu Social -Whatsapp Business API : Mastering Omnichannel Business Communi...
 
User Experience Designer | Kaylee Miller Resume
User Experience Designer | Kaylee Miller ResumeUser Experience Designer | Kaylee Miller Resume
User Experience Designer | Kaylee Miller Resume
 
Large Scale Architecture -- The Unreasonable Effectiveness of Simplicity
Large Scale Architecture -- The Unreasonable Effectiveness of SimplicityLarge Scale Architecture -- The Unreasonable Effectiveness of Simplicity
Large Scale Architecture -- The Unreasonable Effectiveness of Simplicity
 
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdf
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdfFlutter the Future of Mobile App Development - 5 Crucial Reasons.pdf
Flutter the Future of Mobile App Development - 5 Crucial Reasons.pdf
 

The Dashlane Agile Journey

  • 1. An Agile Journey How we evolved our Agile organization from a Feature Factory to Business Teams driven by OKR
  • 2. My name is Frédéric Rivain, CTO of Dashlane. We build a Password Manager, to help you manage your identity and your payments in a simple and secure way everywhere.
  • 3. A bit of context Funded in 2009 by Bernard Liautaud and 3 Centrale students 110 employees in Paris and New York • Product & Engineering in Paris • Marketing & Sales in New York 4 business lines: • Consumer product (B2C) • Enterprise offer (B2B) • Financial Partners • API and Dev Ecosystem • 7 “production” teams
  • 4. Agile timeline • Iterative evolution. • Learning as we grow. • Adapt to our needs and scale. • Various states of maturity. Garage Mode 2014 Move to Agile. Scrum by the Book. Roadmap & Portfolio 2015 OKR Feature Teams 2016 2017
  • 5. Half-Baked Agility* Operations Tactics Strategy Culture Agile Development Scrum, Kaban… Lean Goals / OKR 1 2 3 4 * As quoted from Felipe Castro
  • 7. 1. Agile methodology at the team operational level • We started from Scrum. A lot by the book. • Today we evolved into more of a Scrumban mode in many teams. • Key shared principles between all teams: • 2-week cadence for all teams • 3 clearly identified roles • Product Owner • Scrum Master (possibly rotating among team members) • Business Stakeholders • Regular stand-ups • Review at the end of each cycle, with team + stakeholders + everybody interested
  • 8. 2. Tactics • Scrum is about operational agility. A methodology for day-to-day organization. • Wrap the Scrum cycle with a Lean process, to improve Alignement and Visibility at Company level. Formalize the Project Collaborative Specifications Development Validation Release to Production Assess results Evaluate and prioritize AGILE PRODUCTION Stakeholder Lean overall approach Agile production cycle
  • 9. 2. Roadmap & Portfolio • Introducing 2 tools, inspired from SAFe framework, influenced by Lean approach • A portfolio = a high-level view of all our projects at Dashlane. Live board in Jira. At any point in time, you can know everything that is being worked on by the teams. • A quarterly Roadmap = a view by team, by quarter, by objective. Linked dynamically to the Portfolio. Provides vision, consistency and alignement.
  • 10. 2. The perfect Feature Factory • Build Project-driven roadmaps • Track feature delivery • Only Agile at the Operations level and partially at the Tactics level. • Strategy is based on annual goals with overall top-down planning.
  • 11. 3. Strategy • How to build an Agile Strategy? • How do we move to Full-Stack Agility? • Move away from waterfall / top-down goals. • Introducing OKR… Operations Tactics Strategy Culture Agile Development Scrum, Kaban… Lean Goals / OKR 1 2 3 4
  • 12. 3. OKR – Objective & Key Results • A framework of defining and tracking objectives and their outcomes • Created by Intel, in the 1970s • Made popular by John Doerr and Google • Adopted by most Silicon Valley companies
  • 13. 3. OKR Components • O = Objective: • Aspirational. • Memorable – Simpler, shorter, remarkable. • Qualitative. • KR = Key Results: • 2-5 per Objective. • Quantitative & Measurable. • Metrics (recommended) or Milestones.
  • 14. OKR Example • Objective: Delight our customers • Key Results: • Increase average weekly visits from 3.1 to 3.3 per active user • Improve Net Promoter Score from 46% to 52%. • Increase non paid (organic) traffic from 70% to 80%. • Increase engagement (users that complete a full profile) from 60% to 75%. • Objective: Taming the Autofill Dragon • Key Results: • Achieve successful autologin on the top 50 Chinese websites • Achieve successful autologin on the top 50 Korean websites O can be fun!
  • 15. 3. Dashlane OKR • Yearly Company OKR – High-Level Strategy • KR can be reviewed and adapted every quarter or as needed. • But O should theoretically remain stable in time • Team Quarterly OKR – Tactical Short Term • Impacting Company OKR • No individual OKR, by choice.
  • 16. 3. The move to OKR • It is hard, for everybody but especially for engineering. • Big change of mindset: • Focus on business impact and value first • Projects come second. • In theory, delivering a feature does not really count for success. • Need to be very data-driven. • Need to accelerate massively the cycle time and release process. • Need experimentation tooling such as strong A/B Test Engine and Feature-Flipping. • Need to shift to a more bottom-up process (~60% bottom-up, ~40% top-down).
  • 17. 3. Our first Fails • Too many OKRs per team. • Way way too ambitious. Aim for roofshots, not moonshots. • Team not capable of measuring a KR. • We should decide faster in a Quarter to drop a KR. • Bottom-up is hard also for the teams. • Several quarterly cycles before it starts becoming easier. • Need to manage the feeling that OKR are bullshit.
  • 18. 3. Link between OKR & Roadmap • We still have projects and features. • But they are mostly defined to achieve goals as set by OKR. • Not all projects are associated to OKR. Quarterly OKR  Quarterly Roadmap
  • 19. 3. Slice the Elephant • With OKR, it is even clearer that you need to split big projects. • Ship fast, Experiment, iterate. MVP / Skateboard approach. • For big projects, adapt KR to be more technical KR or learning KR.
  • 20. 3. Our OKR-Roadmap process today • One month before beginning of the quarter, the Lead Stakeholder & Product Owner kick off the OKR & Roadmap process: • Get input from the team • Get input from the stakeholder(s) • Get input from the exec team • Agree on the MUST HAVE of the quarter so that specs can be ready from D1 of the quarter. • PO & Lead Stakeholder prepare high level guidelines that are validated by exec team • Last 2 weeks of the previous quarter are dedicated to OKR & Roadmap definition for each team: • PO needs to provision some sprint time to allow the teams to focus on the process • Drafting is documented on Confluence to allow iteration / back & forth with stakeholders etc. • OKR are ready at the end of the 2 weeks: • Both O & KR properly worded • Metrics baseline & target are agreed upon • Tracking & reporting enabled • Mapping with Company OKR done • Feedback from stakeholders has been taken into account • Roadmap at the end of the 2 weeks: • all teams prepare a confluence page summarizing their OKR and the related portfolio projects for the quarter • Exec team meets and goes over each team's OKR/Roadmap page to challenge teams and sign off on the Quarter's program • During the Quarter teams report on their OKR in a standardized way at each sprint review
  • 21. 3. OKR learnings • Don’t be too ambitious, else teams get frustrated with unreachable goals. Roofshots rather than Moonshots. • Have fewer O and KR rather than too many. Otherwise you loose focus. • Not all projects/initiatives are related to OKR. • Allow for different types of KR: • Learning metrics • Business metrics • Possibly technical metrics • Time those KR based on the current progress and based on the outcome you are looking for. Learning first before optimizing and impacting business for instance.
  • 23. Legacy Platform Teams • Originally, platform teams: • Desktop, iOs, Android, Web Product, Server, Semantic Engine • Works well for small teams. With one line of business. • Starts hurting as you grow the team and as you diversify: • Synchronization issues between platforms • Inconsistency in product • Technical focus > Business focus
  • 24. Moving to Business/Feature Teams • Inspired by the Feature Teams model (a la Spotify) • Applied to the Dashlane context • Cross-functional teams including: • Product, Development, QA + Design, Analytics, Product Marketing, User Support • « Mini Startup » inside the company, with end-to-end responsibility on their business scope. Associated closely to business stakeholders. • 7 teams including • 3 focused on end-user: Acquisition, Conversion, Retention • 2 focused on B2B • 1 for Partnerships • 1 to make use of our semantic engine
  • 25. Managing change • Work closely with all team members to define the target, when and how • Do it when you have enough of each skill to make it sustainable. • We decided for a Big-Bang switch between 2 quarters. 1 full week dedicated to the switch. • Take your time to prepare. • Use the opportunity for team building, training. • Communicate, communicate, communicate… • Listen, listen, listen…
  • 26. Side impacts • Thinking Platforms + Teams • Manage platform organization: • Need more communication • Organizing tech work in « Platform Days » • Adaptations to the Release Process and the way all teams coordinate. • New management style for Tech Leads, with engineers distributed in various teams. • Changing the way we think about resource allocation and roadmap definition.
  • 27. Mobility, Flexibility and Taskforces • Mobility: allow for developers to change teams from time to time. • Flexibility: adapt resource allocation based on needs. • Taskforces: • Some projects don’t fit in a team. • Plan it from the start as part of the process. • Create short-lived taskforces with a clear project goal.
  • 28. Then what ? • The easy part is the switch. Fun and exciting time. • The hard part follows: making it work. • Changing our way of working to optimize the new organization. • Be patient. It takes time. • Inspect and adapt.
  • 30. Tuning time • We are still learning as we do. • Tuning OKR to make them more efficient. • Identifying friction points. • Overcoming obstacles • Improving the foundations that support our organization • Data: stronger and more real-time analytics • Product: adapting the way we design product • Technical: strengthening and accelerating our release pipeline. Industrializing and automating.
  • 31. Future experiments • Nothing planned yet, but interested in looking into: • Design Sprint • Holacracy and other different types of organizations
  • 32. Final Words of Advice
  • 33. Tips and Tricks • Invest time to get support from both the Top and the Bottom: from Execs to Team members. Convince before doing. • Each change is hard as it is. You need everybody to be on board. • There are strong prerequisites to all these evolutions • Data: strong analytics • Product: each change has an impact in the way you design product • Technical: having a smooth and fast release pipeline is key • Culture: be ready for change. • Learn as you go and adapt to your company maturity. • Adapt to your own context.
  • 35. References • OKR • http://felipecastro.com/en/okr/what-is-okr/ • https://www.slideshare.net/meetfelipe/slides-agile2016-stop-using-agile-with-waterfall- goals-goal-agility-with-okr • https://medium.com/the-alignment-shop/the-okr-journey-a-guide-for-okr-adoption- beb775ca2a5a • Feature Teams • https://www.slideshare.net/JoakimSunden/agile-at-spotify • https://www.slideshare.net/ashlychrstn/full-stackagile-squads-chapters-tribes-and- guilds • https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
  • 36. Thank you © 2017 Dashlane, Inc