Every Sprint in Scaled Professional Scrum requires a completed, ready to ship increment of functionality. The ubiquitous “definition of done” spells out the characteristics of such an increment. The end result should include software that has: Presence of valuable functionality for…
I will be conducting a Nexus workshop in Boston on November 17-18, with Richard Hundhausen and Rob Maher, based on the Nexus Guide. Of interest to many, SDK, API architectures, and remediation Scrumbles, and DevOps. Many Scrum teams deliver a “done”, potentially shippable increment…
Scaled Professional Scrum is based on unit of development called a Nexus. The Nexus consists of up to 10 Scrum teams, the number depending on how well the code and design are structured, the domains understood, and the people organized.…
I’ve been working with people who have actually made Scrum scale for large projects and product initiatives over the last twenty years. Our smallest project experience was 3 teams, average 25 teams, and largest was 80 teams. We abstracted a…
Creating software with Scrum is difficult. Creating one integrated piece of software with multiple Scrum teams is a managerial and technical drama, requiring sophisticated techniques, tools, and collaboration. In my last two blogs, I shared my opinions about the skills…
Scrum teams are cross functional. Every person on the team has skills and experience that they contribute, turning the requirements into the best possible increment possible for them. One never knows when an insight, a memory, a skill rarely used…
Find out with a short test? A single instance of Scrum has one Scrum Team that works from one Product Backlog. The team sprints against the selected Product Backlog items and creates an increment of potentially shippable, or usable, functionality…