On Tuesday, Jeff Sutherland and I will be celebrating the twentieth anniversary of Scrum’s first public appearance.
Those twenty years were my warm up for the next twenty, when I will focus on improving our professionalism. Specifically, I will be done when all Scrum teams deliver “done”, potentially shippable, in operations and usable, increments of software functionality. You can follow my progress at Scrum.org..
Martin Fowler famously described the problem of undone increments at the end of Sprints as “flaccid software development.” This problem of delivering incomplete increments has haunted Scrum since its inception, Undone increments have led to unpredictable stabilization phases, as well as adding to technical debt. The persistence of undone increments has undercut our professionalism and relations with our customers.
As software has become an intrinsic part of our society, as continuous delivery and new technologies such as containers and micro services become mainstream, this problem becomes more pressing.
I, Scrum.org, and our community have prioritized this problem. In 2016, we will start developing and delivering SDKs (Scrum Development Kits) that describe done increments. The SDKs will describe how to develop and put done increments into operations (DevOps). These SDKs will support different development sets, including open source. The primary architectural options that reduce dependencies and technical debt will be supported. The SDKs will address small team and scaled (Nexus, Nexus+) development.
More early next year.