Tweet
Tweet

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Agenda - About the team. - What are our challenges? - Actions to solve issues. - Wrap up.

Slide 3

Slide 3 text

About the team

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

About the team LINE Fukuoka - Established at 2013 - 87 Engineers - About 57 % Overseas Nationality ※ Jan, 2021 Point in time

Slide 6

Slide 6 text

About the team “Shop” part

Slide 7

Slide 7 text

About the team History of the “Shop” client team 2021 iOS: 7ppl Android: 6ppl 2017 iOS: 3ppl Android: 2ppl

Slide 8

Slide 8 text

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)

Slide 9

Slide 9 text

What are our challenges?

Slide 10

Slide 10 text

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.

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

What are our challenges? Manager as a bottleneck

Slide 13

Slide 13 text

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.

Slide 14

Slide 14 text

What are our challenges? What is keeping me so busy? l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN

Slide 15

Slide 15 text

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

Slide 16

Slide 16 text

What are our challenges? I needed to solve it, but couldn’t get motivated. Why? l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

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.

Slide 19

Slide 19 text

What are our challenges? Lost opportunities for members to grow l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN

Slide 20

Slide 20 text

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?”

Slide 21

Slide 21 text

What are our challenges? Need to be structured to change the system. (Not an ad hoc way) l5XFNPKJz˜5XJUUFS *ODBOEPUIFSDPOUSJCVUPST -JDFOTFEVOEFS$$#: IUUQTUXFNPKJUXJUUFSDPN

Slide 22

Slide 22 text

Actions to solving issues

Slide 23

Slide 23 text

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”

Slide 24

Slide 24 text

Actions to solving issues Component Lead System

Slide 25

Slide 25 text

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

Slide 26

Slide 26 text

Actions to solving issues Component Lead System TO-BE: Determine the Component Lead

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

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

Slide 29

Slide 29 text

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

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

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

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

- 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

Slide 34

Slide 34 text

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)

Slide 35

Slide 35 text

Actions to solving issues Component Lead System

Slide 36

Slide 36 text

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

Slide 37

Slide 37 text

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

Slide 38

Slide 38 text

Actions to solving issues Component Lead System Component Lead User Group Code Owner Ticket Assign Clarification of the contact point Reviewer Assign

Slide 39

Slide 39 text

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?

Slide 40

Slide 40 text

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

Slide 41

Slide 41 text

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.

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

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)

Slide 44

Slide 44 text

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

Slide 45

Slide 45 text

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

Slide 46

Slide 46 text

Actions to solving issues Component Lead System Normal development flow The flow of a large scale development project ???

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

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

Slide 49

Slide 49 text

- 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

Slide 50

Slide 50 text

Project Review Closing Review Tech Review Actions to solving issues Project Dev Lead

Slide 51

Slide 51 text

- 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.

Slide 52

Slide 52 text

- 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

Slide 53

Slide 53 text

- 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.

Slide 54

Slide 54 text

- 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

Slide 55

Slide 55 text

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

Slide 56

Slide 56 text

- 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.

Slide 57

Slide 57 text

- 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

Slide 58

Slide 58 text

- 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

Slide 59

Slide 59 text

- 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

Slide 60

Slide 60 text

- 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

Slide 61

Slide 61 text

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.

Slide 62

Slide 62 text

Searchability Maintenance Criteria Actions to solving issues About Documentation

Slide 63

Slide 63 text

- 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”.

Slide 64

Slide 64 text

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

Slide 65

Slide 65 text

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

Slide 66

Slide 66 text

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

Slide 67

Slide 67 text

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

Slide 68

Slide 68 text

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.

Slide 69

Slide 69 text

Searchability Portal page (The structure is defined) Maintenance Criteria Actions to solving issues About Documentation

Slide 70

Slide 70 text

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.

Slide 71

Slide 71 text

- 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)

Slide 72

Slide 72 text

- 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)

Slide 73

Slide 73 text

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

Slide 74

Slide 74 text

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/

Slide 75

Slide 75 text

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

Slide 76

Slide 76 text

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

Slide 77

Slide 77 text

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.

Slide 78

Slide 78 text

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

Slide 79

Slide 79 text

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

Slide 80

Slide 80 text

Wrap up

Slide 81

Slide 81 text

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

Slide 82

Slide 82 text

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.

Slide 83

Slide 83 text

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.

Slide 84

Slide 84 text

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.

Slide 85

Slide 85 text

Thank you