4. The Reality of Scrum Pilot
all work comes from product
backlog
one product owner deciding
overall priority for all the work
cross-functional team with
common goal and shared
responsibility
SM as coach not having delivery
responsibility
only feature work is in product
backlog
PO only responsible for feature,
manager still responsible for
maintenance and other work
cross-functional team members
only work in their own speciality,
do not cross-learn, partially work
on this project, etc.
SM (renamed from project
manager or team leader) still
responsible for delivery
5. Team Design vs. Coaching
Richard Hackman,“Leading Teams: Setting the Stage for Great Performances”
8. LeSS vs. LeSS Huge
For the product group, establish the complete
LeSS structure “at the start”; this is vital for a
LeSS adoption.
LeSS Huge adoptions, including the structural
changes, are done with an evolutionary
incremental approach.
16. Work Redesign
Before After
Work is scattered All work goes to one product backlog
Work is organized in programs Work is organized in product, with
programs only as outside interfaces
Multiple program managers One PO (Product Owner)
Done in phases (analysis,
development, testing)
Common DoD (Definition of Done) for
all requirements
27. W
hat are RAs?
Web interface
Collaborative operation
Application/content
security
Pipeline security
Basic security
System support
System
management
Core forwarding
Data security
28. W
hat are RAs?
Web interface
Collaborative operation
Application/content
security
Pipeline security
Basic security
System support
System
management
Core forwarding
Data security
29. One Shared Backlog in RA
System support
System
management
Core forwarding
Data security
System support
Wei
Shu
Wu
https://blog.odd-e.com/yilv/2015/12/shared-backlog-with-one-priority.html
32. Organization-first approach
✓Use an incremental approach to expand
domain specialization for more flexibility
✓Take a transitional path from traditional
Team Leader to ScrumMaster/Coach
✓Enable self-organization across teams via
joint Scrum events.
✓Enable one PO vs. multiple teams by getting
teams on requirement clarification and
feedback.
