Software Project Management Observes: Fiasco V/S Victory
DOI:
https://doi.org/10.21015/vtse.v12i2.500Abstract
A study on successful and un-successful about 210 large software (development) projects from around the world between February 1995 and December 2017 has been presented in this review paper. All these projects involved on mass level that completed on time with their scheduled expense, and time frame estimates in development of those are getting late as defined, much expensive as decide, or were get delayed or close without its completion, major seven hurdles were noted: un sufficient project planning, un sufficient cost estimating, un sufficient measurements, un sufficient milestone tracking, un sufficient change control, and un sufficient -quality control, Poor Coronation and communication. After detail study on past reviews on these hurdles in project management, in this review paper we have presented a short overview of success and failure reasons/causes/possibilities of all those seven factor/ hurdles are noted. Maybe the clearest aspect of these major problems is linked with project management rather than technical resource. Two occupied ideas combine which are no proper excellence regulator are the huge funder for the rates, and late time and unfair plan organization have number of prospective reason of insufficient excellence actions.References
C. Jones, “Software project management practices: Failure versus success,” CrossTalk J. Def. Softw. Eng., vol. 17, no. 10, pp. 5–9, 2004.
C. Jones, Patterns of software system failure and success. Itp New Media, 1996.
C. Jones, Software Assessments, Benchmarks, and Best Practices. Boston, MA, USA: Addison-Wesley Longman Publishing Co., Inc., 2000.
K. Ewusi-Mensah, Software development failures. Mit Press Cambridge, MA, 2003. DOI: https://doi.org/10.7551/mitpress/6322.001.0001
R. L. Glass, Software runaways: monumental software disasters. Prentice-Hall, Inc., 1998.
I. Standish Group International, Chaos Chronicles: Version 3.0. Standish Group International, 2003.
E. Yourdon, “Death March: The Complete Software Developer’s Guide to Surviving,” Mission Impos. Proj. Prentice-Hall, Inc, Up. Saddle River, NJ, 1997.
S. H. Kan, Metrics and models in software quality engineering. Addison-Wesley Longman Publishing Co., Inc., 2002.
C. Jones, “Sizing up software,” Sci. Am. Mag., vol. 279(6), 1998. DOI: https://doi.org/10.1038/scientificamerican1298-104
C. C. Jones, Software quality: Analysis and guidelines for success. Thomson Learning, 1997.
R. A. Radice, High quality low cost software inspections. Paradoxicon Publishing, 2001.
K. E. Wiegers, Peer reviews in software: A practical guide. Addison-Wesley Boston, 2002.
S. Rajkumar, “Art of communication in project management,” in PMI® Research Conference: Defining the Future of Project Management, Washington, DC. Newtown Square, PA: Project Management Institute., 2010
Downloads
Published
How to Cite
Issue
Section
License
Authors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License (CC-By) that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access).
This work is licensed under a Creative Commons Attribution License CC BY
