Scrum pattern: Difference between revisions

Content deleted Content added

Inline

Revision as of 02:16, 7 December 2012

A scrum pattern represents a knowledge that has been identified through large empirical studies [todo: provide example of buddies that collects data worldwide].
By analyzing the ingredients that make a project fail or succeed by collecting and analyzing data worldwide (ranging from small to large projects), a scrum pattern helps you :

identify and provide a name to a recurring problem within your team
offer a solution that is known to work with other team
use and deploy a given pattern, along with its potential limitations and sometimes with some related patterns

By formalizing a problem and providing a solution that has been tested across multiple organizations, a team could significantly increase their productivity, while keeping the individuals happy to work as a whole and self-organized team (i.e. with no hierarchy threatening people and assign tasks to individuals).

In October 2011 Ken Schwaber and Jeff Sutherland released "The Scrum Guide, The Definitive Guide to Scrum: The Rules of the Game" ^[1]. It is a simplified version of the previous guides, so that only the core Scrum is present. The two creators of Scrum made this framework available for free to the community (but they still remain the owner) so that additional advices, improvements and initiatives could be launched. Since then, various communities have further developed scrum patterns^[2]. Names of the same pattern may vary depending on which organization.

"Scrum pattern" refers to both Scrum Scrum (development) that is an agile software development and also to Software design pattern. Similarly to Software design pattern, we could find Scrum Anti-pattern, which gathers a list of all bad practices that guaranties either the failure of a projects or the generation of lots of frustrations.

When you want to move toward agility either on a new project or an existing one, a scrum pattern helps identify and communicate the change needed to the development team and the management. Instead of picking-up randomly any Scrum artifact and implement it, the usage of Lean software development will help identifying the top priority Kaizen (i.e. small change required for improvements). As a result, one could quickly increase a team's velocity in a structured way with low efforts but high Return on investment. Once this small but efficient improvement is in place, go to the next Scrum pattern on the list.

For example, when a development team has identified that the most important impediment that generates frustrations in their job is the constant interruption of their work (either from management or any disruption), which in turn forces them to do unplanned multi-tasking (which as been proven to slower productivity Cite error: The <ref> tag has too many names (see the help page).), a ScrumMaster could start to implement the scrum pattern called "Interrupt Buffer"^[3]. Note: The name of a given scrum pattern could vary depending its "inventors".

References

^ "The Scrum Guide" (PDF). p. 1. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
^ "Scrum Patterns, by unlocking-potential".
^ "Interrupt Buffer".

Videos

Agile Product Ownership in a Nutshell, by Henrik Kniberg http://www.youtube.com/watch?v=502ILHjX9EE

[1] "The Scrum Guide" (PDF). p. 1. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)

[autogenerated0-2] "Scrum Patterns, by unlocking-potential".

[autogenerated1-3] "Interrupt Buffer".

[1]

[2]

[3]

@@ Line 10: / Line 10: @@
 <br />
-In October 2011 Ken Schwaber and Jeff Sutherland released "The Definitive Guide to Scrum: The Rules of the Game" (http://www.scrum.org). It is a simplified version of the previous guides, so that only the core Scrum is present. The two creators of Scrum made this framework available for free to the community (but they still remain the owner) so that additional advices, improvements and initiatives could be launched.
+In October 2011 Ken Schwaber and Jeff Sutherland released "The Scrum Guide, The Definitive Guide to Scrum: The Rules of the Game" <ref>{{cite web |url= http://www.scrum.org/Portals/0/Documents/Scrum%20Guides/Scrum_Guide.pdf |title= The Scrum Guide |coauthors= Ken Schwaber, Jeff Sutherland | page= 1}}</ref>. It is a simplified version of the previous guides, so that only the core Scrum is present. The two creators of Scrum made this framework available for free to the community (but they still remain the owner) so that additional advices, improvements and initiatives could be launched.
-Since then, various communities have further developed scrum patterns (eg. http://unlocking-potential.de/scrum). Names of the same pattern may vary depending on which organization.<br />
+Since then, various communities have further developed scrum patterns<ref name=autogenerated0>{{cite web|url=http://unlocking-potential.de/scrum/|title=Scrum Patterns, by unlocking-potential}}</ref>. Names of the same pattern may vary depending on which organization.<br />
 "Scrum pattern" refers to both Scrum [[Scrum (development)]] that is an [[agile software development]] and also to [[Software design pattern]]. Similarly to Software design pattern, we could find Scrum [[Anti-pattern]], which gathers a list of all bad practices that guaranties either the failure of a projects or the generation of lots of frustrations. <br /><br />
@@ Line 17: / Line 17: @@
 When you want to move toward agility either on a new project or an existing one, a scrum pattern helps identify and communicate the change needed to the development team and the management. Instead of picking-up randomly any Scrum artifact and implement it, the usage of [[Lean software development]] will help identifying the top priority [[Kaizen]] (i.e. small change required for improvements). As a result, one could quickly increase a team's velocity in a structured way with low efforts but high [[Return on investment]]. Once this small but efficient improvement is in place, go to the next Scrum pattern on the list.<BR /><BR />
-For example, when a development team has identified that the most important impediment that generates frustration in their job is the constant interruption of their work (either from management or any disruption), which in turn forces them to do unplanned multi-tasking (which as been proven to slower productivity, eg Dr. Jan Yager, who has a Ph.D. in sociology: "Work Less, Do More:
+For example, when a development team has identified that the most important impediment that generates frustrations in their job is the constant interruption of their work (either from management or any disruption), which in turn forces them to do unplanned multi-tasking (which as been proven to slower productivity
-The 14-Day Productivity Makeover"), a first improvement that can be done is to follow that scrum pattern "Interrupt Buffer" (cf. http://unlocking-potential.de/2011/07/13/scrum-pattern-interrupt-buffer) . Note: The name of a given scrum pattern could vary depending its "inventors".
+<ref Dr. Jan Yager Ph.D. in sociology>{{cite book |last1= Yager |first1= Jan |title=Work Less, Do More: The 14-Day Productivity|publisher=Sterling |date= |accessdate=September 2, 2008}}</ref>), a ScrumMaster could start to implement the scrum pattern called "Interrupt Buffer"<ref name=autogenerated1>{{cite web|url=http://unlocking-potential.de/2011/07/13/scrum-pattern-interrupt-buffer|title=Interrupt Buffer}}</ref>. Note: The name of a given scrum pattern could vary depending its "inventors".
+<BR /><BR />
+== References ==
+{{Reflist|colwidth=30em}}
+<BR /><BR />
+==Further reading==
+* http://jeffsutherland.com/ScrumPapers.pdf<BR />
+* Example of small improvements with high value added: Using Story points instead of Hours http://scrum.jeffsutherland.com/2010/04/story-points-why-are-they-better-than.html
+<BR />
+<BR />
+== Videos==
+* Agile Product Ownership in a Nutshell, by Henrik Kniberg http://www.youtube.com/watch?v=502ILHjX9EE
+<br />
+<br />