Jump to content

Scrum pattern

Add links
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Beland (talk | contribs) at 16:18, 13 May 2015 (consolidate intro with "Further reading" list). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Example of Scrum patterns and usage

List of Scrum Patterns (non exhaustive)

Here are list of some free initiatives

Problem to solve: Multitasking that reduces productivity, introduces errors and frustrations

Problem: Many studies,[1][2][3][4][5] literature,[6] articles[7][8][9] and worldwide consulting firms,[10] including recent ones from Louisiana State University psychology Professor Emily Elliott[1] stresses the fact that multitasking of any kind reduces the productivity and/or increases rate of errors, thus generates unnecessary frustrations.

It has been estimated that $650 billion[11] a year is wasted in US businesses due to multitasking.

Solution: ScrumPlop addresses this issue using the "first-things-first" Scrum pattern, when the context of the problem is summarized, and references and studies that justifies the solution are given.

References

  1. ^ a b Elliott, Emily (18 September 2012). "Louisiana State University psychology professor". ITWorld. Louisiana State University. Retrieved 18 September 2012.
  2. ^ Robert Rogers; Stephen Monsell (1995). "The costs of a predictable switch between simple cognitive tasks". Journal of Experimental Psychology. pp. 124, 207–231.
  3. ^ Rubinstein, Joshua S.; Meyer, David E.; Evans, Jeffrey E. (2001). Executive Control of Cognitive Processes in Task Switching. Human Perception and Performance. Journal of Experimental Psychology.{{cite book}}: CS1 maint: multiple names: authors list (link)
  4. ^ "How Employers Can Make Us Stop Multitasking". Harvard Business Review. Retrieved May 17, 2012.
  5. ^ "Multitasking Gets You There Later". infoQ. June 2010.
  6. ^ Crenshaw, Dave (2008). The myth of multitasking : how doing it all gets nothing done (1st ed. ed.). San Francisco: Jossey-Bass. p. 144. ISBN 978-0470372258. {{cite book}}: |edition= has extra text (help)
  7. ^ RICHTEL, Matt (April 20, 2011). "Message to Executives: Stop Multitasking". The New York Times Blog.
  8. ^ Cherry, Kendra. "The Cognitive Costs of Multitasking". about.com : Cognitive Psychology.
  9. ^ "Multitasking kills productivity and that's bad for new business".
  10. ^ Derek Dean; Caroline Webb (January 2011). "Recovering from information overload". McKinsey Quarterly. McKinsey.
  11. ^ RICHTEL, Matt (14 June 2008). "Lost in E-Mail, Tech Firms Face Self-Made Beast". The New York Times. Retrieved June 14, 2008.

Further reading on software project management

Retrieved from "https://en.wikipedia.org/w/index.php?title=Scrum_pattern&oldid=662171255"