Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.
Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.
A work-breakdown structure (WBS) in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project management element that organizes the team's work into manageable sections. The Project Management Body of Knowledge defines the work-breakdown structure as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."
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. Project planning can be done manually or by the use of project management software.
A project plan, according to the Project Management Body of Knowledge (PMBOK), 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 project stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be sumarized or detailed."
A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.
Communications management is the systematic planning, implementing, monitoring, and revision of all the channels of communication within an organization and between organizations. It also includes the organization and dissemination of new communication directives connected with an organization, network, or communications technology. Aspects of communications management include developing corporate communication strategies, designing internal and external communications directives, and managing the flow of information, including online communication. It is a process that helps an organization to be systematic as one within the bounds of communication.
In project management, float or slack is the amount of time that a task in a project network can be delayed without causing a delay to:
In business and project management, a responsibility assignment matrix (RAM), also known as RACI matrix or linear responsibility chart (LRC), is a model that describes the participation by various roles in completing tasks or deliverables for a project or business process. RACI is an acronym derived from the four key responsibilities most typically used: responsible, accountable, consulted, and informed. It is used for clarifying and defining roles and responsibilities in cross-functional or departmental projects and processes. There are a number of alternatives to the RACI model.
A business analyst (BA) is a person who processes, interprets and documents business processes, products, services and software through analysis of data. The role of a business analyst is to ensure business efficiency increases through their knowledge of both IT and business function.
The precedence diagram method (PDM) is a tool for scheduling activities in a project plan. It is a method of constructing a project schedule network diagram that uses boxes, referred to as nodes, to represent activities and connects them with arrows that show the dependencies. It is also called the activity-on-node (AON) method.
Software project management is the process of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.
Project governance is the management framework within which project decisions are made. Project governance is a critical element of any project, since the accountabilities and responsibilities associated with an organization's business as usual activities are laid down in their organizational governance arrangements; seldom does an equivalent framework exist to govern the development of its capital investments (projects). For instance, the organization chart provides a good indication of who in the organization is responsible for any particular operational activity the organization conducts. But unless an organization has specifically developed a project governance policy, no such chart is likely to exist for project development activity.
A risk register (PRINCE2) is a document used as a risk management tool and to fulfill regulatory compliance acting as a repository for all risks identified and includes additional information about each risk, e.g., nature of the risk, reference and owner, mitigation measures. It can be displayed as a scatterplot or as a table.
A cost overrun, also known as a cost increase or budget overrun, involves unexpected incurred costs. When these costs are in excess of budgeted amounts due to a value engineering underestimation of the actual cost during budgeting, they are known by these terms.
A glossary of terms relating to project management and consulting.
A project management information system (PMIS) is the logical organization of the information required for an organization to execute projects successfully. A PMIS is typically one or more software applications and a methodical process for collecting and using project information. These electronic systems "help [to] plan, execute, and close project management goals." PMIS systems differ in scope, design and features depending upon an organisation's operational requirements.
In project management, scope is the defined features and functions of a product, or the scope of work needed to finish a project. Scope involves getting information required to start a project, including the features the product needs to meet its stakeholders' requirements.
The following outline is provided as an overview of and topical guide to project management:
In project management, resource smoothing is defined by A Guide to the Project Management Body of Knowledge as a "resource optimization technique in which free and total float are used without affecting the critical path" of a project. Resource smoothing as a resource optimization technique has only been introduced in the Sixth Edition of the PMBOK Guide and did not exist in its previous revisions. It is posed as an alternative and a distinct resource optimization technique beside resource leveling.
