Determining When Simplified Agile Project Management Is Right for Small Teams

Abstract: Agile project management was developed in the information technology industry as a way of increasing efficiency, productivity, and responsiveness to customers. Many projects with highly uncertain scopes, tasks, task precedence relationships, and/or resources are difficult to handle with traditional planning tools. Better planning in such cases does not lead to better outcomes. An agile approach that maximizes productivity and quality within the resource and time constraints can be superior whether or not the project is IT related. This article addresses when a simplified agile project management methodology can be appropriate for small teams both in academia and in industry.

[1]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[2]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[3]  Kristian Rautiainen,et al.  Integrating Testing and Implementation into Development , 2004 .

[4]  Mark C. Layton,et al.  Agile Project Management For Dummies , 2012 .

[5]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[6]  Hany Wells,et al.  How Effective Are Project Management Methodologies? An Explorative Evaluation of Their Benefits in Practice , 2012 .

[7]  Ian Sommerville,et al.  Integrated requirements engineering: a tutorial , 2005, IEEE Software.

[8]  Laurie Williams,et al.  Extreme Programming and Agile Methods — XP/Agile Universe 2002 , 2002, Lecture Notes in Computer Science.

[9]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[10]  A. Cockburn,et al.  Agile Software Development: The People Factor , 2001, Computer.

[11]  H. D. Benington,et al.  Production of Large Computer Programs , 1983, Annals of the History of Computing.

[12]  Chris Sims,et al.  Scrum: a Breathtakingly Brief and Agile Introduction , 2012 .

[13]  Carl B Traylor.  Project Management: A Systems Approach to Planning, Scheduling, and Controlling , 2014 .

[14]  Jack R. Meredith,et al.  Project Management: A Managerial Approach , 1989 .

[15]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

[16]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[17]  Laurie A. Williams,et al.  Agile software development: it's about feedback and change , 2003, Computer.

[18]  Brian Hobbs,et al.  Contextualized Project Management Practice: A Cluster Analysis of Practices and Best Practices , 2013 .

[19]  Barry W. Boehm,et al.  Empirical Findings in Agile Methods , 2002, XP/Agile Universe.

[20]  W BoehmBarry.  A Spiral Model of Software Development and Enhancement , 1988 .

[21]  Michele Sliger,et al.  The Software Project Manager's Bridge to Agility , 2008 .

[22]  Agile Manifesto,et al.  Manifesto for Agile Software Development , 2001 .

[23]  Robert K. Wysocki,et al.  Effective Project Management: Traditional, Adaptive, Extreme , 2000 .