Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A Story of Self-Designing Team

A Story of Self-Designing Team

2021/09/08 Agile Summit by Derek Wang
Event page: https://agile.ithome.com.tw/

2102a6b8760bd6f57f672805723dd83a?s=128

LINE Developers Taiwan
PRO

August 30, 2021
Tweet

Transcript

  1. Derek Chen[陳岳澤] 一個關於自我規劃 團隊的故事 A Story of Self-Designing Team

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

  3. Agenda • What is self-designing team? • A story of

    self-designing team at LINE TODAY • How do we proceed self-designing team workshop • Any alternative approaches? • Reflection and learning from the story 3
  4. 你覺得團隊裡最常⾒ 的問題是什麼呢? 4

  5. 5

  6. 6 https://theconversation.com/actually-its-ok-to-disagree-here-are-5-ways-we-can-argue-better-121178 Human Problem Poor Communication

  7. 7 Photo by Annie Spratt on Unsplash Is it possible

    for us to choose whom I work closely with every day?
  8. 以下哪個描述最符合你目前所在的團隊? 8

  9. 9

  10. Four Levels of Team 10 J. Richhard Hickman, Leading Teams:

    Setting the Stage for Great Performances
  11. The story starts in 2018 11

  12. LINE TODAY 12 Taiwan Thailand Indonesia Hong Kong

  13. Background • Product team • 40+ people • 1 PO

    team (PO, planners and designers) • 3 component teams (developers and testers) • Process • Multiple product backlogs • Six-weeks of a Sprint • Small-waterfall (analysis, development and testing phases) • Tasks were dispatched by team lead 13
  14. Challenges • 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 14
  15. Goals Increase customer value One product backlog to determine priorities

    Reduce waste and lead time Reduce handoffs and dependencies Form feature team Cross-functional, co-located, long-lived Each team can select any item from backlog Reduce social conflicts Let teams reform themselves 15
  16. We adopt LeSS framework 16 https://less.works

  17. 17 Self-Designing Team Workshop

  18. Workshop Schedule Duration Topic 00:10 Opening • Introduction • Agenda

    00:20 Ideal team definition • Define team skills • Evaluate personal skills 01:35 Forming team • Briefing rules (10 mins) • 3 iterations, including reviews (25 mins) • Less time for iteration 2, 3 • Break between iteration 2, 3 (10 mins) 00:30 Voting • Scrum Master • Team name 00:10 Closing • Retrospective • Thanks • The workshop took about 3 hours, followed by a dinner • About 40+ participants including management • Management explained product vision and workshop target, and then left • Management came back at the end for team presentations and closing
  19. Defining team skills… 19

  20. Evaluating personal skills… 20

  21. Briefing Rules… 21 • Form 4 feature teams • Team

    size is 7 - 8 people (excluding PO, Planner and SM) • The need for diversity of skills and experience in each team
  22. Iteration Timetable 22 Duration Topic 00:20 Iteration 1: forming team

    00:05 Review 00:20 Iteration 2: forming team 00:05 Review 00:10 Take a Break 00:20 Iteration 3: forming team 00:10 Review
  23. 23 Forming team…

  24. 24 Reviewing…

  25. Reviews • Iteration 1 • The number of people in

    each team was not equal • Iteration 2 • Some team lacked high skilled and mature experience • The process stagnated • Iteration 3 • After the break, someone voluntarily joined another team • Finally, we matched the constrains 25
  26. Scrum Master • There are two dedicated SM • Teams

    vote for their SM • One SM serves two teams 26
  27. Team Name • All Stars、Avengers、Champions、Crew、Legends、Ninjas、Power、 Revolution、Rule Breakers、United、Vikings、Warriors • Aces、Blaze、Chaos、Empire、Extreme、Mafia、Unbeatable •

    A Team Has No Name、No Shame、Wasted Potential、We Showed Up、Mandatory Fun、Make Teams Great Again、Heartbreakers 27 Photo by Duy Pham on Unsplash
  28. Retrospective 28 Good Bad • Interesting forming process • I

    can decide who to work with • Creation of well-balanced team • Sense of team spirits • Creative team names • More information ahead the workshop • Reluctance of team members to move out from the original team • Need more facilitation to break out the deadlock • Pressure join a team you’re not happy with
  29. Alternative Approaches 29

  30. Forming 30

  31. Team Knowledge Model • The knowledge distribution within the team

    • Balance of challenges and skills • Lack of knowledge in the team • Knowledge development over time 31 Valtech, Team Knowledge Model
  32. Team Vision 32

  33. Team Charter - do’s and don’ts 33

  34. Common DoD 34

  35. World Café: Discuss technical best practice Development Process Testing Automation

    Code Quality CI / CD
  36. Lessons Learned • Provide more information ahead the workshop •

    Getting stuck in iteration 2 seems normal. Have a break and trust people to get job done • One facilitator for each team helps to speed up forming team • A lot of positive energy and joy from the workshop • There is a sense of empowerment at the end of the three hours 36
  37. Reference • Self-designing Feature Teams by Josef Scherer • LeSS

    Official Site • BMW Group • Port of Rotterdam • Huawei • Large Scale Transformation at PandaDoc 37
  38. 38

  39. 39

  40. Derek Chen[陳岳澤] Thank You