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

The Mechanisms to Improve the Productivity of Large-Scale Development Team

The Mechanisms to Improve the Productivity of Large-Scale Development Team

LINE DEVDAY 2021
PRO

November 11, 2021
Tweet

More Decks by LINE DEVDAY 2021

Other Decks in Technology

Transcript

  1. None
  2. Agenda - About the team. - What are our challenges?

    - Actions to solve issues. - Wrap up.
  3. About the team

  4. KOREA About the team Global branches JAPAN/TOKYO TAIWAN VIETNAM JAPAN/FUKUOKA

  5. About the team LINE Fukuoka - Established at 2013 -

    87 Engineers - About 57 % Overseas Nationality ※ Jan, 2021 Point in time
  6. About the team “Shop” part

  7. About the team History of the “Shop” client team 2021

    iOS: 7ppl Android: 6ppl 2017 iOS: 3ppl Android: 2ppl
  8. About the team Release Train - Release every 2 weeks

    - Cooperate with… - All region’s developers - Planners - Data Scientists - QA members - Service operaters - etc… ““Release Train” in Software Development” Retrieved from https://medium.com/tiket-com/release-train-in-software-development-6794fb1939f1 (Oct. 1, 2021)
  9. What are our challenges?

  10. What are our challenges? - Who to ask for a

    code review? - Implementation differences between iOS and Android have become technical debt. - Outage has increased. - Struggling with new member’s onboarding. - Knowledge is dependent on the individual. - Less documentation. Even if there are some documents, already outdated.
  11. What are our challenges? Negative feedback loop Too busy with

    my day-to-day managerial work to do what I need to do from a medium- to long-term perspective. Outage Need to consider a fundamental solution… A member who don’t know some hidden spec Knowledge is dependent on the individual But too busy to do it later… New member join Less documentation
  12. What are our challenges? Manager as a bottleneck

  13. What are our challenges? “My advice is that you schedule

    in some think time, and hold that think time sacred.” Kim Scott: Radical Candor 2017, 210 p.
  14. What are our challenges? What is keeping me so busy?

    l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  15. What are our challenges? QA Planner A Planner B Other

    dept Planner C Members l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  16. What are our challenges? I needed to solve it, but

    couldn’t get motivated. Why? l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  17. What are our challenges? - Worried about whether the members

    can do well. - Skill concerns. (Not only technical skill but also communication skill and so on.) - Language concerns. (Planners and QA members are mostly Japanese speakers, so worried about English-speaking members.) - Worried about whether members really want to do something in the first place. The reason why I couldn’t get motivated
  18. What are our challenges? - Worried about whether the members

    can do well. - Skill concerns. (Not only technical skill but also communication skill and so on.) - Language concerns. (Planners and QA members are mostly Japanese speakers, so worried about English-speaking members.) - Worried about whether members really want to do something in the first place. The reason why I couldn’t get motivated It would be faster if I did it myself, and no one would complain that way.
  19. What are our challenges? Lost opportunities for members to grow

    l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  20. What are our challenges? Co-worker Review C-Review Supervisor Subordinates Co-workers

    Coworkers Review (C-Review) Supervisor, Co-workers and Subordinates evaluate work performance and attitude. Someone said… “You seem to be reluctant to let your members do their jobs. I wonder whether you trust them?”
  21. What are our challenges? Need to be structured to change

    the system. (Not an ad hoc way) l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  22. Actions to solving issues

  23. Actions to solving issues - Who to ask for a

    code review? - Implementation differences between iOS and Android have become technical debt. - Outage has increased. - Struggling with new member’s onboarding. - Knowledge is dependent on the individual. - Less documentation. Even if there are some documents, already outdated. - Lost opportunities for members to grow. The base issue is “Manager as a bottleneck”
  24. Actions to solving issues Component Lead System

  25. Actions to solving issues Component Lead System etc… Emoji AutoSuggest

    Keyboard Theme Sticker AS-IS: No specific person in charge We have several “Component” in our scope of responsibility
  26. Actions to solving issues Component Lead System TO-BE: Determine the

    Component Lead
  27. Actions to solving issues Component Lead System QA Planner Planner

    Other dept Planner Members QA Planner Planner Other dept Planner Component Leads AS-IS: TO-BE: l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  28. Actions to solving issues Component Lead System QA Planner Planner

    Other dept Planner Members QA Planner Planner Other dept Planner Component Leads AS-IS: TO-BE: 6TFS(SPVQT l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  29. Actions to solving issues Component Lead System Component Leads Code

    reviewer for the P-R of responsible component l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  30. Actions to solving issues Component Lead System Component Leads Code

    reviewer for the P-R of responsible component But if component lead itself created it, who will review it? Component A’s load -> Component B’s load -> Component C’s load -> l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  31. Actions to solving issues Component Lead System Component Leads Sub

    Component Leads Make Sub-Component Lead to distribute the load l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  32. Actions to solving issues Component Lead System e.g. Sticker Component

    has 6 Sub-Components - Login/Sync - Sending/Receiving Logic - Animation/Sound/Popup/Effect Stickers - Custom/Message Stickers - Settings1 - Settings2 l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  33. - Login/Sync - Sending/Receiving Logic - Animation/Sound/Popup/Effect Stickers - Custom/Message

    Stickers - Settings1 - Settings2 Actions to solving issues Component Lead System e.g. Sticker Component has 6 Sub-Components Component Lead Covered all Sub-Components l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  34. Actions to solving issues Component Lead System About code owners

    - GitHub Docs Retrieved from https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners (Oct. 1, 2021)
  35. Actions to solving issues Component Lead System

  36. Actions to solving issues Component Lead System Task Assign Planner

    Component Lead Sub-Component Lead Other member Handle on my own? Development Assign Assign Code Review Code Review Code Review No Yes Development Development l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  37. Actions to solving issues Component Lead System Component Lead :

    0~n • Communication Point of a Component • Decide who to assign development tasks • Code review of all sub-components included by a Component • Manage documentation of all Sub-Components included by a Component Sub-Component Lead : 1~n • Code review • Manage documentation l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  38. Actions to solving issues Component Lead System Component Lead User

    Group Code Owner Ticket Assign Clarification of the contact point Reviewer Assign
  39. Actions to solving issues Component Lead System By built Component

    Lead System to solve Manager as a bottleneck but I still have some concerns… - Worried about whether the members can do well. - Skill concerns. (Not only technical skill but also communication skill and so on.) - Language concerns. (Planner and QA members are mostly Japanese speakers, so the worrying is for English speaker members.) - Don't you want to play such a troublesome role in the first place?
  40. Prior consultation with some members about the idea then gave

    a thorough presentation and explanation to all members. Actions to solving issues Component Lead System
  41. Prior consultation with some members about the idea then gave

    a thorough presentation and explanation to all members. Actions to solving issues Component Lead System Got agreement from members and readily decided the person in charge.
  42. But there are different skill levels and experiences. Actions to

    solving issues Component Lead System I need to coordinate expectation levels between the manager and members. l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  43. Actions to solving issues Component Lead System Delegation Poker “Use

    Delegation Poker to clarify who’s responsible for what and to what level. This is a method where you can encourage employee engagement through controlled self-organization and clarified value and decision-making.” “Delegation Poker & Delegation Board” Retrieved from https://management30.com/practice/delegation-poker/ (Oct. 1, 2021)
  44. Supported by Effective Team and Delivery Dept Actions to solving

    issues Component Lead System - See more details on - https://speakerdeck.com/line_devday2019/project-management-and-agile- strategies-and-examples-of-enterprise-wide-organization - https://www.youtube.com/watch?v=yC2SBf5ITt0 - https://logmi.jp/tech/articles/322286
  45. Actions to solving issues Component Lead System By built Component

    Lead System to solve Manager as a bottleneck but I still have some concerns… - Worried about whether the members can do well. - Skill concerns. (Not only technical skill but also communication skill and so on.) - Language concerns. (Planner and QA members are mostly Japanese speakers, so the worrying is for English speaker members.) - Don't you want to play such a troublesome role in the first place? l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  46. Actions to solving issues Component Lead System Normal development flow

    The flow of a large scale development project ???
  47. The definition of a large scale development project - Involving

    multiple teams such as Server, Client, Frontend, Data science, etc. - Assigning a project manager and proceeding a project few months. Actions to solving issues
  48. The definition of a large scale development project - Involving

    multiple teams such as Server, Client, Frontend, Data science, etc. - Assigning a project manager and proceeding a project few months. Actions to solving issues Project Dev Lead l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  49. - Responsibilities - Communicate with the stakeholders - Manage progress

    and schedule of iOS/ Android dev - Decision making of the client side Actions to solving issues Project Dev Lead QA iOS/Android members Planner Others Manager Observing PM l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  50. Project Review Closing Review Tech Review Actions to solving issues

    Project Dev Lead
  51. - Before designing the system and after kicking off the

    project. When? What? - Share the project overview and expected range of impact with all team members and ask some opinions. Actions to solving issues Project Dev Lead 1. Project Review Why? - To reduce oversights.
  52. - Project Review - Project Dev Lead prepares a project

    doc. - Share the detail of the project. - Discussion about the affecting range among all team members. Actions to solving issues Project Dev Lead All team members Project Doc Specs, Affected Range Discussion l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  53. - Before starting development and after project review. When? What?

    - Share the architecture of the implementation and ask for review. Actions to solving issues Project Dev Lead 2. Tech Review Why? - To eliminate rework and ensure smooth progress in development.
  54. - Tech Review - Project Dev Lead organizes iOS/Android development

    leads (Project dev lead may also be the platform lead). - iOS/Android leads prepare a Design Doc. - iOS/Android leads asks team members to review architectures. Actions to solving issues Project Dev Lead iOS members Review Android members iOS Lead Android Lead Project Dev Lead Organize Design Doc Architectures Review l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  55. Make consensus among Server/iOS/Android - Tech Review - Project Dev

    Lead organizes iOS/Android development leads (Project dev lead may also be the platform lead). - iOS/Android leads prepare a Design Doc. - iOS/Android leads asks team members to review architectures. - Check API usage to avoid diff between iOS/Android. Actions to solving issues Project Dev Lead iOS Lead Project Dev Lead Common Design Doc API usage Android Lead Server Lead l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  56. - Before unassign, after launching the project. When? What? -

    Share the final specification and merge the design doc to the existing spec document. Actions to solving issues Project Dev Lead 3. Closing Review Why? - Ensure the final specification and to keep the documentation clean.
  57. - Closing Review - Project Dev Lead organizes iOS/Android development

    leads (Project dev lead may also be the platform lead). - iOS/Android leads finalizes a Design Doc. Actions to solving issues Project Dev Lead iOS Lead Android Lead Project Dev Lead Organize Design Doc Architectures Finalize the Design Doc l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  58. - Closing Review - Project Dev Lead organizes iOS/Android development

    leads (Project dev lead may also be the platform lead). - iOS/Android leads finalizes a Design Doc. - iOS/Android leads merges the Design Doc to the existing spec document. Actions to solving issues Project Dev Lead Project Dev Lead Merge Spec Doc iOS Lead Android Lead Project Dev Lead Organize Design Doc Architectures l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  59. - Closing Review - Project Dev Lead organizes iOS/Android development

    leads (Project dev lead may also be the platform lead). - iOS/Android leads finalizes a Design Doc. - iOS/Android leads merges the Design Doc to the existing spec document. - iOS/Android leads archives the Design Doc. Actions to solving issues Project Dev Lead Project Dev Lead Merge Spec Doc iOS Lead Android Lead Project Dev Lead Organize Design Doc Architectures l"SDIJWFEzBEEFEPO UIFUPQPGUIFUJUMF 3FNPWFUIF FEJUJOHBVUIPSJUZ l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  60. - Closing Review - Project Dev Lead organizes iOS/Android development

    leads (Project dev lead may also be the platform lead). - iOS/Android leads finalizes a Design Doc. - iOS/Android leads merges the Design Doc to the existing spec document. - iOS/Android leads archives the Design Doc. - Share the final spec to the all members. Actions to solving issues Project Dev Lead iOS Lead Android Lead Project Dev Lead Organize Design Doc Architectures Share the final spec iOS/Android members l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  61. Actions to solving issues - Who to ask for a

    code review? - Implementation differences between iOS and Android have become technical debt. - Outage has increased. - Struggling with new member’s onboarding. - Knowledge is dependent on the individual. - Less documentation. Even if there are some documents, already outdated. - Lost opportunities for members to grow. - Manager as a bottleneck.
  62. Searchability Maintenance Criteria Actions to solving issues About Documentation

  63. - How do we spend less effort finding the right

    place to read/create documentation? Question Issues - We use Confluence as a Wiki service and of course we can search with keywords but it’s often difficult to find what we’re looking for. - Related information is not organized in a systematic way, so we may have to search for documents again and again. Actions to solving issues About documentation - Searchability Searchability Action - Defined the structure of the documentation space for the team. And named it “Internal Docs”.
  64. Actions to solving issues About documentation - Searchability Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page
  65. Actions to solving issues About documentation - Searchability Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page Create the pages when integrate the Component Lead System. (But initially, these are almost empty) l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  66. Actions to solving issues About documentation - Searchability Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page Create a Design Doc before doing any relatively large scale development. And it will be used on a Tech Review. l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  67. Actions to solving issues About documentation - Searchability Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page When a Closing Review, it will be merged onto Main Docs and Sub-Component Docs then archived. Merge l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  68. Actions to solving issues About documentation - Searchability Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page Recommend to use “template" feature of Confluence for creating a new page. Especially, for creating a new set of multiple pages, “custom blue print” feature is useful. Please check it out.
  69. Searchability Portal page (The structure is defined) Maintenance Criteria Actions

    to solving issues About Documentation
  70. Issues - Someone says “Code is everything” - Quality, Granularity

    are depends on an author. Actions to solving issues About documentation - Criteria Criteria Action - Create a template and run it. - The concept of a document is one that allows the reader to build a “mental model” of the functionality it covers.
  71. - What is this feature? - ScreenShots - Related documents

    links - Release history - Terminology - Resources (e.g. Json files, Config files) - Used APIs and its usages - Database design - Debugging tips Actions to solving issues About documentation - Criteria Items of document (Case of Component Main Docs)
  72. - Diagrams - Class diagram - Data flow diagram -

    Sequence diagram (Especially, for the complicated logic) - Class description Actions to solving issues About documentation - Criteria Items of document (Case of Sub-Component Docs)
  73. Searchability Portal page (The structure is defined) Maintenance Criteria A

    reader could make the mental model for the feature Actions to solving issues About Documentation
  74. Issues - Documentation is easily outdated. - Maintenance is costly.

    Actions to solving issues About documentation - Maintenance Maintenance Action - Just make time and do it. - The contents should be maintainable. It should not be detailed. “Twemoji” ©Twitter, Inc and other contributors (Licensed under CC-BY 4.0) https://twemoji.twitter.com/
  75. Common page Common page Android page Android page Android page

    Sub-component Lead Actions to solving issues About documentation - Maintenance Internal Docs structure for each Component iOS page Android page Common page iOS page Android page Common page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Common page Component Lead Sub-component Lead Update the document if needed. Sub-component Lead l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  76. Actions to solving issues About documentation - Maintenance Internal Docs

    structure for each Component iOS page Android page Common page iOS page Android page Common page Common page Common page Android page Android page iOS page iOS page Main Docs iOS Main page Android Main page Common page Design Docs Misc Docs Sub-Component Docs iOS Sub-Component Main page iOS Sub-Component Main page Sub-Component Docs Sub-Component Docs Common page ɾ ɾ ɾ iOS page Android page Common page iOS page Android page Common page Sub-component Lead Component Lead Sub-component Lead Sub-component Lead If busy, create a ticket to register the task. l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  77. Actions to solving issues About documentation - Maintenance Hold the

    “Maintenance Week” When? - Twice a year if possible. How? - Review current document. - Update if need. - Solve the tickets of documentation tasks.
  78. Searchability Portal page (The structure is defined) Criteria A reader

    could make the mental model for the feature Actions to solving issues About Documentation Maintenance Hold the Maintenance week
  79. Actions to solving issues - Who to ask for a

    code review? - Implementation differences between iOS and Android have become technical debt. - Outage has increased. - Struggling with new member’s onboarding. - Knowledge is dependent on the individual. - Less documentation. Even if there are some documents, already outdated. - Lost opportunities for members to grow. - Manager as a bottleneck. l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN
  80. Wrap up

  81. Wrap up Challenges - Who to ask for a code

    review? - Implementation differences between iOS and Android have become technical debt. - Outage has increased. - Struggling with new member’s onboarding. - Knowledge is dependent on the individual. - Less documentation. Even if there are some documents, already outdated. - Lost opportunities for members to grow. - Manager as a bottleneck. Actions - Component Lead System - Empower members - Delegation Poker - Code Owner - Project Dev Lead - Project Review - Tech Review - Closing Review - Design Doc - Documentation - Searchability - Structured portal page - Criteria - Mental model - Maintenance - Maintenance Week
  82. Wrap up Next Actions - Modularize the code to fit

    the Component. - May need a review process for writing the documentation. - Use DocC to manage the documentations (iOS). - Analyzing the situation of the Component Lead system. - Analyze the actual amount of tasks for each Component and Sub-Component, and consider changing assignments according to load conditions, such as increasing or decreasing the number of Sub-Component Leads. In the end, this load balancing will also be systemized.
  83. Wrap up My advice is that you schedule in some

    think time, and hold that think time sacred. “My advice is that you schedule in some think time, and hold that think time sacred.” Kim Scott: Radical Candor 2017, 210 p.
  84. Wrap up It’s still difficult. Because I have to observe

    the each leads and members more than before. But at least, I think I'm not bottleneck anymore.
  85. Thank you