LINE TODAY打造內容入口的服務，內建於LINE程式中，提供使用者即時新聞資訊、體育賽事及娛樂電影資訊，服務的國家包括台灣、泰國、印尼、香港，月活躍用戶超過1800萬。 隨著使用者的需求增加，產品的功能變得越來越多，團隊加入更多的成員進行設計與開發。我們發現團隊的交付時間拉長、無法快速的響應變化、成員間的合作與溝通複雜性上升。 於是我們開始思考，怎麼做可以幫助我們解決這些問題呢？變成一個更好的團隊呢？ 首先，我們跑了三小時的自由組隊工作坊，組成個多個特性團隊。接著，採用大規模敏捷框架「LeSS」，幫助我們對齊開發節奏，以使用者為中心關注整個產品，我們發現做得更少，但成效卻更好！ 如果你對於LINE TODAY的大規模敏捷之路有興趣的朋友，歡迎來聽我的分享。

1. LINE TODAY的大規模敏捷之路
Derek Chen・Nov 2021
The Journey to LINE TODAY Large-Scale Agile

2. WHO AM I
Derek Chen
Scrum Master @LINE TAIWAN

3. Agenda
3
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

4. Agenda
4
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

5. The story starts in 2018
5

6. LINE TODAY
6
Taiwan Thailand Indonesia Hong Kong

7. Background
7
Product Team Process
• 40+ people
• 1 PO team (PO, planners and
designers)
• 3 Dev teams (developers and
testers)
• Multiple product backlogs
• Six-week Sprint
• Small-waterfall (analysis,
development and testing phases)
• Team lead dispatched tasks

8. Monday Tuesday Wednesday Thursday Friday
Sprint Review
Sprint Retrospective
Sprint Review
Sprint Retrospective
Release
Regression Testing
Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Development
Feature Testing
Sprint 1
Development
Feature Testing
Sprint 2
Sprint Pre-Planning Sprint Planning
Planning
Six-week
Sprint
Schedule

9. After one year… 2019
9

10. Challenges with Scale
10
Source: Leading Large Scale Product Development with Large-Scale Scrum (LeSS)

11. Challenges
11
Trust
Stakeholder’s requests take longer to deliver, so
we lost their trust
Priority
Every item is top priority and priorities change
frequently
Complexity
As more members join, it increases the complexity
of communication and cooperation
Adaptation
Long duration of a Sprint slows down responding
to change

12. Goals
12
Increase customer value
One product backlog to determine
priorities
Form feature team
A cross-functional, co-located, long-
lived team. Each team can select
any item from backlog
Reduce waste and lead time
Reduce handoffs and dependencies
Reduce social conflicts
Let teams reform themselves

13. Agenda
13
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

14. Agenda
14
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

15. 15
Self-Designing Team Workshop

16. Trainings
16

17. 17
Forming

18. 18
Reviewing

19. Voting for Scrum Master
• Teams vote for their SM
• One SM serves two teams
19

20. PO Team
Scrum Scrum Scrum Scrum
20
FE
BE
QA
Lead
Lead
Lead
SM SM
Planner
Designer
PO
Lead
UXUI
TE/AE

21. Agenda
21
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

22. 22
LeSS Framework LeSS Principles

23. We adopt LeSS framework
23
https://less.works

24. Two-Week Sprint Schedule
24
Monday Tuesday Wednesday Thursday Friday
Sprint Planning 1
Sprint Review
Sprint Retrospective
Daily Scrum Daily Scrum Daily Scrum Daily Scrum
Daily Scrum Daily Scrum Daily Scrum Daily Scrum
Product Backlog
Refinement
Week 1
Week 2
Sprint Planning 2
Overall Retrospective

25. Cross-team Coordination
25
Align the development pace
Synchronized time box, Sprint Planning,
Daily Scrum, Sprint Review, Sprint
Retrospective.
Hold overall retrospective
Discuss cross-team issues and create
improvement experiments.
Demo together
Developers do demonstrations for
business, product teams and stakeholders.
Send scouts to other teams
The scout observes others and reports back
to his team. Usually, the best time and place
is the Daily Scrum of other teams.

26. Inter-team Coordination
26
Story
Story
Coding
Write test case
Fix Bugs
Run test case
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
QA
Dev
Story
QA
Dev
QA
Dev

27. LeSS Principles
27

28. 28
Source: https://twitter.com/michaeldotjames/status/1259163007969419264
MORE with
LeSS
• Handoffs
• Preparation Sprints
• Stabilization Sprints
• “Dependencies”
• Separate Analysis Groups
• Separate Architects
• Separate Product Backlog

29. Whole Product Focus
29
One Product Backlog
One Product Owner
One Shippable Product
One Sprint

30. Whole Product Focus
30
A Project B Project C Project D Project
Project
Agile A1 A2
B1 B2
C1 C2
D1 D2 C3 D3
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Focus on High-Value Work

31. Systems Thinking
31
Source: Photo by Wim van 't Einde on Unsplash

32. Source: Yi Lv, 2020, Number of backlogs and multi-learning 32
#backlogs
e2e
cycle time
Specialization
+
Local
identity
+
#parts for
integration
+
Integration
time
+
+
+
+
Rework
time
+ +
+
+
Efficiency
+
Level of
collaboration
– –
Touch time
–
Level of
synchronization
–
Rework
–
Waiting
time
–
Efficiency
goal
Efficiency
gap
+
+
–
B1
R1
R2
–
R3
Knowledge
breath
–

33. Agenda
33
• The origin of story
• Challenges
• Self-designing team workshop
• Large Scale Scrum (LeSS) adoption
• 5 experiments in our process
How
Why
What

34. Source: Photo by PHC Software on Unsplash 34
One Open Space
vs.
Separate Rooms
Experiment #1

35. 35
Meeting in an open space

36. Meeting in separate rooms
36
Planner
Planner
Planner
Planner
SM
Planner SM
Planner
Room 1
Room 2
Room 3
Room 4
Scrum 1
Scrum 2
Scrum 3
Scrum 4

37. Source: Photo by Iva Rajović on Unsplash 37
How does the team
select stories?
Experiment #2

38. Sprint Backlog: Select by priorities and the same epics
38
One Product
Backlog
Team 1
Sprint Backlog
Team 2
Sprint Backlog
Team 3
Sprint Backlog
Team 4
Sprint Backlog

39. Source: Photo by Ante Hamersmit on Unsplash 39
How do we deal with
online issues?
Experiment #3

40. Scrum
Form a maintenance team
• Each team takes turns in the maintenance work for
certain period.
• When it’s a team’s turn, half people do maintenance,
and other half people do development.
• This practice help developers broaden the knowledge
and focus on the whole product.
40
Maintenance
Development

41. Source: Photo by LinkedIn Sales Solutions on Unsplash 41
One day, the PO told everyone that
it’s time to build the next generation
of product.
But, how so many teams develop
at the same time?
Experiment #4

42. Have a leading team and add new teams in area
42
Sprints
Team #2 joins PBR
to learn new area
Team #3
joins area
Team #2
joins area
Start new team
in area
Team #3 joins PBR
to learn new area

43. Source: Photo by Tim Mossholder on Unsplash 43
Do we really need full-time
Scrum Masters?
Experiment #5

44. Scrum Master Focus
44
Source: https://less.works/less/structure/scrummaster

45. 45
Half-time SM Full-time SM
• Serve one team
• Take SM and developer role
• Focus on team
• Involve himself in the team
• Switch roles frequently
• Serve two team
• Take Agile Coach role and
support other SMs
• Focus on team, PO and
organization
• Stay neutral and unbiased

46. 46
SUMMARY

47. 47
How
Why
What
• Increase customer value
• Reduce waste and lead time
• Form feature team
• Reduce social conflicts
Leading
Team
Meeting
Room
Select
Stories
Online
Issues
Full-time
SM
Challenges with Scale
Self-designing team workshop

48. 48
There will be no “BEST” in this world…
Only “BETTER” exists

49. Reference
• less.works
• Leading Large Scale Product Development with Large-Scale
Scrum (LeSS)
• Introduction to Large-Scale Scrum LeSS
49

50. 51
Q A