Regional Scrum Gathering Tokyo 2019

1. Dropped My Leadership,
And Put It
Into The Team Circle.
SMS Career, inc
Product Development Department
Atsuko TsujiokaRSGT2019

2. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

3. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

4. Profile

5. ProfileAtsuko Tsujioka
April,2011 ~ April,2016 Rakuten,inc.
As Web Application Engineer (java,scala,ruby)
May,2016 ~ SMS Career,inc.
As Engineer of Recruitment Consultant Service
(salesforce, python etc. vue.js(in salesforce env)

6. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

7. Started Team

8. Dictionary : Internal Words
Career Partner
- Recruitment Agent
System Planning
- My Affiliated Post

9. Biz Marketing/
Inside Sales
System
Planning
Customer
Web Marketing
Career
Partner
System Planning
＝System Support

10. Process load image

11. Why just 3 process were high?

12. Detail Process x Load Image

13. Found the reason

14. It may be better
to leave….
※when passed only 3 month from I
joined.

15. She throws the word to All
employees in award ceremony.
Career Partner

16. Is it
for your customer?

17. Biz Marketing/
Inside Sales
System
Planning
Customer
Web Marketing
Career
Partner
Dev should not work only for
internal people,

18. Biz Marketing/
Inside Sales
Development
Career Partner
Web Marketing
Customer
Should work for our customer,

19. I become to team leader,

20. Team structure and what I did
Structure
- 3service
- 5~6 engineer
What I did
- Explained about what is scrum
- Input daily scrum
- Input sprint planning (1week )
- Input retrospective
- Input Kanban style(Trello)

21. After a half year...

22. Before

23. After

24. Establish basic processes

25. Decrease MUDA Process

26. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

27. Dropped Leadership

28. Previous team can not vanish MUDA Process.

29. Biz Marketing/
Inside Sales
Development
Career Partner
Web Marketing
Customer
Far from ….

30. WHY

31. No person who have
the basic role in the
scrum book.

32. No
Product Owner

33. It is difficult to find
the matched person.

34. What is our mission
for our customer?

35. What is “team leader”?

36. After consideration

37. Dropped
Leadership

38. Why？
To become the team that
develops for our
customer continuously
also in the future.

39. - Everyone can lead to anyone
- 1 leader makes the dependency to leader
- If all team member have the leadership, we
can break down the wall.
- That’s all I can come up with now.
Why?(Detail)

40. Believe the team
Aim for the person who is
believed by the team.
What team leader(I) did?

41. What team leader(I) did (Detail)?
- Decide by team, not by leader.
- Support if member confused. But not
support to the utmost.
- Drop to think about own evaluation
- Guard team immediately if had a trouble
- Coding as a player

42. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

43. Cooperation
With The Team

44. Engineer
Team Leader
It was the normal relationship.

45. Engineer
Team Leader
vanish

46. Engineer
Product
Ownership
Engineer
Team
Leader
Named the role that approach to requirement
as “Product Ownership Engineer”

47. What we did?
Reveal our true
self each other

48. What we did (Detail)?
- Talked anyone in retrospective(with snack sometimes)
- Team workshop
- Team review

49. Why?
To get the env that we can
work for what we really
want to do.

50. Why(detail)?
- Confirm User’s voice and confirm what we
should do.
- Work with real intention and do KAIZEN with
seriousness.
- Should work for your interesting, not for easy
for you.
- To abolish Human dependency

51. Engineer
Leadership
Product Ownership
Engineer
Leadership dived to the team circle!

52. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

53. Cooperation
With Career Partner

54. Product
Ownership
Engineer
Career
PartnerEngineer
We don’t know about
your works (each other).

55. What POEngineer did to CareerPartner?
Reveal our true
self each other

56. What POEngineer did to CareerPartner(Detail)?
- Explain about system overview to Career
Partner
- Career Partner tells us about there’s work
- Explain about our time for resolving there
request and reason why takes the time.
- Get feedback after released

57. Why?
Because, We also want to
work for our customer.

58. Why(Detail)?
- Want to be known dev’s work
- Want to be known system structure’s
problem
- Want to resolve true problem each other

59. Career
Partner
Engineer
Product Ownership
Engineer
Connected to Career Partner

60. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

61. Extra Edition

62. The slide story was in 1~2
years ago,
Let me introduce for the event
in 2018 after the story.
Future is now

63. 2018
Increased things
to challenge.

64. What 2018 dev group started to do
- Abolish the role “team leader”
- Establish “project team”
- Rotate “facilitator”
- other….

65. Biz Marketing/
Inside Sales
Development
Career
Partner
Web Marketing
Customer
Gradually closing this future

66. ● Profile
● Started Team
● Dropped Leadership
● Cooperation With The Team
● Cooperation With Career Partner
● Extra Edition
● After I dropped My Leadership

67. After I dropped My
Leadership

68. Wall was

69. Broken down

70. As a Result

71. Just system supporter changed to

72. Development Team

73. Team think about
“the reason” for
every thing.

74. Increased the
“Time” for team
leader.

75. And then,

76. Career Partner
Product Ownership
Engineer
All team member had
Product Ownership.

77. YAMAZUMI
One of methods to create
load map in lean production system.
Reference：

78. |ω·)ノ See you again!
Twitter: @kappezoro
Facebook: atsuko.tsujioka