Презентация выступления Константина Разумовского и Артема Колышкина.

1. 1CONFIDENTIAL
NEXUS:
HOW WE DO SCRUM WITH 150+ PEOPLE
ARTEM KOLYSHKIN
KANSTANTSIN RAZUMOUSKI
March 11, 2017

2. 2CONFIDENTIAL
• Artem Kolyshkin
– Senior Delivery Manager
• Kanstantsin Razumouski
– Agile Coach
ABOUT US

3. 3CONFIDENTIAL
CONTENTS
The Pain1
Nexus Framework2
Our Experience with Nexus3
Nexus+4

4. 4CONFIDENTIAL
THE PAIN

5. 5CONFIDENTIAL
• 100% re-engineering of existent warehouse system used by stores for day-to-
day operations: ordering, inventory management, shipping and receiving,
reporting, and much more.
OUR CUSTOMER & PRODUCT
Customer
Product
• A big retail company, that offers a broad range of retail products, home and
financial services.

6. 6CONFIDENTIAL
• Which process to use?
THE QUESTION

7. 7CONFIDENTIAL
THE SCALING PAIN: DEPENDENCIES
Data Management
Claims &
Settlements
Order ManagementDeal Management
APO
Placing &
Seasonal
Signage
Reporting
Employee
Purchase
Workforce
Management
Security
Inventory Management
Shipping & Receiving
Store Analysis
Management
Reporting
Operational
Reporting
System Utility
Daily Sales
Fast Find
Inquiry
Returns
Management
Price
Management
Search
Multi-Store
Functions
APAP
AIM
Merchandising
Regular
Order

8. 8CONFIDENTIAL
NEXUS FRAMEWORK

9. 9CONFIDENTIAL
• Created by Ken Schwaber and Scrum.org
• Fully defined in 11 page Nexus Guide
• Heavily focused on dependencies
NEXUS FRAMEWORK: OVERVIEW
Nexus (noun) - a relationship or connection
between people or things

10. 10CONFIDENTIAL
NEXUS

11. 11CONFIDENTIAL
“We need multiple-teams Scrum,
not multiple Scrum teams.”
Craig Larman
#ScaledScrumIsStillScrum
cbn Group work by Eldan Goldenberg
“Nexus is an exoskeleton of scaled Scrum”
Ken Schwaber

12. 12CONFIDENTIAL
OUR EXPERIENCE
WITH NEXUS

13. 13CONFIDENTIAL
ORGANIZING TEAMS

14. 14CONFIDENTIAL
IDENTIFYING DEPENDENCIES

15. 15CONFIDENTIAL
IDENTIFYING DEPENDENCIES

16. 16CONFIDENTIAL
IDENTIFYING DEPENDENCIES

17. 17CONFIDENTIAL
• Accountable for Nexus integration
• In normal mode acts like a virtual team
• Raises awareness of dependencies
• Ensures integration tools and practices are
known and used
• Serves as consultants, coaches, and
communication links
• Facilitate shared architecture
NEXUS INTEGRATION TEAM: THEORY

18. 18CONFIDENTIAL
• Facilitating cross-location communication and decision
making issues
• Facilitating grooming sessions for dependencies
identification
• Ensuring Nexus rules are understood and followed, e.g:
– Integrated Increment meets DoD and deployed to STG env
– Sprint-related information is transparent for all stakeholders
• Continuous deployment process runs like clockwork
• Common engineering excellence practices are in place and
supported by all teams
NEXUS INTEGRATION TEAM: OUR PRACTICE
Product
Owner
Solution
Architect
DevOps QA
Delivery Manager
Project Manager
BA

19. 19CONFIDENTIAL
TECHNICAL EXCELLENCE IN NEXUS: THEORY
“Many software development practices are
needed to create an Integrated Increment.
Most of these practices require automation.
The automation helps manage the volume
and complexity of the work and artifacts
especially in scaled environments.”
Nexus Guide

20. 20CONFIDENTIAL
TECHNICAL EXCELLENCE: OUR PRACTICE
Auto
Manual
Automated tests cover
97% of requirements

21. 21CONFIDENTIAL
NEXUS DEFINITION OF ‘DONE’
DoD
• All acceptance criteria are met
• All required types of auto-tests are created
• Story tests are all green
• The story is in the QA environment
• All smoke tests are green
• Regression tests are more than 85% green
• Code review is done before merge and all review
issues are resolved
• Non-functional requirements are implemented
• Architectural, developer's guidelines, standards
conventions must be obeyed
• REST API is documented
• There is no new sonar ‘major’ issues
• Git branch is deleted after merge
• PO has accepted the story

22. 22CONFIDENTIAL
NEXUS+

23. 23CONFIDENTIAL
1. Low cohesion between some parts of the Nexus.
2. Complexity of long-term scaled planning.
3. Monotony of scale.
4. Difficulty/cost of changes.
5. Keeping up engineering excellence (moving to level 4).
NEW CHALLENGES
As we grow and have reached 180+ size we have faced some new challenges:

24. 24CONFIDENTIAL
AT SCALE YOU ARE UNIQUE (TRIBUTE TO JURGEN APPELO)
Product
Backlog
https://medium.com/agility-scales/stop-your-agile-transformation-right-now-6cf2ef2fa1a#.vbk4oydgh

25. 25CONFIDENTIAL
OUR BARBAPAPA (TODAY)
APO Area
(9 squads)
Original Nexus (now 12 teams)
Integration Area
(5 squads)
Product
Backlog

26. 26CONFIDENTIAL
NEXUS POINTS OUT FAULTS AT ENTERPRISE LEVEL
cbn Group work by Eldan Goldenberg
“Scrum is like your mother-in-law,
it points out ALL your faults”
Ken Schwaber
© Mountain Goat Software, 101 Inspiring Quotes about Agile

27. 27CONFIDENTIAL
1. Nexus helps to capitalize on your existing Scrum experience.
2. Nexus (scaled Scrum) is still Scrum.
3. New roles/artifacts/rules address the pain of dependencies and integration.
4. Automation and technical excellence are crucial at scale.
5. Nexus+ recognizes uniqueness at scale and only provides guiding principles.
6. Nexus is a catalyst for business agility, but not a silver bullet.
LESSONS LEARNED

28. 28CONFIDENTIAL
REFERENCES

29. 29CONFIDENTIAL
REFERENCES
www.scrum.org/Nexus Scaled Professional Scrum, 2 day course
Nexus + 50 scaling practices
=

30. 30CONFIDENTIAL
• Artem Kolyshkin
– Artem.Kolyshkin@gmail.com
– linkedin.com/in/akolyshkin
• Kanstantsin Razumouski
– www.proscrum.by
– linkedin.com/in/razumovsky
QUESTIONS?