Less in-action
-
Upload
india-scrum-enthusiasts-community -
Category
Leadership & Management
-
view
135 -
download
0
Transcript of Less in-action
Gosei Oy all rights reserved.
Session
Product development started in 2007
Two teams and management culturesWaterfallAgile
The productHigh capacity GGSN and SAE Gateway
What did we learn about LeSS
2
Gosei Oy all rights reserved.
Who am I
3
Ran NymanWorked with LeSS in 2005
Worked with many large SAFe implementations for several years between 2008 and 2011
MSc in Computer Science
Since in 1995 professional SW development
Gosei Oy all rights reserved.
Starting Phase
Two teamsMixing teamsComponent or Feature teams?
No legacy codeHow often can you start from scratch?
First steps Build initial architectureCreate Producut BacklogDecide tooling and development practices
5
Gosei Oy all rights reserved.
Setting up Teams
Where to get ScrumMasters?
What do with managers?
Mixing teams a good approach?
6
Gosei Oy all rights reserved.
Deciding Development Practices
Programming Language
Continuous Integration
Automated Acceptance TestingTools Robotframwork.org with Catapult driver
Unit testing
Fast feedback!Even with prototype Hardware is essential
7
Gosei Oy all rights reserved.
LeSS with 2 Teams
Initial Product Backlog Creation
Initial Architecture
Common Sprint Planning 1 & 2
Scrum of Scrum coordination during Sprint
Joint Sprint Review
Team Retrospectives
Overall Sprint Retrospective
9
Gosei Oy all rights reserved.
Remarks
Arguments between teams
Do not separate teams in opposite end of building
Common planning and workshops are not enough
Create shared space with teams that create initial architecture
Technical challenges
Planning vs Doing balance was hard to find
Improvements!17
Gosei Oy all rights reserved.
Growing Phase 1
Adding 4 more teams to existing siteNon agile backgroundResistance to new ways of Coaching helped
20
Gosei Oy all rights reserved.
LeSS with up to 6 Teams
Common Sprint Planning 1 and 2 did not work anymore
Common Product Backlog Refinement did not workSprint Planning 1 and Product Backlog Refinement with Team Representatives
21
Less.Works - Ran Nyman
Sprint Planning
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
SM
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
SM
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
SM
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
SM
TR SMPO
TR TR
TR
TR
TR
TRTR1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Sprint backlog
Team
PO
Team
PO + TeamsMore than few teams
Less.Works - Ran Nyman
Sprint Planning
Team
SMSM
TR SMPO
TR TR
TR
TR
TR
TRTR
Team Team Team
SM
Team Team
1
2
Time-‐box 2h
Sprint planning PO + Team representatives
Time-‐box 2h
Sprint backlog
Team
PO
Team
PO + TeamsMore than few teams
Gosei Oy all rights reserved.
Remarks
Growing from 2 to 6 teams was easy
Coaching helps
Do not underestimate resistance
25
Gosei Oy all rights reserved.
Offsite Teams
Adding offsite subcontractorTrainingVisit to main siteSame rules as for local teamsProduct Owner proxyOffsite technical helpers
27
Gosei Oy all rights reserved.
LeSS Huge
Introduced requirement areas
Team working mainly in one requirement area1-2 Teams per area
Area Product Owners?From Product ManagementFeature experts
28
Gosei Oy all rights reserved.
LeSS Huge in Action
Common cadence to all teams
Sprint Review to SequentialPO + Feature Experts visiting each team
Product Backlog refinement per Requirement Area
Separate Sprint Review for offsite teamsOffsite Proxy Product Owner key person
31
Less.Works - Ran Nyman
Moving to LeSS Huge
Adds:Requirement Areas
Area Product OwnerArea Product Backlog
Less.Works - Ran Nyman
Moving to LeSS Huge
Adds:Requirement Areas
Area Product OwnerArea Product Backlog
Gosei Oy all rights reserved.
Observations
Overall RetrospectiveHow to get improvements done and keep people motivated
What do with project mangers?
Performance testing?
33
Gosei Oy all rights reserved.
Analysis
Impediment service
Training
Managers as development team worked fabulously
Requirement Areas too Small -> No Area Product Owners
Real Area Product Owners not Feature ExpertsFeedback and motivation for teams
34
Gosei Oy all rights reserved.
Achievement
Capability to release in 2 week cadence
Fast reaction to changing requirements from customer
“As a result of our Agility in developing products, we have been able to demonstrate the product capabilities at an early stage of the development cycle itself, helping us to win new customers cases.”
Head of Business-line
41
Gosei Oy all rights reserved.
Employee Feedback
42
We would have not succeeded without LeSS
This is the only way of building products. We do not want to go back to sequential development.
More collaboration, freedom, discussions, impacts on productSeeing the results with fast feedback
ChallengesHow to keep architecture in good shapeSeeing the whole difficult
Gosei Oy all rights reserved.
Conclusions
LeSS was only viable option
We focused too much on developing product
Focus on process is important also
Coaching is not enoughOffer training
Involve higher managementHaving support only from product group is not enoughSustainable agile organization needs changes in organizational structure
Customer visit!
Moving from LeSS to LeSS Huge needs effort
43
Questions
Upcoming LeSS Trainings in India:http://bit.ly/LeSS-BLR
http://bit.ly/LeSS-PUNE
More with LeSS: http://less.works
45