Software Scrum Patterns
 
Some Scrum patterns are applicable only to software. They are not part of the "Scrum core," because to put them there would limit Scrum's applicability to software. Scrum is broader than that. However, Jeff Sutherland maintains that these patterns are necessary to make Scrum work as a software framework, and he has never created a Scrum instance that lacked a single one of them.

Pattern Name Description Scrum Notes
WORK FLOWS INWARD Information should flow from customers through filtering roles to developers, not from managers downward [Jeff Sutherland blessed this 20/6/2008] XXX
ARCHITECT CONTROLS PRODUCT The architect sets the architectural tone and direction, and provides leadership. This is a best practice in an IT scrum, and without them, it’s broken [Jeff Sutherland 20/6/2008]
ARCHITECT ALSO IMPLEMENTS
Architects have to be in touch and have "street credentials" to do a good job.XXXX
DOMAIN EXPERTISE IN ROLES
Roles embody domain knowledgeXXX
GET ON WITH IT
Even if you don’t have a complete, comfortable plan to get started, take what you know and take it forward to build an initial product.Jeff maintains that this is one of the fundamental principles of early Scrum teams: to not wait around, but to move on and do something