Traditional Project Management and Agile Project Management Approaches

2639 Words6 Pages

A project may be regarded as a sequence of tasks with a beginning and an end. It is delimited by time, resources and desired result as stated in Fox & Van Der Walt (2008, p.2). However, according to PMBOK Guide (2008), project management may be defined as the “application of knowledge, skills, tools and techniques to project activities to meet the project requirements”. According to Young, Brady & Nagle (2009, p.1) “A fruitful project is one that is accomplished within a defined budget and schedule ensuring that goals and objectives of the customer are met”. If project success can be defined in one sentence, then why do some projects fail? Projects fail for various reasons. In this essay, we will discuss both how Traditional Project Management and Agile Project Management Approaches contribute to the success of an IT project. The following sections are as follows. The Overview section provides a summary of the Traditional and Agile Project Management Approaches in terms of project success. The Critical Analysis section explains the key differences between the two above-mentioned Approaches and summarizes how Waterfall and Agile Project Management Approaches contribute to the success of a project. The Risk Management phase provides a clear explanation on the importance of risk management for a project to succeed. The Additional Topic is based on Cost Management. Lastly; the Conclusion provides a summary of the main results of the essay and suggests some recommendations. Overview: Traditional Project Management: Traditional Project Management (TPM) is one of the first Project Management Approaches that was developed. Also known as the Waterfall Model and discovered in 1970 by Dr. Royce Winston, the Waterfall Model is a seque... ... middle of paper ... ...ines.html#sec8. [Accessed 26 December 13]. Kendrick, T, 2009. Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project. 2nd ed. United States of America: AMACOM. Project Management Institute, 2008. A guide to Project Management Body of Knowledge (PMBOK Guide). 4th ed. Atlanta, United States of America: PMI book service center. Puri, C.P, 2009. Agile Management: Feature Driven Development. 1st ed. New Delhi, India: Global Indian Publications PVT Ltd. The Standish Group, 2011. Agile Process. Chaos Manifesto: The Laws of CHAOS and the CHAOS 100 Best PM Practices, [Online]. Pg.25. Available at:http://versionone.com/assets/img/files/ChaosManifest_2011.pdf [Accessed 26 December 2013]. Young, R.R, & Brady, S.M, & Nagle, D.C Jr, 2009. How to Save a Failing Project: Chaos to Control. 1st ed. United States of America: Management Concept.

Open Document