safe meet up stockholm_ safe vs less
TRANSCRIPT
SAFe and LeSS – two frameworks for scaling agile Same, same but different?
Page 2
SAME, SAME
Page 4
#1 Agile and Lean Roots
AGILE MANIFESTO
LEAN THINKING
SYSTEMS THINKING
SCRUM
XP
SELF-ORGANIZING, X-FUNCTIONAL
TEAMS
AGILE PRINCIPLES
PRIORITIZED BACKLOGS STORIES
SAFe
Page 5
#2 Based on Principles
10 PRINCIPLES9 PRINCIPLES
SAFe
Page 6
#3 Synchronized Cadence
ALL TEAMS HAVE THE SAME “HEARTBEAT”
SYNCRONIZED EVENTS
SAFe
SPRINTS 1-4 WITERATIONS 2WAND INCREMENTS 8-12 W
Page 7
#4 Limit size for efficient collaboration
LESS 2-8 TEAMS AND LESS HUGE > 8 TEAMS
AGILE REALEASE TRAINS5-12 TEAMS
SAFe
VALUE STREAM
Page 8
#5 Frequent integration and technical practices
SAFe
TEST FIRST REFACTORING
PAIR WORK
COLLECTIVE OWNERSHIP
CONTINUOUS INTEGRATION
Page 9
#6 Leadership change
SAFe
IN ORDER THE CHANGE THE CULTURE IN THE ORGANIZATION, THE
LEADERS MUST CHANGE FIRST
GO SEEGEMBA
EXHIBIT LEAN & AGILE PRINCIPLES
EVOLVE THE SYSTEM
BUT DIFFERENT
Page 11
#1 Roles and organization
SAFe
PRODUCT MGMT
PO (1-2 TEAMS)
SMDEVELOPMENT
TEAM
RTE
SYSTEM TEAM
DEVELOPMENT TEAM
SM
PO (2-8 TEAMS)APO
RELEASE MANAGEMENT
ENTERPRISE ARCHITECT
BUSINESS OWNER
LINE MANAGERLINE MANAGER
“UN DONE DEPARTMENT”
SYSTEM ARCHITECT
VSESOLUTION MGMT
PROGRAM PORTFOLIO MGMT
DEVOPS
UXSHARED
SERVICES
SOLUTION ARCHITECT
EPIC OWNERS
SUPPORT
COACHING
Page 12
#2 Backlogs and PBIs
SAFe
EPIC, CAPABILITY, FEATURE, STORY
REQUIREMENT MODEL –“TREE LIKE SPLITTING”
• THEME• STORY
SHARED DEFINITION OF DONE FOR PRODUCT
CELL-LIKE SPLITTING
ONE PRODUCT BACKLOG
BACKLOGS• PORTFOLIO, VALUE
STREAM, PROGRAM, TEAM
1 SPRINT REVIEW - PRODUCT
SYSTEM & TEAM DEMO
DEFINITION OF DONE• TEAM(S), SYSTEM,
SOLUTION, RELEASEARCHITECTUAL RUNWAY WSJF
Page 13
#3 Planning and collaboration
SAFe
PM/PO COORDINATES
PI PLANNING & ITERATION PLANNING
SPRINT PACE
TEAM RESPONSIBILITY
INCREMENT PACE
SCRUM OF SCRUMS
PO – CUSTOMER INTERFACE/ CLARIFIES
PO CONNECTSCUSTOMER & TEAM
ITERATION PACE
Page 14
#4 Scaling
SAFe
KANBANSCRUM-XP
FEATURE TEAMS
FEATURE TEAMSCOMPONENT TEAMS
• CAPABILITIES/FEATURES• SUBSYSTEMS
SCALING SCRUM!
VALUE STREAMS
TEAM ADOPTION MAPS
PORTFOLIO
“SEVERAL SCRUM TEAMS”
“MULTI TEAM SCRUM”
SAME, SAMEBUT DIFFERENT!
Page 16
Design Principles
SAFe
ESSENTIAL SAFE
“OPEN”
#1 SIMPLE#2 BUILD UP#3 DESCALING# RULES
F_L_ I_ T_E B_AN_SPROCESS
PRACTITIONER
SCALABLE & MODULAR
COMPREHENSIVE
“CLOSED”“IT”
“PRODUCT”
The names says quite a lot:
SAFe – familiar, “everything” is thereLeSS - There are “holes”, is up to me to fill
Thank [email protected]