O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Effective team onboarding

390 visualizações

Publicada em

Slides for the talk given in Madrid at the Thoughtworks meetup event with Martin Fowler.

Onboarding is a key part of a team’s success and productivity as well as the new joiners’. However, as technologists we sometimes fail to pay enough attention to it, not having a clear approach to it. In this talk, we share different techniques on how to improve the onboarding process. From effectively sharing the vision to improving the time it takes a new engineer to contribute to the team.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

Effective team onboarding

  1. 1. EFFECTIVE TEAM ONBOARDING Madrid June 2018 María Gómez @mariascandella Jorge Agudo @joragupra
  2. 2. ©ThoughtWorks 2018 Commercial in Confidence Why is onboarding important? 2
  3. 3. ©ThoughtWorks 2018 Commercial in Confidence Three dimensional onboarding process: Goals 3 Being able to effectively contribute to the team fast. Achieve a frictionless and scalable process. Reach business as usual performing mode as soon as possible. INDIVIDUAL TEAM ORGANISATION
  4. 4. 4
  5. 5. As an Individual I want to have enough context So that I can contribute to the team 5
  6. 6. ©ThoughtWorks 2018 Commercial in Confidence “How long is the time gap between starting on the project, and making my first meaningful commit to the code base? [..] the shorter that time gap, the happier I’ve been over the long term as a developer on that project.” Vishal Bardoloi https://bit.ly/2HixcfS Time to first commit 6
  7. 7. ©ThoughtWorks 2018 Commercial in Confidence Time to first commit 7 Environment setup Understand Tech Stack Access to tools Understand my strengths and gaps Understand Business Context
  8. 8. As a Team I want to onboard in an effective way So that I can continue providing value with the least disruption 8
  9. 9. ©ThoughtWorks 2018 Commercial in Confidence Team metrics 9 VELOCITY Completed stories per iteration Work per time CYCLE TIME Amount of time passed working on a story Time per work
  10. 10. ©ThoughtWorks 2018 Commercial in Confidence Onboarding plan ● Start lean ● Get everyone involved ● Get feedback ● Iterate 10 "Plans are useless but planning is indispensable"
  11. 11. ©ThoughtWorks 2018 Commercial in Confidence Pairing 11 SHARE KNOWLEDGE Context Business Tech stack COMMUNICATE Getting to know better Understand how teammates work
  12. 12. ©ThoughtWorks 2018 Commercial in Confidence Architecture Decision Records ● Document design decisions ● Provide context ● Explain rationale ● Describe implications * Lightweight Architecture Decision Records have been in the Tech Radar since Nov 2017 “Today's problems come from yesterday's solutions.” 12
  13. 13. ©ThoughtWorks 2018 Commercial in Confidence “The C4 model is a way to help software development teams describe and communicate software architecture” Simon Brown https://c4model.com/ 13
  14. 14. ©ThoughtWorks 2018 Commercial in Confidence Psychological Safety 14 Can we take risks in this team without feeling insecure or embarrassed?
  15. 15. serendipity /ˌsɛr(ə)nˈdɪpɪti/ noun 1. the occurrence and development of events by chance in a happy or beneficial way. 2. "a fortunate stroke of serendipity" 15
  16. 16. As an Organisation I want to empower teams So that we can learn and define best practices to have a scalable process 16
  17. 17. ©ThoughtWorks 2018 Commercial in Confidence 17 SUPPORT Allow time and resources for teams to improve their onboarding processes Mix up your images to match your content. Mix up your images to match your content. RETROS Mix teams to share their experiences CONNECT Identify processes which work
  18. 18. The Enterprise onboarding plan Don't try to build the greatest company onboarding plan Don't push your plan top-down 18
  19. 19. 19 Thanks! @mariascandella @joragupra See you in XConf!

×