Editing Project management software (section)

==History==

===Predecessors===
The first historically relevant year for the development of project management software was 1896, marked by the introduction of the Harmonogram. Polish economist [[Karol Adamiecki]] attempted to display task development in a floating chart and laid the foundation for project management software as it is today.<ref>[http://projectmanagementhistory.com/The_Harmonogram.html "The Harmonogram"], ''projectmanagementhistory.com'',</ref> In 1912, [[Henry Gantt]] replaced the Harmonogram with the more advanced [[Gantt chart]], a scheduling diagram that broke ship design tasks down for the purposes of Hoover Dam in early 1931.{{citation needed|date=March 2018}} Today's Gantt charts are almost the same as their original counterparts and are a part of many project management systems.

===Emergence of the term "project management" and modernized techniques===
The term ''[[project management]]'' was not used prior to 1954 when [[United States Air Force|US Air Force]] General [[Bernard Adolph Schriever]] introduced it for military purposes. In the years to follow, project management gained relevance in the business world — a trend that had a lot to do with the formation of the [[AACE International|American Association of Engineers]] AACE (1956), and Rang and DuPont's Critical Path Method, which has been used to calculate project duration ever since 1957.<ref>[http://www.aacei.org/aboutUs/ "About UsAACE International: The Authority for Total Cost Management"], ''aacei.org'',</ref>

The trend is also related to the appearance of the [[Program evaluation and review technique|Program Evaluation Review Technique]] (PERT) in 1958. PERT advanced project monitoring, enabling users to simultaneously monitor tasks, evaluate their quality, and estimate the time needed to accomplish each of them. Like [[Gantt chart]]s and CPM, PERT was invented for military purposes, this time for the US Navy Polaris missile submarine program.<ref>[http://www.referenceforbusiness.com/encyclopedia/Per-Pro/Program-Evaluation-and-Review-Technique-PERT.html "PROGRAM EVALUATION AND REVIEW TECHNIQUE (PERT)"], ''referenceforbusiness.com'',</ref>

In 1965, there was a new improvement in project management technology. The [[United States Department of Defense|US Department of Defense]] presented the [[work breakdown structure]] (WBS) to dissolve projects into even smaller visual units, organizing them in a hierarchical tree structure. WBS was an inspiration for [[Winston W. Royce|Winston Royce]]’s Waterfall Method (1970) where management phases are organized in a way that doesn’t allow a new task to begin before the previous ones are completed.<ref>[http://www.dau.mil/pubscats/pubscats/pm/articles02/lit-ma2.pdf "“Breaking Down” The Work Breakdown Structure"] {{webarchive|url=https://web.archive.org/web/20161221132113/http://www.dau.mil/pubscats/PubsCats/PM/articles02/lit-ma2.pdf |date=2016-12-21 }}, ''dau.mil'',</ref> 

===The first project management products and associations===
In the period between 1965 and 1969, two of the leading project management associations were formed: the International Project Management Association (IPMA) in Europe, and the [[Project Management Institute]] (PMI) which trains project management professionals and issues certificates. With businesses shifting towards technology-based and paperless methods, the first project management systems started to emerge.<ref>Sandro Azzopardi, [https://www.projectsmart.co.uk/evolution-of-project-management.php "THE EVOLUTION OF PROJECT MANAGEMENT"], ''projectsmart.co.uk'',</ref> [[Oracle Corporation|Oracle]] and [[Artemis (software)|Artemis]] launched their project managers in 1977, while Scitor Corporation did the same in 1979.<ref>Sandro Azzopardi, [http://www.oracle.com/us/corporate/history/index.html "Oracle's History: Innovation, Leadership, Results"], ''oracle.com'',</ref><ref>[http://www.computinghistory.org.uk/det/14416/Metier-Artemis/ "Metier Artemis"], ''computinghistory.org.uk'',</ref> Many improvements followed in the upcoming decades. In 1986, [[Carnegie Mellon University]]’s [[Software Engineering Institute]] introduced capability maturity software, a five-level project management method for rapidly maturing processes, while in 1988, users were introduced to earned value management which added processes’ scope and cost to the schedule.<ref>[https://www.sei.cmu.edu/reports/93tr024.pdf "Technical Report"], ''sei.cmu.edu'',</ref> The trend continued with [[PRINCE2]] (1996) which increased the number of processes to seven, because of which developers considered designing products for managing complex projects. In 2001, they adopted the [[Agile management|Agile project management]] concept and focused on adaptive planning and flexible response to changes. In 2006, users were already able to trigger [[total cost management]], a framework that helps control and reduce costs in project management.<ref>[http://www.aacei.org/tcmfree/tcmframework_webedition.pdf "TOTAL COST MANAGEMENT FRAMEWORK"] {{webarchive|url=https://web.archive.org/web/20160530211731/http://www.aacei.org/tcmfree/tcmframework_webedition.pdf |date=2016-05-30 }}, ''aacei.org'',</ref>