Large-Scale Scrum (LeSS) Road, Where does it Leads?

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Agenda › Background › LeSS Overview › TODAY’s LeSS Experiment › Current State

Slide 3

Slide 3 text

Background

Slide 4

Slide 4 text

Not a Large Scale Scrum (LeSS) Lecture › Debate what is the best approach ✘ › Provide basic LeSS Overview for the purpose of understanding terms used and content of this session ✓ › Underlying reasoning behind LeSS principles ✘

Slide 5

Slide 5 text

Team’s Belief Embrace Agile values and mindset, Don’t stick to a particular Agile methodology Trust No Trust = Not Agile Believe in transparency, overcommunicate, and open-minded Collaboration Open-minded to suggestions from others and learn from experience Responding to change Flexible to change Being able to respond fast to changes in market

Slide 6

Slide 6 text

LINE TODAY News content delivery platform

Slide 7

Slide 7 text

Stakeholders from multiple locations Requirements increases as user base grew Taiwan Thailand Indonesia Hong Kong

Slide 8

Slide 8 text

Team Composition Multi-functional 40+ Members Backend Frontend Service Planner Designer QA

Slide 9

Slide 9 text

Problem as Team and Delivery Item Grow Trust Business owner’s request takes longer to deliver Collaboration More burden: Service Planners for detail specs, Developers code base dependency grew, QA needed more time to test Responding to change 4-6 weeks per release Requirement at most may miss current sprint and wait 2 months

Slide 10

Slide 10 text

LeSS Overview

Slide 11

Slide 11 text

Some LeSS Principles Principles most relevant to the session

Slide 12

Slide 12 text

LeSS is Scrum › Transparency › Empirical process control › Self-managing teams

Slide 13

Slide 13 text

More with LeSS Descale to Scale Less › Roles › Artifacts › Processes More › Responsible teams

Slide 14

Slide 14 text

Ceremonies in LeSS

Slide 15

Slide 15 text

Ceremonies in LeSS Overall Retrospective Sprint Planning 2 Sprint Review Product Backlog Refinement Team Daily / Retrospective Sprint Planning 1

Slide 16

Slide 16 text

Ceremonies in LeSS Overall Retrospective Sprint Planning 2 Sprint Review Product Backlog Refinement Team Daily / Retrospective Sprint Planning 1

Slide 17

Slide 17 text

Ceremonies in LeSS Overall Retrospective Sprint Planning 2 Sprint Review Product Backlog Refinement Team Daily / Retrospective Sprint Planning 1

Slide 18

Slide 18 text

Ceremonies in LeSS Overall Retrospective Sprint Planning 2 Sprint Review Product Backlog Refinement Team Daily / Retrospective Sprint Planning 1

Slide 19

Slide 19 text

Team Anxiety with LeSS › How to measure success or failure of the experiment?

Slide 20

Slide 20 text

TODAY’s LeSS Experiment

Slide 21

Slide 21 text

First Target Goal Backlog 1 Sprint 2 week Scrum Teams 4

Slide 22

Slide 22 text

Forming New Teams

Slide 23

Slide 23 text

Forming New Teams 4 Teams, 8 people max

Slide 24

Slide 24 text

New Product Team Structure Product Owner Backend Frontend QA Backend Frontend QA Backend Frontend QA Backend Frontend QA Scrum Master Scrum Master Dev Lead Service Planner Designer Service Planner Designer

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Sprint Cycle Goal: 2 Week Sprint 1 Potential Shippable per Sprint Release at end of Month 1 Potential Shippable per Sprint + Use 2nd Sprint as buffer Release every 2 Sprint 1 Potential Shippable per Sprint Release every 2 Sprint 1 Potential Shippable per Sprint Release every Sprint Transition (2W Sprint) Transition (2W Sprint) Goal Before (4W Sprint)

Slide 30

Slide 30 text

Carrying out Ceremonies

Slide 31

Slide 31 text

PO short brief the whole team on the Sprint goal and priority. Members from all 4 teams pick tickets from the top, and quickly trade with other team to maximize productivity. Sprint Planning 1 ( Overall Planning ) Each team takes the selected tickets and begin planning independent from other teams. Base on estimation and story break down, quickly negotiate with service planners Sprint Planning 2 ( Single Team Planning )

Slide 32

Slide 32 text

Product Backlog Refinement PBR Group discussion Group discussion Group discussion Group discussion Converge

Slide 33

Slide 33 text

Product Backlog Refinement PBR Group discussion Group discussion Group discussion Group discussion Converge Overall PBR Single Team Pick / Trade ticket as if Planning 1

Slide 34

Slide 34 text

Sprint Review

Slide 35

Slide 35 text

Sprint Review › Difficult to organize bazaar-like style › Big screen, presentation is clearer › Stakeholders can easily watch all presentations › Comments / suggestions can be discussed with everyone present

Slide 36

Slide 36 text

Overall Retrospective › Team velocity healthcheck › Resource issues requiring manager assistance › Cross team / function collaboration improvement › Any good lessons learned worth sharing with other team Team Representatives Scrum Masters Product Owner Managers

Slide 37

Slide 37 text

Continuous Improvements

Slide 38

Slide 38 text

Continuous Improvements 2 Week Release Goal (Community) Knowledge sharing Function-wise, Cross-team More responsible teams Gradual rollout, Feature toggle, Automation coverage, QA regression shortened Planning/PBR Task breakdown, Estimation, ticket exchange, align PBR/Planning teams Scrum/Kanban? Split into leading team for V2 architecture revamp

Slide 39

Slide 39 text

Current State

Slide 40

Slide 40 text

Where does it leads?

Slide 41

Slide 41 text

Set Next Agile Goal › Keep building up trust › Keep seeking ways to improve collaboration › Be Agile

Slide 42

Slide 42 text

Thank you