Project management software

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Project management software has the capacity to help plan, organize, and manage resource tools and develop resource estimates. Depending on the sophistication of the software, it can manage estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, quality management and documentation or administration systems. Today, numerous PC & browser based project management software and contract management software solutions exist, and are finding applications in almost every type of business.


The origins of project management software are rooted in the 1950s when Dupont Chemical collaborated with mainframe computer maker Remington Rand (Univac) to devise the Critical Path Method of network scheduling (CPM). This method was tested in 1958 with the construction of a major new chemical plant. In parallel, the US Navy working together with Lockheed Aerospace devised the automated Project Evaluation Review Technique (PERT) for the Polaris Missile program that ran on the IBM mainframe. Mainframe and Mini computers dominated the project management software arena until the early 1980s when PC computers began to proliferate across business and government circles alike.[1]

Tasks and activities[edit]


One of the most common project management software tool types is scheduling tools. Scheduling tools are used to sequence project activities and assign dates and resources to them. The detail and sophistication of a schedule produced by a scheduling tool can vary considerably with the project management methodology used, the features provided and the scheduling methods supported. Scheduling tools may include support for:[2]

Providing information[edit]

Project planning software can be expected to provide information to various people or stakeholders, and can be used to measure and justify the level of effort required to complete the project(s). Typical requirements might include:

  • Overview information on how long tasks will take to complete.
  • Early warning of any risks to the project.
  • Information on workload, for planning holidays.
  • Evidence.
  • Historical information on how projects have progressed, and in particular, how actual and planned performance are related.
  • Optimum utilization of available resource.
  • Cost maintenance.
  • Collaboration with each teammates and customers.
  • Instant communication to collaborators and customers.



Project management software has been implemented as a program that runs on the desktop of each user. Project management tools that are implemented as desktop software are typically single-user applications used by the project manager or another subject matter expert, such as a scheduler or risk manager..


Project management software has been implemented as web application to be accessed using a web browser. This may also include the ability to use a smartphone or tablet to gain access to the application. Software as a Service (SaaS) is also web-based and has become a common delivery model for many business applications, including Project Management, Project Management Information System (PMIS) and Project Portfolio Management (PPM). SaaS is typically accessed by users using a thin client via a web browser.


A personal project management application is one used at home, typically to manage lifestyle or home projects. There is considerable overlap with single user systems, although personal project management software typically involves simpler interfaces. See also non-specialised tools below.

Single user[edit]

A single-user system is programmed with the assumption that only one person will ever need to edit the project plan at once. This may be used in small companies, or ones where only a few people are involved in top-down project planning. Desktop applications generally fall into this category.


A collaborative system is designed to support multiple users modifying different sections of the plan at once; for example, updating the areas they personally are responsible for such that those estimates get integrated into the overall plan. Web-based tools, including extranets, generally fall into this category, but have the limitation that they can only be used when the user has live Internet access. To address this limitation, some software tools using client–server architecture provide a rich client that runs on users' desktop computer and replicates project and task information to other project team members through a central server when users connect periodically to the network. Some tools allow team members to check out their schedules (and others' as read only) to work on them while not on the network. When reconnecting to the database, all changes are synchronized with the other schedules.


A common problem in project management is a difficulty with both viewing and understanding large amounts of fluctuating project data.[3] To tackle this, some project management software utilize information visualization, so that users can more easily find, analyze and make changes to their data.[4] To avoid information overload,[5] the visualization mantra of “overview first, zoom and filter, then details on demand” is often followed.[6]

See also[edit]


  1. ^ History of the Critical Path Method by Maria Kielmas, Demand Media
  2. ^ Nevogt, Dave (17 September 2013). "31 Project Management Solutions". Hubstaff. Retrieved 3 November 2013. 
  3. ^ "My Problems with Project Management Software | Marketing Technology". Marketing Technology. Retrieved 2016-01-08. 
  4. ^ "Targetprocess 3 Launches to Bring Visualization and Flexibility to Project Management". Retrieved 2016-01-08. 
  5. ^ Wurman, From the book "Information Anxiety" by Richard Saul Wurman Copyright 1989 by Richard Saul (1989-01-22). "INFORMATION OVERLOAD : What to Do When Anxiety Cripples You". Los Angeles Times. ISSN 0458-3035. Retrieved 2016-01-08. 
  6. ^ Shneiderman, Ben (1996). "The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations". University of Maryland, Human Computer Interaction Laboratory. 

Further reading[edit]

  • Project Time Management. (2008). In A guide to the project management body of knowledge (PMBOK guide) (4th ed., p. 145). Newtown Square, Pa: Project Management Institute. ISBN 978-1933890517