Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
×
1 of 45

More Related Content

You Might Also Like

Related Books

Free with a 30 day trial from Scribd

See all

After the Pandemic: Rethinking Developer Productivity (There’s more to it than you think)

  1. 1. After the Pandemic: Rethinking Developer Productivity (There’s more to it than you think) Margaret-Anne Storey May 18th , 2021 @margaretstorey mstorey@uvic.ca
  2. 2. https://www.thepeoplespace.com/ideas/articl es/what-work-short-history @margaretstorey 2
  3. 3. From work from home, to work as a “place” and “time” @margaretstorey 3
  4. 4. Work was shaped by social and cultural expectations even before the modern office existed https://www.bbc.com/worklife/article/20170818-the-ancient-roots-of-the-modern-office @margaretstorey 4
  5. 5. https://www.theatlantic.com/t echnology/archive/2015/12/w hat-telecommuting-looked-lik e-in-1973/418473/ @margaretstorey 5
  6. 6. Work from home studies (pre pandemic) Bloom’s 2014 study of travel call center employees in China: - 13% increase in performance (perhaps due to quieter environment) - Increased work satisfaction, fewer breaks and sick days Bloom, Nicholas, James Liang, John Roberts, and Zhichun Jenny Ying. “Does Working from Home Work? Evidence from a Chinese Experiment*.” The Quarterly Journal of Economics 130, no. 1 (February 1, 2015): 165–218. @margaretstorey 6
  7. 7. But what is developer productivity? 7
  8. 8. 8 “Accidental vs. Essential Complexity” Brooks @margaretstorey
  9. 9. 2020 2010 2000 1990 1980 1970 1968 Importance of tools in software engineering @margaretstorey 9
  10. 10. Developer “workspaces”, where proximity increases interactions, facilitates leadership and enables collaboration and communication @margaretstorey 10
  11. 11. @margaretstorey 11
  12. 12. What factors influence developer productivity and satisfaction? Storey MA, Zimmermann T, Bird C, Czerwonka J, Murphy B, Kalliamvakou E. Towards a theory of software developer job satisfaction and perceived productivity. IEEE Transactions on Software Engineering. 2019. @margaretstorey 12
  13. 13. @margaretstorey 13
  14. 14. @margaretstorey 14
  15. 15. Engineering system Hardware Engineering processes Collaboration tools Engineering tools Work environment Physical environment Interruptions # people in workspace Private office Impactful work Learning skills for future Work vision Work type Can achieve goals Impact of work Work culture Manager Autonomy Team culture Collaborative team Organization culture Important contributor Skills are well used Important team member After hierarchical clustering… @margaretstorey 15
  16. 16. Linear regression models with standardized coefficients show how different factors influence overall job satisfaction @margaretstorey 16
  17. 17. Linear regression models with standardized coefficients show how different factors influence perceived productivity @margaretstorey 17
  18. 18. @margaretstorey 18
  19. 19. Developer Satisfaction Perceived Productivity Impactful work Important contributor Appreciation Work culture Work-life balance Autonomy Can complete tasks Engineering system Technical skills Work environment Developer satisfaction and productivity theory Storey MA, Zimmermann T, Bird C, Czerwonka J, Murphy B, Kalliamvakou E. Towards a theory of software developer job satisfaction and perceived productivity. IEEE Transactions on Software Engineering. 2019 Sep 27. @margaretstorey 19
  20. 20. WFH impact on developer productivity? @margaretstorey 20
  21. 21. Working from Home: A Tale of Two Cities “We’re doing very well, we’re barely hanging in there.” — Shane O’Flynn Ford D, Storey MA, Zimmermann T, Bird C, Jaffe S, Maddila C, Butler JL, Houck B, Nagappan N. A tale of two cities: Software developers working from home during the covid-19 pandemic. arXiv preprint arXiv:2008.11147. 2020 Aug. @margaretstorey 21
  22. 22. Working from Home: A Tale of Two Cities March 2020 May 2020 “We’re doing very well, we’re barely hanging in there.” — Shane O’Flynn @margaretstorey 22
  23. 23. Working from Home: A Tale of Two Cities Less distraction from others, especially coming from an open office scenario. Teams meetings for some meetings where very little participation is required lets you continue to work while “attending” and listening in, which is better than being idle in a conference room. Interruptions and concentration as I can [only] be reached on Teams and by email vs someone walking over for a question. Harder to keep tabs on direct reports. Dichotomous variables: focus time, work-life balance, childcare needs... @margaretstorey 23
  24. 24. Working from Home: A Tale of Two Cities @margaretstorey 24
  25. 25. Team productivity during work from home I think we spend a lot more time trying to coordinate with each other and driving for clarity and shared understanding is harder. This means more time solidifying what we need to be doing and less time doing/building it. Miller C, Rodeghero P, Storey MA, Ford D, Zimmermann T. " How Was Your Weekend?" Software Development Teams Working From Home During COVID-19. To appear, ICSE 2021. @margaretstorey 25
  26. 26. 26
  27. 27. Productivity: there’s more to it than you think Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler. The SPACE of Developer Productivity, ACM Queue 19, 1, January-February 2021. @margaretstorey 27
  28. 28. S – Satisfaction & Well-Being P – Performance A – Activity C – Collaboration & Communication E – Efficiency & Flow @margaretstorey 28
  29. 29. Bao, Lingfeng, Tao Li, Xin Xia, Kaiyu Zhu, Hui Li, and Xiaohu Yang. “How Does Working from Home Affect Developer Productivity? -- A Case Study of Baidu During COVID-19 Pandemic.” March 25, 2021. http://arxiv.org/abs/2005.13167. Butler, Jenna, and Sonia Jaffe. “Challenges and Gratitude: A Diary Study of Software Engineers Working From Home During Covid-19 Pandemic.” In 2021 IEEE/ACM 43rd International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP), 362–63. Madrid, Spain: IEEE, 2021. https://doi.org/10.1109/ICSE-SEIP52600.2021.00047. Camara, Rafael da, Marcelo Marinho, Suzana Sampaio, and Saulo Cadete. “How Do Agile Software Startups Deal with Uncertainties by Covid-19 Pandemic?” International Journal of Software Engineering & Applications 11, no. 4 (July 31, 2020): 15–34. https://doi.org/10.5121/ijsea.2020.11402. Ford, Denae, Margaret-Anne Storey, Thomas Zimmermann, Christian Bird, Sonia Jaffe, Chandra Maddila, Jenna L. Butler, Brian Houck, and Nachiappan Nagappan. “A Tale of Two Cities: Software Developers Working from Home During the COVID-19 Pandemic.” ArXiv:2008.11147 [Cs], August 25, 2020. http://arxiv.org/abs/2008.11147. Machado, Leticia S., Clara Caldeira, Marcelo Gattermann Perin, and Cleidson R.B. de Souza. “Gendered Experiences of Software Engineers During the COVID-19 Crisis.” IEEE Software 38, no. 2 (March 2021): 38–44. https://doi.org/10.1109/MS.2020.3040135. Miller, Courtney, Paige Rodeghero, Margaret-Anne Storey, Denae Ford, and Thomas Zimmermann. “‘How Was Your Weekend?’ Software Development Teams Working From Home During COVID-19.” ArXiv:2101.05877 [Cs], February 11, 2021. http://arxiv.org/abs/2101.05877. Neto, Paulo Anselmo da Mota Silveira, Umme Ayda Mannan, Eduardo Santana de Almeida, Nachiappan Nagappan, David Lo, Pavneet Singh Kochhar, Cuiyun Gao, and Iftekhar Ahmed. “A Deep Dive on the Impact of COVID-19 in Software Development.” ArXiv:2008.07048 [Cs], August 16, 2020. http://arxiv.org/abs/2008.07048. Forsgren, Nicole, The GitHub Blog. “Octoverse Spotlight: An Analysis of Developer Productivity, Work Cadence, and Collaboration in the Early Days of COVID-19,” May 6, 2020. https://github.blog/2020-05-06-octoverse-spotlight-an-analysis-of-developer-productivity-work-cadence-and-collaboration-in-the-early-days-of-covid-19/. Ralph, Paul, Sebastian Baltes, Gianisa Adisaputri, Richard Torkar, Vladimir Kovalenko, Marcos Kalinowski, Nicole Novielli, et al. “Pandemic Programming.” Empirical Software Engineering 25, no. 6 (November 1, 2020): 4927–61. https://doi.org/10.1007/s10664-020-09875-y. Rodeghero, Paige, Thomas Zimmermann, Brian Houck, and Denae Ford. “Please Turn Your Cameras On: Remote Onboarding of Software Developers during a Pandemic.” ArXiv:2011.08130 [Cs], March 6, 2021. http://arxiv.org/abs/2011.08130. Russo, Daniel, Paul H P Hanel, Seraphina Altnickel, and Niels van Berkel. “Predictors of Well-Being and Productivity of Software Professionals during the COVID-19 Pandemic – A Longitudinal Study,” Russo, Daniel, Paul H. P. Hanel, Seraphina Altnickel, and Niels van Berkel. “The Daily Life of Software Engineers during the COVID-19 Pandemic.” In 2021 IEEE/ACM 43rd International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP), 364–73. Madrid, Spain: IEEE, 2021. https://doi.org/10.1109/ICSE-SEIP52600.2021.00048. Schrage, Zacharias. “How Can Software Development Teams Be Controlled During the COVID-19 Pandemic.” In Digital Responses to Covid-19: Digital Innovation, Transformation, and Entrepreneurship During Pandemic Outbreaks, 87–103. SpringerBriefs in Information Systems. Cham: Springer International Publishing, 2021. https://doi.org/10.1007/978-3-030-66611-8_7. Smite, Darja. “From Force WFH to WFA - Darja Smite et al Under Review Wang, Yun, Ying Liu, Weiwei Cui, John Tang, Haidong Zhang, Doug Walston, and Dongmei Zhang. “Returning to the Office During the COVID-19 Pandemic Recovery: Early Indicators from China.” In Extended Abstracts of the 2021 CHI Conference on Human Factors in Computing Systems, 1–6. Yokohama Japan: ACM, 2021. https://doi.org/10.1145/3411763.3451685. Yang, Longqi, Sonia Jaffe, David Holtz, Siddharth Suri, Shilpi Sinha, Jeffrey Weston, Connor Joyce, et al. “How Work From Home Affects Collaboration: A Large-Scale Study of Information Workers in a Natural Experiment During COVID-19.” ArXiv:2007.15584 [Cs], July 30, 2020. http://arxiv.org/abs/2007.15584. Applying SPACE to developer WFH studies! 29
  30. 30. Satisfaction Performance Activity Collaboration/Communication Efficiency and Flow Work life balance [Bao, Ford, Neto, Russo, Smite, Yang] More free time [Ford, Smite] Fewer bugs [Camara, Miller, Neto] Bug fixing time ↓ [Camara, Russo] Communication friction [Ford, Butler, Smite, Machado, Miller] Better/more use of Communication tools* [Camara, Wang] Distractions ↑ [Butler, Ford, Russo] Focus time ↑ [Butler, Ford, Russo, Smite, Yang] Physical health [Ford, Smite] Healthier food/ activity [Ford] LOC ↑ [Smite] Collaboration ↓ [Miller, Yang] Open source collaboration ↑ [Forsgren] Work interruptions ↑ [Ford] More hours [Forsgren, Smite] Flexible hours [Butler, Ford, Smite] Commits (↑) [Bao, Forsgren, Neto, Yang] Team cohesion ↓ [Miller, Smite] Benefits for global distrib. teams [Smite, Wang] Family interruptions ↑ [Butler, Ford, Machado] Childcare* [Bao, Ford, Neto] Family closer [Ford] Merges (↑) [ Forsgren, Smite] Social connections ↓ [Ford, Miller] New social activities ↑ [Butler, Camara, Smite] Impactful work ↓ [Miller] Impactful work↑ [Miller] More time on docs/specs/testing [Russo] # Messages ↑ [Miller, Yang] # Emails ↓ [Russo] Ergonomics* [Ford, Ralph, Russo, Smite] More money [Ford] Same activities as WFH [Russo] # Meetings ↑/ quality ↓ [Miller, Smite] # Meetings ↓ [Russo. Yang] Loneliness [Russo, Smite] # Meetings ↓ [Russo] Onboarding [Neto, Rodeghero] Knowledge externalization ↑ [Russo, Smite] Burnout [Forsgren, Smite] Awareness ↓ [Ford, Miller] Fewer breaks [Butler, Ford, Russo] Problem solving /Brainstorming ↓ [Ford, Butler, Smite, Machado, Miller] Pairing ↓ [Smite] @margaretstorey 30
  31. 31. Satisfaction Performance Activity Collaboration/Communication Efficiency and Flow Work life balance [Bao, Ford, Neto, Russo, Smite, Yang] More free time [Ford, Smite] Fewer bugs [Camara, Miller, Neto] Bug fixing time ↓ [Camara, Russo] Communication friction [Ford, Butler, Smite, Machado, Miller] Better/more use of Communication tools* [Camara, Wang] Distractions ↑ [Butler, Ford, Russo] Focus time ↑ [Butler, Ford, Russo, Smite, Yang] Physical health [Ford, Smite] Healthier food/ activity [Ford] LOC ↑ [Smite] Collaboration ↓ [Miller, Yang] Open source collaboration ↑ [Forsgren] Work Interruptions ↑ [Ford] More hours [Forsgren, Smite] Flexible hours [Butler, Ford, Smite] Commits (↑) [Bao, Forsgren, Neto, Yang] Team cohesion ↓ [Miller, Smite] Benefits for global distrib. teams [Smite, Wang] Family Interruptions ↑ [Butler, Ford, Machado] Childcare* [Bao, Ford, Neto] Family closer [Ford] More time on docs/specs/testing [Russo] Social connections ↓ [Ford, Miller] New social activities ↑ [Butler, Camara, Smite] Impactful work ↓ [Miller] Impactful work↑ [Miller] Same activities as WFH [Russo] # Messages ↑ [Yang] # Emails ↓ [Russo] Ergonomics* [Ford, Ralph, Russo, Smite] More money [Ford] # Meetings ↓ [Russo] # Meetings ↑/ quality ↓ [Smite] # Meetings ↓ [Russo. Yang] Loneliness [Russo, Smite] Onboarding [Neto, Rodeghero] Knowledge externalization ↑ [Russo, Smite] Burnout [Forsgren, Smite] Awareness ↓ [Ford, Miller] Fewer breaks [Butler, Ford, Russo] Problem solving /Brainstorming ↓ [Ford, Butler, Smite, Machado, Miller] Pairing ↓ [Smite] Many findings from the WFH studies relate to developer satisfaction and well-being @margaretstorey 31
  32. 32. Satisfaction Performance Activity Collaboration/Communication Efficiency and Flow Work life balance [Ford] More free time [Ford, Smite] Fewer bugs [Camara, Miller, Neto] Bug fixing time ↓ [Camara, Russo] Communication friction [Ford, Butler, Smite, Machado, Miller] Better/more use of Communication tools* [Camara, Wang] Distractions ↑ [Butler, Ford, Russo] Focus time ↑ [Butler, Ford, Russo, Smite, Yang] Physical Health [Ford, Smite] Healthier food/ activity [Ford] LOC ↑ [Smite] Collaboration ↓ [Miller, Yang] Open source collaboration ↑ [Forsgren] Work Interruptions ↑ [Ford] More hours [Forsgren, Smite] Flexible hours [Butler, Ford, Smite] Commits (↑) [Bao, Forsgren, Neto, Yang] Team cohesion ↓ [Miller, Smite] Benefits for global distrib. teams [Smite, Wang] Family Interruptions ↑ [Butler, Ford, Machado] Childcare* [Bao, Ford, Neto] Family closer [Ford] Merges (↑) [ Forsgren, Smite] Social connections ↓ [Ford, Miller] New social activities ↑ [Butler, Camara, Smite] Impactful work ↓ [Miller] Impactful work↑ [Miller] More time on docs/specs/testing [Russo] # Messages ↑ [Yang] # Emails ↓ [Russo] Ergonomics* [Ford, Russo, Smite] More money [Ford] Same activities as WFH [Russo] # Meetings ↑/ quality ↓ [Smite] # Meetings ↓ [Russo. Yang] Loneliness [Russo, Smite] # Meetings ↓ [Russo] Onboarding [Neto, Rodeghero] Knowledge externalization ↑ [Russo, Smite] Burnout [Forsgren, Smite] Awareness ↓ [Ford, Miller] Fewer Breaks [Butler, Ford, Russo] Problem solving /Brainstorming ↓ [Ford, Butler, Smite, Machado, Miller] Pairing ↓ [Smite] Not many WFH studies report on performance, a few show stable or increased activities @margaretstorey 32
  33. 33. Satisfaction Performance Activity Collaboration/Communication Efficiency and Flow Work life balance [Ford] More free time [Ford, Smite] Fewer bugs [Camara, Miller, Neto] Bug fixing time ↓ [Camara, Russo] Communication friction [Ford, Butler, Smite, Machado, Miller] Better/more use of Communication tools* [Camara, Wang] Distractions ↑ [Butler, Ford, Russo] Focus time ↑ [Butler, Ford, Russo, Smite, Yang] Physical Health [Ford, Smite] Healthier food/ activity [Ford] LOC ↑ [Smite] Collaboration ↓ [Miller, Yang] Open source collaboration ↑ [Forsgren] Work Interruptions ↑ [Ford] More hours [Forsgren, Smite] Flexible hours [Butler, Ford, Smite] Commits (↑) [Bao, Forsgren, Neto, Yang] Team cohesion ↓ [Miller, Smite] Benefits for global distrib. teams [Smite, Wang] Family Interruptions ↑ [Butler, Ford, Machado] Childcare* [Bao, Ford, Neto] Family closer [Ford] More time on docs/specs/testing [Russo] Social connections ↓ [Ford, Miller] New social activities ↑ [Butler, Camara, Smite] Impactful work ↓ [Miller] Impactful work↑ [Miller] Same activities as WFH [Russo] # Messages ↑ [Yang] # Emails ↓ [Russo] Ergonomics* [Ford, Russo, Smite] More money [Ford] # Meetings ↓ [Russo] # Meetings ↑/ quality ↓ [Smite] # Meetings ↓ [Russo. Yang] Loneliness [Russo, Smite] Onboarding [Neto, Rodeghero] Knowledge externalization ↑ [Russo, Smite] Burnout [Forsgren, Smite] Awareness ↓ [Ford, Miller] Fewer Breaks [Butler, Ford, Russo] Problem solving /Brainstorming ↓ [Ford, Butler, Smite, Machado, Miller] Pairing ↓ [Smite] Many (mixed) findings about collaboration and communication across WFH studies @margaretstorey 33
  34. 34. Satisfaction Performance Activity Collaboration/Communication Efficiency and Flow Work life balance [Ford] More free time [Ford, Smite] Fewer bugs [Camara, Miller, Neto] Bug fixing time ↓ [Camara, Russo] Communication friction [Ford, Butler, Smite, Machado, Miller] Better/more use of Communication tools* [Camara, Wang] Distractions ↑ [Butler, Ford, Russo] Focus time ↑ [Butler, Ford, Russo, Smite, Yang] Physical Health [Ford, Smite] Healthier food/ activity [Ford] LOC ↑ [Smite] Collaboration ↓ [Miller, Yang] Open source collaboration ↑ [Forsgren] Work interruptions ↑ [Ford] More hours [Forsgren, Smite] Flexible hours [Butler, Ford, Smite] Commits (↑) [Bao, Forsgren, Neto, Yang] Team cohesion ↓ [Miller, Smite] Benefits for global distrib. teams [Smite, Wang] Family interruptions ↑ [Butler, Ford, Machado] Childcare* [Bao, Ford, Neto] Family closer [Ford] More time on docs/specs/testing [Russo] Social connections ↓ [Ford, Miller] New social activities ↑ [Butler, Camara, Smite] Impactful work ↓ [Miller] Impactful work↑ [Miller] Same activities as WFH [Russo] # Messages ↑ [Yang] # Emails ↓ [Russo] Ergonomics* [Ford, Russo, Smite] More money [Ford] # Meetings ↓ [Russo] # Meetings ↑/ quality ↓ [Smite] # Meetings ↓ [Russo. Yang] Loneliness [Russo, Smite] Onboarding [Neto, Rodeghero] Knowledge externalization ↑ [Russo, Smite] Burnout [Forsgren, Smite] Awareness ↓ [Ford, Miller] Fewer Breaks [Butler, Ford, Russo] Problem solving /Brainstorming ↓ [Ford, Butler, Smite, Machado, Miller] Pairing ↓ [Smite] Mixed findings about efficiency and flow from the WFH studies (depends on home context and collaboration needs) @margaretstorey 34
  35. 35. @margaretstorey 35
  36. 36. Charting a new course after the pandemic @margaretstorey 36
  37. 37. Future of developer work: why go hybrid? More flexibility with time and place More importance on personal well-being and “purpose” More emphasis on personal health, social and team health Positive changes in office and workspace design, climate Innovative tools and how they are used “I do not think permanent work-from-home will work, but I believe the hybrid working may be an optimal solution for the future. It can provide us much flexibility to leverage benefits from both remote work and office work.” [Wang et al.] @margaretstorey 37
  38. 38. Expect some squalls Confusion about who is remote/at office, when and where Reduced or lower quality collaboration More stress for developers and managers More fragmentation in documentation and communication tools Ineffective knowledge sharing Retention challenges (more remote options) Less cohesive teams 38
  39. 39. Some recommendations from WFH studies Hybrid should be a choice [Ford, Bao, Wang] Pandemic WFH not the same as WFH [Yang], many adapt [Russo] Project characteristics may have an impact [Bao] Seek out interventions to support developer well-being [Butler, Ford, Ralph] Diaries for reflecting on challenges and gratitudes improves well-being, reveals insights [Butler] Take actions to define communication tools and processes [da Camara] Need for more effective drawing tools [Wang, MicrosoftWFH*] Coordinate schedules [Wang] Plan for future pandemics [Russo] "The action of defining a communication tool showed the importance to concentrate all the information exchanged about the projects in one environment, aiming to replace the old exchanges of information in the co-located environment…” [da Camara] * https://www.microsoft.com/en-us/research/uploads/prod/2021/01/NewFutureOfWorkReport.pdf @margaretstorey 39
  40. 40. Use SPACE to define metrics ( >=2 dimensions!) to gain insights into WFX but Metrics are incomplete signals, they neither explain nor recommend changes @margaretstorey 40
  41. 41. Some guiding (and evaluation) theories Self-determination theory [Deci et al.] Autonomy, competence, social-relatedness Two-factor model [Herzberg] Hygiene factors and motivating factors Regulation theory* for developer productivity (tools) Task tracking, coordination, awareness, communication Guidelines from remote companies [GitLab] Proxemic theory, media richness theory [Clark] Control theory [Schrage] *Arciniegas-Mendez, Maryi & Zagalsky, Alexey & Storey, Margaret-Anne & Hadwin, Allyson. Regulation as an Enabler for Collaborative Software Development, CSCW 2015. @margaretstorey 41
  42. 42. Margaret-Anne Storey @margaretstorey mstorey@uvic.ca Takeaway: Consider the full space of developer productivity when we return to work from wherever and however Acknowledgements: Darja Smite, Jacek Czerwonka, Tom Zimmermann, Brendan Murphy, Chris Bird, Eirini Kalliamvakou, Brian Houck, Denae Ford, Courtney Miller, Paige Rodeghero, Nicole Forsgren, Chandra Maddila, Cassandra Petrachenko 42
  43. 43. Backup slides
  44. 44. 44
  45. 45. Activity Async Communication Weekly announcements Engineering Management creates weekly announcement video and slides to be viewed async New team member introduction New team member creates 2-min video introduction, introducing themselves to the team shared in meetings / Slack Backlog refinement / planning poker Team collaborates via a GitLab issue tagging appropriate parties with specific requests. Use Highlights section Capacity planning Team updates a shared Google Sheet monthly Team members who are unable to attend sync meetings Meeting organizers should affix a Google Doc agenda to each meeting invite prior to sending. Team members should update the meeting agenda, prerecord videos Quarterly team results recaps Corporate Marketing creates a Google Doc or Slides for team members to add results async, shares celebration video Project sprints and milestones Growth Marketing uses Geekbot Slack app to poll team members: 1) Which project are you currently focusing on? 2) What went live/was completed since Tuesday? 3) What is this week's top 3 priorities? 4) Do you need help? Broadening coverage during PTO Team members may assign a Channel instead of a Co-worker to cover for them when planning paid time off Weekly team kickoff/standup sessions Geekbot for weekly async standups: 1) How do you feel today? Red/Yellow/Green 2) What did you do this weekend? 3) What are the priorities this week? 4) Anything blocking progress? 5) Any upcoming paid time off? Missed deliverable retrospective Engineering Package Group utilizes async deliverable retrospectives through GitLab issues Blocked calendars/ non-linear workdays Block calendar so that family and friends come first, forcing a non-linear workday and asynchronous comm. Asynch. engineering standup meetings Standup meetings keep all team members appraised of recent work, planned work and if they need help https://about.gitlab.com/company/culture/all-remote/asynchronous/ 45

×