Wait a second!
More handpicked essays just for you.
More handpicked essays just for you.
Critical analysis of the Agile approach to project management
Don’t take our word for it - see why 10 million students trust us with their essay needs.
Beginnings of Agile
Agile project management is widely used by Information Technology professionals for software development. It was not always this way. In the earlier stages of development the norm was to use “heavy” methodologies such as Waterfall or Spiral for software development. These other methods were criticized for having too many regulations and being unable to adapt to project changes. People understood these methods were flawed because IT teams were not delivering software that met the agreed-upon budgets, schedules, or costs. In fact “The DoD (Department of Defense), noted that, of the $35.7 billion spent by the organization in 1995 for software, only 2 percent of the software was usable as delivered.” (Freedman). This led IT professionals to try out new ways of managing their projects and used the internet to share their experiences with each other. Two more common agile methods, Scrum and Extreme Programing, were developed in the mid 1990’s, but at that time there were not yet any guidelines that detailed what Agile was. In 2001 seventeen software developers meet in Utah to discuss the new ways of managing software projects and published the Agile Manifesto for Software Development.(The Agile Alliance). The Manifesto underlined common values and principals of all agile projects and led to what Agile is today. Agile Project Management is a lightweight method for software development projects. This means it has fewer rules and regulations to follow; instead, there are guidelines and principles that can help guide the project team along the way. This is why there are many different implantation methods, but not all will fit every project. Agile is meant to be tailored to every different project which means every ma...
... middle of paper ...
...are-Development-Benefits/
http://www.dummies.com/how-to/content/ten-benefits-of-agile-project-management.html
The Agile Samurai by Jonathan Rasmusson
Agile Web Design and Development Lecture and Notes
Cervone, Frank H., “Understanding Agile Programming Methods using Scrum” OCLC Systems and Services: International Digital Library Perspectives. 27.1 (2010): 18-22. Print.
Rasmusson, Jonathan. The Agile Samurai. The Pragmatic Bookshelf, 2010. Print
Tolbert, Mark. “Agile Project Management vs. PMBOK® Guide and EVM- ‘Revolution or Evolution?’” PMI Washington DC. January 2012. Web. 4 December 2014.
Freedman, Rick. "The roots of agile project management." Tech Republic. CBS, 16 July 2009. Web. 12 Nov. 2014.
The Agile Alliance. Manifesto for Agile Software Development. Ed. Ward Cunningham. N.p., 2001. Web. 12 Nov. 2014. .
Agile project management is an iterative approach to the planning and monitoring of project processes. Agile projects are conducted in smaller tranches called iterations with each of these iterations closely reviewed and critiqued by the project team (employees, representatives of the clients etc.). The knowledge gained from this process is then used to ascertain the next steps of the
Wells, D. (2009). Agile Software Development: A gentle introduction. In Agile Process. Retrieved April 20, 2014, from http://www.agile-process.org.
Graham, R. J. & Randall, L., Creating an Environment for Successful Projects: The Quests to Manage Project Management, second ed. San Francisco: Jossey-Bass, 65-113, 2003.
Gray, Clifford F.; Larson, Erik W., Project Management – The Managerial Process, Copyright © 2001 by The McGraw-Hill Companies, Inc.
Jugdev, K. (2012). Learning from Lessons Learned: Project Management Research Program. American Journal of Economics and Business Administration , 4(1), 13-22.
Gray, C., Larson, E. (2008). Project Management: The managerial Process. New York, NY: The McGraw-Hill Companies Inc.
He reviews the difficulties that lie with changes, implementation, communicating agile to general managers, the risk of false agile, decline to bureaucracy, and resolving persistent conflict of goals between teams at all organizational levels, and the way the organization runs from the top (Stephen Denning,
Project Management Institute . (2008). A Guide to the Project Management body Of Knowledge. Newton Square, PA: Project Management Institute, Inc.
PMBOK, (2013). A guide to the project management body of knowledge : (PMBOK guide). 5th ed. Newtown Square, PA: Project Management Institute, Inc..
Scrum is basically a framework for agile development. Scrum is a process that is used most of the time during complex projects in software development. It is also a simple yet affective way to manage work. The strategy in Scrum is to divide members into a team and have them work together to achieve a common goal or project. Scrum provokes communication between the members of the teams. This communication is imperative to the success of the project.
In the late 1990s, the word “agile"[2] in the field of computer system mean either” ready ability to move with quick easy grace “or “able to move your body quickly and easily”. However, this word starts to have another meaning in February, 2001. A group of seventeen software developer gathered at Snowbird, Utah and determine agile software development. Agility is a common ground where they can agree, though each participant has his own ideas about how to build high-quality software. Common ground agreement results fro...
Schrodl, Holger and Wind, Stefan, "Adoption of SCRUM for Software Development Projects: An Exploratory Case Study from the ICT Industry" (2011). AMCIS 2011 Proceedings - All Submissions. Paper 256.
ScottAmbler. (2010, May 31). Agility@Scale: Strategies for Scaling Agile Software Development. Retrieved from https://www.ibm.com/: https://www.ibm.com/developerworks/community/blogs/ambler/entry/principles_lean_software_development?lang=en
Abstract Agile Methodology provides us a platform to develop software in an efficient and effective manner. Agile Methodology provides more of a people oriented approach rather than a process oriented. Nowadays most of the Software development Organization starts following agile methodology to gain customer satisfaction and to improve the quality of the software. Extreme programming and SCRUM gain a more popularity which made agile approaches used more widely. In this paper there is comparison between the traditional software development methods with agile method.
Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.