Outline of project management

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

The following outline is provided as an overview of and topical guide to project management:

Project management – discipline of planning, organizing, securing, managing, leading, and controlling resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables), undertaken to meet unique goals and objectives,[1] typically to bring about beneficial change or added value. The temporary nature of projects stands in contrast with ongoing business operations.[2]

What type of thing is project management?[edit]

Project management can be described as all of the following:

  • Management – in business and human organization activity is simply the act of getting people together to accomplish desired goals. Management comprises planning, organizing, staffing, leading or directing, and controlling an organization (a group of one or more people or entities) or effort for the purpose of accomplishing a goal.
    • Management process – is a process of planning and controlling the performance or execution of any type of activity.
  • Process – ongoing collection of activities, with inputs, outputs and the energy required to transform inputs to outputs.
  • Project – A temporary endeavor undertaken to create a unique product, service, or result.[3]

Branches of project management[edit]

Project management by domain[edit]

  • Construction project management concepts
    • Construction – in the fields of architecture and civil engineering, is a process that consists of the building or assembling of infrastructure. Far from being a single activity, large scale construction is a feat of multitasking. Normally the job is managed by the project manager and supervised by the construction manager, design engineer, construction engineer or project architect.
    • Architectural engineering
    • Virtual Design and Construction – (VDC) is the use of integrated multi-disciplinary performance models of design-construction projects, including the Product (i.e., facilities), Work Processes and Organization of the design - construction - operation team in order to support explicit and public business objectives.
  • Software project management concepts
    • Software engineering – is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.[4]
    • Software development
      • Agile software development – is a set of principles about how software should be developed based on an rapidly iterative agile way of working in contrast to many previous software development methodologies.[5]
    • Capability Maturity Model – (CMM) in software engineering is a model of the maturity of the capability of certain business processes. A maturity model can be described as a structured collection of elements that describe certain aspects of maturity in an organization, and aids in the definition and understanding of an organization's processes.
    • Dynamic Systems Development Method – (DSDM) is a software development methodology originally based upon the Rapid Application Development methodology. DSDM is an iterative and incremental approach that emphasizes continuous user involvement.
    • Unified Process – The Unified process is a popular iterative and incremental software development process framework. The best-known and extensively documented refinement of the Unified Process is the Rational Unified Process (RUP).

Types of projects[edit]

Project management approaches[edit]

Related fields[edit]

Fields concerned primarily with projects[edit]

History of project management[edit]

Project management processes[edit]

Project management process – is the management process of planning and controlling the performance or execution of a project. Typical phases include:

  1. Initiation
  2. Planning and design
  3. Execution and construction
  4. Monitoring and controlling systems
  5. Completion

General project management concepts[edit]

  • Dependency in a project network is a link amongst a project's terminal elements.
  • Duration of a project's terminal element is the number of calendar periods it takes from the time the execution of element starts to the moment it is completed.
  • Float in a project network is the amount of time that a task in a project network can be delayed without causing a delay to subsequent tasks and or the project completion date.
  • Hammock activity – is a schedule (project management) or project planning term for a grouping of subtasks that "hangs" between two end dates it is tied to. (Or the two end-events it is fixed to.)
  • Product breakdown structure – (PBS) in project management is an exhaustive, hierarchical tree structure of components that make up an item, arranged in whole-part relationship.
  • Product description – in project management is a structured format of presenting information about a project product
  • Project Management Triangle – is a model of the constraints of project management.
  • Resources in project management terminology are required to carry out the project tasks. They can be people, equipment, facilities, funding, or anything else capable of definition (usually other than labour) required for the completion of a project activity.
  • Scope of a project in project management is the sum total of all of its products and their requirements or features.
  • Tasks in project management are activity that needs to be accomplished within a defined period of time.
  • Work in project management is the amount of effort applied to produce a deliverable or to accomplish a task (a terminal element).
  • Vertical slice – is a type of milestone, benchmark, or deadline, with emphasis on demonstrating progress across all components of a project.
  • Work package – is a subset of a project that can be assigned to a specific party for execution. Because of the similarity, work packages are often misidentified as projects.
  • Workstream – is a set of associated activities, focused around a particular scope that follow a path from initiation to completion.

Project management procedures[edit]

  • Aggregate planning – is an operational activity which does an aggregate plan for the production process, in advance of 2 to 18 months, to give an idea to management as to what quantity of materials and other resources are to be procured and when, so that the total cost of operations of the organization is kept to the minimum over that period.
  • Allocation – is the assignment of available resources in an economic way.
  • Budgeting
    • Budget – generally refers to a list of all planned expenses and revenues.
    • Budgeted cost of work performed – (BCWP) measures the budgeted cost of work that has actually been performed, rather than the cost of work scheduled.
    • Budgeted cost of work scheduled – (BCWS) the approved budget that has been allocated to complete a scheduled task (or Work Breakdown Structure (WBS) component) during a specific time period.
  • Constructability – is a project management technique to review the construction processes from start to finish during pre-construction phrase. It will identify obstacles before a project is actually built to reduce or prevent error, delays, and cost overrun.
  • Cost engineering – is the area of engineering practice where engineering judgment and experience are used in the application of scientific principles and techniques to problems of cost estimating, cost control, business planning and management science, profitability analysis, project management, and planning and scheduling."[8]
  • Critical path method – (CPM) is a mathematically based modeling technique for scheduling a set of project activities, used in project management.
  • Earned value management – (EVM) is a project management technique for measuring project progress in an objective manner, with a combination of measuring scope, schedule, and cost in a single integrated system.
    • Earned schedule – (ES) is an extension to earned value management (EVM), which renames two traditional measures, to indicate clearly they are in units of currency or quantity, not time.
  • Estimation in project management is the processes of making accurate estimates using the appropriate techniques.
  • Graphical Evaluation and Review Technique (GERT) – is a network analysis technique that allows probabilistic treatment of both network logic and activity duration estimated.
  • HERMES is a Project Management Method developed by the Swiss Government, based on the German V-Modell. The first domain of application was software projects.
  • Kickoff meeting – is the first meeting with the project team and the client of the project.
  • Linear scheduling method – (LSM) is a graphical scheduling method focusing on continuous resource utilization in repetitive activities. It is believed that it originally adopted the idea of Line-Of-Balance method.
  • Program Management – is the process of managing multiple ongoing inter-dependent projects. An example would be that of designing, manufacturing and providing support infrastructure for an automobile manufacturer.
  • Project accounting – Is the practice of creating financial reports specifically designed to track the financial progress of projects, which can then be used by managers to aid project management.
  • Project Cost Management A method of managing a project in real-time from the estimating stage to project control; through the use of technology cost, schedule and productivity is monitored.
  • Project planning – is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment.[9]
  • Task is part of a set of actions which accomplish a job, problem or assignment.

Project management tools[edit]

  • Event chain diagram – : diagram that show the relationships between events and tasks and how the events affect each other.
  • Gantt chart – is a type of bar chart that illustrates a project schedule. It illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements comprise the work breakdown structure of the project.
  • Project plan – is a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summary or detailed.[10]
    • Integrated Master Plan – (IMP) is an event-based, top level plan, consisting of a hierarchy of Program Events.
  • Project Management Simulators – are computer-based tools used in project management training programs. Usually, project management simulation is a group exercise. The computer-based simulation is an interactive learning activity.
  • Project management software – is a type of software, including scheduling, cost control and budget management, resource allocation, collaboration software, communication, quality management and documentation or administration systems, which are used to deal with the complexity of large projects.
  • Project network – is a graph (flow chart) depicting the sequence in which a project's terminal elements are to be completed by showing terminal elements and their dependencies.
  • Risk register – is a tool commonly used in project planning and organizational risk assessments.
  • Schedules in project management consists of a list of a project's terminal elements with intended start and finish dates.
  • Work Breakdown Structure (WBS) is a tool that defines a project and groups the project’s discrete work elements in a way that helps organize and define the total work scope of the project. A Work breakdown structure element may be a product, data, a service, or any combination. WBS also provides the necessary framework for detailed cost estimating and control along with providing guidance for schedule development and control.

Project-related problems[edit]

  • Cost overrun – is defined as excess of actual cost over budget.
  • Scope creep – refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence that is to be avoided.
The Systems Development Life Cycle.

Project management standards[edit]

  • ISO 10006 – guideline for quality management in projects, is an international standard developed by the International Organization for Standardization.
  • PMBoK; Project Management Body of Knowledge, is the international standard for project management developed by the Project Management Institute PMI.

Project participants[edit]

  • Project Management Professional – is a certificated professional in project management.
  • Certified Project Management Professional
  • Project manager – : professional in the field of project management. Project managers can have the responsibility of the planning, execution, and closing of any project, typically relating to construction industry, architecture, computer networking, telecommunications or software development.
  • Project stakeholders – are those entities within or without an organization which sponsor a project or, have an interest or a gain upon a successful completion of a project.
  • Project team – is the management team leading the project, and provide services to the project. Projects often bring together a variety number of problems. Stakeholders have important issues with others.
  • Project management office –: The Project management office in a business or professional enterprise is the department or group that defines and maintains the standards of process, generally related to project management, within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance and metrics on the practice of project management and execution.

Project management education[edit]

Degrees[edit]

Professional Certifications[edit]

Schools[edit]

Project management organizations[edit]

Project management publications[edit]

Persons influential in project management[edit]

See also[edit]

References[edit]

  1. ^ *The Definitive Guide to Project Management. Nokes, Sebastian. 2nd Ed.n. London (Financial Times / Prentice Hall): 2007. ISBN 978-0-273-71097-4
  2. ^ Paul C. Dinsmore et al (2005) The right projects done right! John Wiley and Sons, 2005. ISBN 0-7879-7113-8. p.35 and further.
  3. ^ Project Management Institute (2004). A Guide to the Project Management Body of Knowledge: PMBOK Guide. 3rd Edition. Newtown Square, Pennsylvania, Project Management Institute, p. 5.
  4. ^ “IEEE Standard Glossary of Software Engineering Terminology,” IEEE std 610.12-1990, 1990, quoted at the beginning of Chapter 1: Introduction to the guide "Guide to the Software Engineering Body of Knowledge". February 6, 2004. Archived from the original on 2008-01-18. Retrieved 2008-02-21. 
  5. ^ Peter Schuh (2005). Integrating Agile Development in the Real World. ebrary, Inc. p.2.
  6. ^ [1].
  7. ^ The PRINCE2 Guide - A to Z.
  8. ^ AACE International's Recommended Practice 11R-88, Required Skills and Knowledge of Cost Engineering, provides some answers which are excerpted here. Beyond being a guiding document for AACE International’s education and certification developments, 11R-88 is an excellent reference for industry core competency and career model development.
  9. ^ Harold Kerzner (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th Ed. ed.). Wiley. ISBN 0-471-22577-0. 
  10. ^ Project Management Body of Knowledge (PMBOK), 2000 Edition

External links[edit]