Scrum pattern
 | It has been suggested that this article be merged into Scrum (software development). (Discuss) Proposed since May 2015. |
 | This article may require cleanup to meet Wikipedia's quality standards. The specific problem is: fundamental misunderstanding of scrum and patterns, promotional in places, overbroad claims. (May 2015) |
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
- ^ a b Elliott, Emily (18 September 2012). "Louisiana State University psychology professor". ITWorld. Louisiana State University. Retrieved 18 September 2012.
- ^ Robert Rogers; Stephen Monsell (1995). "The costs of a predictable switch between simple cognitive tasks". Journal of Experimental Psychology. pp. 124, 207–231.
- ^ 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) - ^ "How Employers Can Make Us Stop Multitasking". Harvard Business Review. Retrieved May 17, 2012.
- ^ "Multitasking Gets You There Later". infoQ. June 2010.
- ^ 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) - ^ RICHTEL, Matt (April 20, 2011). "Message to Executives: Stop Multitasking". The New York Times Blog.
- ^ Cherry, Kendra. "The Cognitive Costs of Multitasking". about.com : Cognitive Psychology.
- ^ "Multitasking kills productivity and that's bad for new business".
- ^ Derek Dean; Caroline Webb (January 2011). "Recovering from information overload". McKinsey Quarterly. McKinsey.
- ^ 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
- Joshua H. Goodman (2009). "The Optimal Reference Guide: Why 70% of Government IT Projects Fail – Quality Project Management for Education Agencies" (PDF). Retrieved 2015-05-13.
- Michael Krigsman (2009-01-14). "Study: 68 percent of IT projects fail". ZDNet. Retrieved 2015-05-13.
- Robert Frese (2003-12-16). "PROJECT SUCCESS AND FAILURE: WHAT IS SUCCESS, WHAT IS FAILURE, AND HOW CAN YOU IMPROVE YOUR ODDS FOR SUCCESS?". University of Missouri-St. Louis. Retrieved 2015-05-13.
- Joseph Gulla (February 2012). "Seven Reasons IT Projects Fail". IBM Systems Magazine. Retrieved 2015-05-13.