1) The frontend team at Rakuten Ranking migrated from Kanban to Scrum to measure velocity and integrate development processes. 2) They experienced common Scrum implementation challenges like lack of problem sharing and workload imbalances. 3) Through adjustments like allowing additional work during sprints and regular skills sharing, the team achieved stable service delivery and a well-balanced workload over six months. 4) The team continues improving through challenges like maintaining communication and team dynamics remotely during the pandemic.

1. In to the unknown :
Successful Scrum Migration
Sep 26th, 2020
@woosyume
Scrum Fest Mikawa 2020
Rakuten, Inc.

2. 2
Woohyeok Kim
# Certified Scrum Master
# Speaker at RSGT2020 etc.
# Favorite Lang : Korean, Java
Engineer at Ranking Frontend
Selenium User Community Organizer(Kansai)
ウヒョク キム
Speaker
- Developers Summit Kansai 2020
- Regional Scrum GatheringTokyo 2020
- DevRelCon Earth 2020
- SeleniumConf 2019
- AgileJapan 2019
- Etc.

3. 3
Target of this session
1) Anyone who want to introduce Scrum
2) Anyone who want to understand what effect should be
expected from Scrum migration etc.

4. 4
Intro

5. 5
Scrum and Agile
The most commonly used agile method, Scrum
Share
Scrum Hybrid ScrumBan XP Kanban Others
56%
Scrum

6. 6
Agile History
There are variety of trials for providing better product
1) Visual-Paradigm, 2020/09/18, https://www.visual-paradigm.com/guide/agile-software-development/what-is-agile-software-development/

7. 7
Other frameworks in Agile perspective : Kanban
Maximize capacity so that team can process more tasks
WIP, WIP !!
1) Wikipedia, 2020/09/18, https://en.wikipedia.org/

8. 8
Other frameworks in Agile perspective : Extreme Programming (XP)
With Brave, Responsibility of person
Goal is providing high quality product to customers
Recursiveness
1) Wikipedia, 2020/09/18, https://en.wikipedia.org/

9. 9
Other frameworks in Agile perspective : Feature Driven Dev(FDD)
Domain Object Modeling → Create high-level class → Add artifacts
Regularity
1) Wikipedia, 2020/09/18, https://en.wikipedia.org/

10. 10
Other frameworks in Agile perspective : Crystal Methodology
Continuous Integration, Flexible process, Active user involvement
Creating / Maintaining our product as a valuable crystal
Ownership
1) Free PNG provider, 2020/09/18, https://www.pngbarn.com

11. 11
Comparison with other frameworks
Scrum XP
Common Continuous improvement with short term
Characteristic
Cultural,
Managing ORG
Engineering
Task priority
Product Owner,
Developers
Customers
Changed Request Review/Planning Refactoring
Let’s see similar framework with Scrum

12. 12
Comparison with other frameworks
Scrum XP
Common Continuous improvement with short term
Characteristic
Cultural,
Managing ORG
Engineering
Task priority
Product Owner,
Developers
Customers
Changed Request Review/Planning Refactoring
Let’s see similar framework with Scrum
Scrum Kanban
Cadence Regular Fixed(Sprint) Continuous Flow
Release Methodology At end of each sprint Continuous Delivery
Roles SCM, PO, DEV No Required Roles
Key Velocity
Lead Time, Cycle Time,
WIP
Philosophy
Shouldn’t make change
during the sprint
Change can happen at
any time

13. 13
Why Scrum would be Mainstream of Agile
It considers happiness the most valuable engine for improvement
1) Free PNG provider, 2020/09/18, https://www. flaticon.com

14. 14
Scrum concerning with Happiness
Motivation
Team
Wellbeing
Productivity
Happiness is core of it

15. 15
What happened
in Rakuten Ranking?

16. 16
What is Ranking Service
Provide item ranking ordered by some factors (sales etc.)
Support customers to see the latest trend feeling ‘Shopping is the entertainment’
PC TB
SP(feat. AMP)
Rakuten Ranking, 2020/09/20, https://ranking.rakuten.co.jp/

17. 17
Rakuten Ranking’s organization
Platform
provides score data
API
provides fixed rank data
Frontend
provides web UI
Scrum
KANBAN

18. 18
Frontend team in Rakuten Ranking
Operation
• Regular ops
(supersale
etc.)
• Trouble
shooting
New
Feature
• Adopt Google
AMP
• UI renewal
Kaizen
• Improve
performance
etc.
• Test
automation

19. 19
Frontend team as Ops
Team name is frontend but we do all thing related with providing web app.
(Server architecting, Managing traffics, Changing business logic etc.)
Usual works for a week
Others
Regular
Ops
Test
Automation
Operation
• Regular ops
(supersale
etc.)
• Trouble
shooting
New
Feature
• Adopt
Google AMP
• UI renewal
Kaizen
• Improve
performance
etc.
• Test
automation

20. 20
Worked with Kanban style
TODO DONE
…
WORK IN PROGRESS
通常オペレーション
トラブルシューティング
ビジネスリクエスト
改善タスク１
改善タスク２
改善タスク３
…
Maximizing WIP

21. 21
The Best team of Kanban
1)
MVP
Nominated 2 times and GOT ONE
Project of the month
Nominated 1 time
1) Free PNG provider, 2020/09/18, https://www. pngtree.com

22. 22
Frontend team was suggested
to migrate to Scrum

23. 23
Yes, why?
1. Want to see ‘velocity’ as objective data
2. Integrate each team’s dev process to one
3. And want to head for ‘Happiness’
Platform
provides score data
API
provides fixed rank data
Frontend
provides web UI
Scrum

24. 24
Members’ Scrum exp at that time
Almost member didn’t have any experience Scrum actually
Member Exp Knowledge
A - O
B 2 year O
C - △
D 1 year △
E - X
F 1 year △
G - X

25. 25
Ready to make good practice
• Team supported 2 members to take a CSM(Certified Scrum Master) course
• Others had study session discussing where to head
1) Free PNG provider, 2020/09/18, https://pngio.com/images/png-a152896.html

26. 26
We suddenly would be a Scrum team

27. 27
Try

28. 28
Backlog Migration
Migrated stories from Kanban to Scrum using Sprint backlog
Product Backlog Sprint Backlog
Usual operation
Business request
Kaizen task１
Kaizen task２
Kaizen task３
Existing WIP task
Existing WIP task

29. 29
Set 1 week Sprint to minimize difference from Kanban
Product Backlog
…
WORK IN PROGRESS
IN PROGRESS IN TEST Pending
Sprint Backlog
…

30. 30
1 week Sprint to minimize difference from Kanban
DONEOGRESS
Pending
… 1 Sprint
(1week)
IN REVIEW

31. 31
Hold Sprint Regular meetings
Planning / Review / Retrospective
Daily Scrum
Scrum Improvement Meeting

32. 32
Decide Team Scrum rule & Working Agreement
What is activity for our scrum?
What is the definition of DONE?

33. 33
Cultural trial for Psychological safety(心理的安全性)
Proactive Discussion with
Fun Done Learn
Fun Learn
Done
F+D
F+L
F+L+D
L+D

34. 34
And Other Small Rules…
Including how to define story,
We defined each rules to activate Scrum

35. 35
Alert

36. 36
Problem with No Problem
At every daily scrum, problem was not shared well.
It finally bombed at the last phase of sprint on Friday
NO PROBLEMBIGPROBLEM

37. 37
Coverage for sudden request
As an ops team, we must correspond to sudden request from business side.
It broke planned tasks’ frame in sprint
WORK IN PROGRESS
IN PROGRESS IN TEST Pending
Sprint Backlog
Existing WIP
task
Existing WIP
task
Existing WIP
task
Existing WIP
task
Existing WIP
task

38. 38
Superman appeared
We found abnormal trend that some tasks which are important, difficult
are centered on particular high-skilled member
He got other members but it broke balance
Member Story Point(%)
A 11%
B 9%
Superman 35%
…
1) Free PNG provider, 2020/09/18, https://pngwing.com/

39. 39
Not Happy one appeared
Some members felt that their opinion is not respected enough
Scrum team fell into the trap of democracy
Vote Result
Yes 63%
多数決で
APPROVED!!
No 37%
37% means 3 member of 8 disagreed with this agenda
37% is not small to igrnore
え？僕は違うと思うけど。。。 Voting for agenda
At Sprint Improvement Meeting
1) Free PNG provider, 2020/09/18, https://picpng.com/

40. 40
Trouble Shooting

41. 41
Create culture for sharing bottleneck freely
Having bottleneck sharing meeting right before daily closing meeting,
We tried to detect bottleneck fast and build a strategy to clear it beforehand
I’m in bottleneck…
Somebody help me
Let’s see it tomorrow :)
1) Free PNG provider, 2020/09/18, https://picpng.com/
2) Free PNG provider, 2020/09/18, https://vexels.com/

42. 42
Fuse with Kanban style by allowing to include additional stories
We allowed to add new tickets during the sprint but
decided to track it with tag
WORK IN PROGRESS
IN PROGRESS IN TEST Pending
Sprint Backlog
Existing WIP
task
Existing WIP
task
Existing WIP
task
Existing WIP
task
Existing WIP
task

43. 43
Fuse with Kanban style by allowing to include additional stories
Analyzing the sudden task was REALLY necessary at retrospective meeting
To minimize miss for future planning
Additional_sudden
Additional_sudden
Additional_sudden
“This could not be helped”
“This kind of task could be adjusted
with business side beforehand”
“This can not be helped”

44. 44
Balance each members’ possession of story point
People agreed with what I proposed
They started to realize the power of DevRel gradually
Member Story Point(%)
A 11%
B 9%
Superman 35%
…
Member Story Point(%)
A 15%
B 15%
Superman 25%
…
Hey A and B,
Can you please
support
the superman?
When planning just finished After load balancing
1) Free PNG provider, 2020/09/18, https://pngwing.com/

45. 45
Balance each members’ possession of story point
To enhance members’ level so that all member can be assigned to all tasks,
We regularly hold study session
1) Free PNG provider, 2020/09/18, https://pngwing.com/

46. 46
Introduce trial period
To avoid to fall into the trap of democracy,
We set trial period of 2weeks when we decide something.
And re-vote seeking to make a consensus for all Scrum members
Vote Result
Yes 63% TRIAL!
No 37%Vote Result
Yes 83% TRIAL!
No 37%Vote Result
Yes 100% APPROVED!!
No 0%
1st turn
2nd turn

47. 47
Achievement

48. 48
Stable service providing
No service down, No any big trouble with STABLE velocity
1) Rakuten Ranking, 2020/09/20, https://ranking.rakuten.co.jp/

49. 49
Well balanced team
Member Before After
A 13.6% 14.1%
B 8.1% 10.9%
Superman 35% 26%
D … …
E … …
F … …
G … …
Load Balancing for 6 months

50. 50
Team supporting each other PROACTIVELY
As one team, save each other beforehand not to meet bottleneck
Oh, may I help you?

51. 51
Team supporting each other PROACTIVELY
As one team, save each other beforehand not to meet bottleneck
Support and be happy

52. 52
Team studying TOGETHER
Experience resolved difficulty together could be motivation for self-developing
Why this situation arised?
Could we prevent this problem?
Let’s analyze the cause together

53. 53
[Special]
With Corona

54. 54
Scrum online
Online poker

55. 55
Scrum online
Mob
Programming

56. 56
Scrum online
Discussion
Via board

57. 57
Of course we’re facing problems now as well
Superman is
still superman
Less
communication
under Corona

58. 58
But we can enjoy this unlimited challenges
as we can always find co-worker beside of us

59. 59
So, How to migrate
to Scrum?

60. 60
Scrum Migration Roadmap
Define
Team’s
Happiness
Understand
Why we
seek Scrum
Create
Shikumi
for
correspond
ing
changes
e.g. Mob
pro,
Code
inspection
Imagine
what
should be
changed
Follow
what you
decided
1 2 3 4 5
Preparati
on
Make UNKOWN to KNOWN Do it!
Retrospect
continuous
ly
6

61. 61
And
Love your team
【 Free image provider, www. pexels.com, 2020/09/18 】
Scrum Migration Roadmap