‚Scaling' became the most hyped and at the same time the most diversely interpreted word in the context of agile. The fad and the confusion obfuscate. Despite Scrum being the most adopted framework for agile software development, scaling Scrum in a way that respects Scrum's foundations and principles is a challenge. Many don’t scale the benefits of Scrum, but organizational dysfunctions that remain unaddressed through weak implementations of Scrum.
In his opening keynote of Scrum Day Europe 2015 Gunther shared the views of Scrum.org, the organization of Scrum co-creator Ken Schwaber, on Scaled Professional Scrum.
Gunther shepherds the Professional Series at Scrum.org, is a partner of Ken Schwaber and represents Scrum.org in Europe.
"Scaling" became the most hyped and at the same time the most diversely interpreted word in the context of agile. The fad and the confusion obfuscate. Despite Scrum being the most adopted framework for agile software development, scaling Scrum while respecting its foundations and principles remains a challenge. Few scaled implementations grew upon Scrum's DNA of empiricism and self-organization.
Gunther introduces the “Scaled Professional Scrum” framework and the Nexus by Scrum.org. The Nexus interconnects 3-9 Scrum Teams through… Scrum.
Gunther shepherds Professional Scrum at Scrum.org and is a partner of Ken Schwaber.
A healthy Scrum foundation is the best path to success before trying to scale, otherwise you’ll scale your current dysfunctions Scrum alone isn’t enough for success. Establishing, promoting, and stewarding technical excellence as a foundation for growth.
One team working on several products is not scaled Scrum. It is the reverse of scaling. Many teams each working on one product is a lot of Scrum, but not scaled Scrum.
Empiricsm From Stephen Hawking’s A Brief History of Time (1988):
A well-known scientist (some say it was the philosopher Bertrand Russell) once gave a public lecture on astronomy. He described how the Earth orbits around the sun and how the sun, in turn, orbits around the centre of a vast collection of stars called our galaxy. At the end of the lecture, a little old lady at the back of the room got up and said: “What you have told us is rubbish. The world is really a flat plate supported on the back of a giant tortoise.” The scientist gave a superior smile before replying, “What is the tortoise standing on?” “You’re very clever, young man, very clever,” said the old lady. “But it’s turtles all the way down!”
Self-organization Many natural systems such as cells, chemical compounds, galaxies, organisms and planets show this property. Animal and human communities too display self organization: in every group a member emerges as the leader (who establishes order and rules) and everybody else follows him or her, usually willingly.
Scrum, ultimately can only be fully comprehended when its rules and roles are read as an expression of the values and principles of the Manifesto for Agile Software Development. is an operating system for the values and principles of the Manifesto. The kernel of the OS is the Scrum Stance.
Professional Scrum: Any Scrum instance that implements Scrum’s mechanics, its values and principles, and technical excellence.
People – someone on another Scrum Team, in my Nexus or another Nexus, but not necessarily a PBI being worked on by another team; person is on vacation, only one person with that skillset, communication paths within the team and the Nexus, etc. Domain – If you are organized around business domains, there may be features that overlap those boundaries (e.g. workflow) Technology – frameworks, DBs, messaging servers, other types of servers, tools, etc. (e.g. don’t have access to a DB to deploy your code/schema) Software/software implementation – for a single team, execution sequence; across team, architecture misaligned to team structure (e.g. the code I need to change isn’t under my team’s control) External – any of the above types of dependencies which are not solvable within the Nexus (e.g. a finance person is required to provide biz rules)
The term “Nexus” means a connection, link; also a causal link, or a connected group or series. It’s origin is Latin (from nectere "to bind“) and was first used in 1663 (http://www.merriam-webster.com/dictionary/nexus)
It’s not about the structure, it’s about the connections (i.e. collaboration and conversation)
Consists of 3 to 9 Professional Scrum Teams: To interoperate, significant architectural components must standardize their interaction
The Nexus’ foundation is Scrum and the heart of the Nexus is 3 to 9 Professional Scrum teams.
There is no separate Nexus Integration Team Product Backlog; they work off of the same Product Backlog as everyone else They may develop utilities, scripts, etc. to help with integration
This module is about managing the Nexus, not about managing in general. The first few topics will appeal to PMs ($) and the last few are more technical
Adding practices/tools may initially slow you down
Adding practices/tools may initially slow you down
The reason a nexus is limited to 9 teams is point 1 (see Dunbar’s Number for specifics: http://en.wikipedia.org/wiki/Dunbar%27s_number) If you haven’t experienced this then you shouldn’t be teaching this Scaled Scrum teams of this size are built on the foundations of Professional Scrum at each individual single team
10,000 google developers check in to trunk every day. No branches. From a Google dev-op talk
Gunther Verheyen (email@example.com) is a seasoned Scrum professional. He works for Scrum.org, the home of Scrum. He represents Scrum co-creator Ken Schwaber and Scrum.org in Europe. Gunther ventured into IT and software development after graduating as Industrial Engineer in 1992. His Agile journey started with eXtreme Programming and Scrum in 2003. Years of dedication followed, of working with several teams and organizations, of using Scrum in diverse circumstances. Building on the experience gained, Gunther became the driving force behind some large-scale enterprise transformations. Gunther left consulting to partner with Ken Schwaber, Scrum co-creator, at Scrum.org in 2013. He is Professional Scrum trainer, directs the ‘Professional Scrum’ series and co-created the framework for Evidence-Based Management of Scrum.org. He shepherds classes, trainers, courseware and assessments for the programs of Professional Scrum Foundations (PSF), Professional Scrum Developer (PSD), Professional Scrum Master (PSM), and Professional Scrum Product Owner (PSPO). In 2013 Gunther published his highly appraised book “Scrum – A Pocket Guide,” a ‘smart travel companion’ to Scrum. Gunther lives in Antwerp (Belgium) with his wife Natascha, and their children Ian, Jente and Nienke. Find Gunther on Twitter as @ullizee or read more of his musings on Scrum on his personal blog, http://guntherverheyen.com/tag/scrum/.
Scrum Day Europe 2015 - Scaled Professional Scrum
by Scrum.org – Improving the Profession of Software Development
Scaled Professional Scrum
Focused. Effective. Viable.
Shepherding Professional Scrum
July 2, 2015