Project Management

Published on May 2016 | Categories: Types, Presentations | Downloads: 15 | Comments: 0 | Views: 99
of 13
Download PDF   Embed   Report

Project ManagementWikipedia

Comments

Content

Project management
Project management is the discipline of initiating, plan- to systematically apply project management tools and
ning, executing, controlling, and closing the work of a techniques to complex engineering projects.* [8]
team to achieve specific goals and meet specific success
criteria. A project is a temporary endeavor designed to
produce a unique product, service or result with a defined beginning and end (usually time-constrained, and
often constrained by funding or deliverables) undertaken
to meet unique goals and objectives, typically to bring
about beneficial change or added value.* [1]* [2] The temporary nature of projects stands in contrast with business
as usual (or operations),* [3] which are repetitive, permanent, or semi-permanent functional activities to produce products or services. In practice, the management
of these two systems is often quite different, and as such
requires the development of distinct technical skills and
management strategies.* [4]
The primary challenge of project management is to
achieve all of the project goals and constraints.* [5] This
information is usually described in a user or project manual, which is created at the beginning of the development. The primary constraints are scope, time, quality
and budget.* [6] The secondary ̶and more ambitious ̶
challenge is to optimize the allocation of necessary inputs
and integrate them to meet pre-defined objectives.

1

Henry Gantt (1861–1919), the father of planning and control
techniques

History

As a discipline, project management developed from several fields of application including civil construction, engineering, and heavy defense activity.* [9] Two forefathers of project management are Henry Gantt, called the
father of planning and control techniques,* [10] who is famous for his use of the Gantt chart as a project management tool (alternatively Harmonogram first proposed by
Karol Adamiecki* [11]); and Henri Fayol for his creation
of the five management functions that form the foundation of the body of knowledge associated with project
and program management.* [12] Both Gantt and Fayol
were students of Frederick Winslow Taylor's theories of
scientific management. His work is the forerunner to
modern project management tools including work breakdown structure (WBS) and resource allocation.

Roman soldiers building a fortress, Trajan's Column 113 AD

The 1950s marked the beginning of the modern project
management era where core engineering fields come together to work as one. Project management became recognized as a distinct discipline arising from the management discipline with engineering model.* [13] In the
United States, prior to the 1950s, projects were managed
on an ad-hoc basis, using mostly Gantt charts and infor-

Until 1900, civil engineering projects were generally
managed by creative architects, engineers, and master
builders themselves, for example Vitruvius (first century
BC), Christopher Wren (1632–1723), Thomas Telford
(1757–1834) and Isambard Kingdom Brunel (1806–
1859).* [7] It was in the 1950s that organizations started
1

2
mal techniques and tools. At that time, two mathematical
project-scheduling models were developed. The "Critical
Path Method" (CPM) was developed as a joint venture between DuPont Corporation and Remington Rand
Corporation for managing plant maintenance projects.
And the "Program Evaluation and Review Technique" or
PERT, was developed by the United States Navy in conjunction with the Lockheed Corporation and Booz Allen
Hamilton as part of the Polaris missile submarine program.* [14]
PERT and CPM are very similar in their approach but still
present some differences. CPM is used for projects that
assume deterministic activity times; the times at which
each activity will be carried out are known. PERT, on
the other hand, allows for stochastic activity times; the
times at which each activity will be carried out are uncertain or varied. Because of this core difference, CPM and
PERT are used in different contexts. These mathematical
techniques quickly spread into many private enterprises.

2 APPROACHES
formed in the USA.* [17] PMI publishes A Guide to
the Project Management Body of Knowledge (PMBOK
Guide), which describes project management practices
that are common to “most projects, most of the time.”
PMI also offers multiple certifications.

2 Approaches
There are a number of approaches for managing project
activities including lean, iterative, incremental, and
phased approaches.
Regardless of the methodology employed, careful consideration must be given to the overall project objectives,
timeline, and cost, as well as the roles and responsibilities
of all participants and stakeholders.

2.1 The traditional approach
A traditional phased approach identifies a sequence of
steps to be completed. In the “traditional approach”
,* [18] five developmental components of a project can be
distinguished (four stages plus control):

PERT network chart for a seven-month project with five milestones

Typical development phases of an engineering project

At the same time, as project-scheduling models were be1. initiation
ing developed, technology for project cost estimating,
cost management, and engineering economics was evolv2. planning and design
ing, with pioneering work by Hans Lang and others. In
1956, the American Association of Cost Engineers (now
3. execution and construction
AACE International; the Association for the Advance4. monitoring and controlling systems
ment of Cost Engineering) was formed by early practitioners of project management and the associated spe5. completion and finish point
cialties of planning and scheduling, cost estimating, and
cost/schedule control (project control). AACE continued
its pioneering work and in 2006 released the first inte- Many industries use variations of these project stages.
grated process for portfolio, program and project man- For example, when working on a brick-and-mortar design
and construction, projects will typically progress through
agement (Total Cost Management Framework).
stages like pre-planning, conceptual design, schematic
The International Project Management Association design, design development, construction drawings (or
(IPMA) was founded in Europe in 1967,* [15] as a fed- contract documents), and construction administration. In
eration of several national project management associa- software development, this approach is often known as
tions. IPMA maintains its federal structure today and the waterfall model,* [19] i.e., one series of tasks after annow includes member associations on every continent ex- other in linear sequence. In software development many
cept Antarctica. IPMA offers a Four Level Certifica- organizations have adapted the Rational Unified Process
tion program based on the IPMA Competence Baseline (RUP) to fit this methodology, although RUP does not re(ICB).* [16] The ICB covers technical, contextual, and quire or explicitly recommend this practice. Waterfall debehavioral competencies.
velopment works well for small, well defined projects, but
In 1969, the Project Management Institute (PMI) was often fails in larger projects of undefined and ambiguous

2.3

Critical chain project management

nature. The Cone of Uncertainty explains some of this
as the planning made on the initial phase of the project
suffers from a high degree of uncertainty. This becomes
especially true as software development is often the realization of a new or novel product. In projects where
requirements have not been finalized and can change,
requirements management is used to develop an accurate and complete definition of the behavior of software
that can serve as the basis for software development.* [20]
While the terms may differ from industry to industry, the
actual stages typically follow common steps to problem
solving̶"defining the problem, weighing options, choosing a path, implementation and evaluation.”

2.2

PRINCE2

3
PRINCE2 provides a common language for all participants in the project. The governance framework of
PRINCE2 – its roles and responsibilities – are fully described and require tailoring to suit the complexity of the
project and skills of the organisation.* [22]

2.3 Critical chain project management
Main article: Critical chain project management
Critical chain project management (CCPM) is a method
of planning and managing project execution designed to
deal with uncertainties inherent in managing projects,
while taking into consideration limited availability of
resources (physical, human skills, as well as management
& support capacity) needed to execute projects.

Main article: PRINCE2
CCPM is an application of the theory of constraints
PRINCE2 is a structured approach to project man(TOC) to projects. The goal is to increase the flow of
projects in an organization (throughput). Applying the
first three of the five focusing steps of TOC, the system
constraint for all projects is identified as are the resources.
To exploit the constraint, tasks on the critical chain are
given priority over all other activities. Finally, projects
are planned and managed to ensure that the resources are
ready when the critical chain tasks must start, subordinating all other resources to the critical chain.

The PRINCE2 process model

agement released in 1996 as a generic project management method.* [21] It combines the original PROMPT
methodology (which evolved into the PRINCE methodology) with IBM's MITP (managing the implementation
of the total project) methodology. PRINCE2 provides
a method for managing projects within a clearly defined
framework.
PRINCE2 focuses on the definition and delivery of products, in particular their quality requirements. As such, it
defines a successful project as being output-oriented (not
activity- or task-oriented) through creating an agreed set
of products* [22] that define the scope of the project and
provides the basis for planning and control, that is, how
then to coordinate people and activities, how to design
and supervise product delivery, and what to do if products
and therefore the scope of the project has to be adjusted
if it does not develop as planned.
In the method, each process is specified with its key inputs
and outputs and with specific goals and activities to be
carried out to deliver a project's outcomes as defined by
its Business Case. This allows for continuous assessment
and adjustment when deviation from the Business Case is
required.

The project plan should typically undergo resource leveling, and the longest sequence of resource-constrained
tasks should be identified as the critical chain. In some
cases, such as managing contracted sub-projects, it is advisable to use a simplified approach without resource leveling.
In multi-project environments, resource leveling should
be performed across projects. However, it is often enough
to identify (or simply select) a single“drum”. The drum
can be a resource that acts as a constraint across projects,
which are staggered based on the availability of that single
resource.
One can also use a“virtual drum”by selecting a task or
group of tasks (typically integration points) and limiting
the number of projects in execution at that stage.

2.4 Process-based management
Main article: Process-based management
The incorporation of process-based management has
been driven by the use of Maturity models such as
the OPM3 and the CMMI (capability maturity model
integration; see this example of a predecessor) and
ISO/IEC15504 (SPICE – software process improvement
and capability estimation). Unlike SEI's CMM, the
OPM3 maturity model describes how to make project
management processes capable of performing success-

4

2 APPROACHES

fully, consistently, and predictably in order to enact the
strategies of an organization .

2.5

Agile project management

Main article: Agile Project Management
Agile project management encompasses several itera-

to develop that provides real value by implementing
tight feedback loops at all levels of the development
process and using them to steer development. XP
popularized Test Driven Development (TDD) and
Pair Programming.
• eXtreme Manufacturing (XM) - An agile methodology based on Scrum, Kanban and Kaizen that facilitates rapid engineering and prototyping.
• Crystal Clear - An agile or lightweight methodology
that focuses on colocation and osmotic communication.
• Kanban (看板) - A lean framework for process improvement that is frequently used to manage work
in progress (WIP) within agile projects. Kanban has
been specifically applied in software development.

• It is the only technique in which the client will be
actively involved in the project development.

Lean project management uses the principles from lean
manufacturing to focus on delivering value with less waste
and reduced time.

2.7 Extreme project management
Main article: Extreme project management
In critical studies of project management it has been

months
weeks

on
ati
ter

n

pla

I

days

• The only disadvantage with this technique is that it
should be used only if the client has enough time to
be actively involved in the project.

Acceptance Test

hours

St

an

minutes

d

i
Pa

up

m

ee
tin

r
N

g

n

tio
ia

ot

eg

ing

est
it T

Un

mm

ra
Prog
Pair

Code

Agile is an umbrella term for multiple project management methodologies, including:

pl
an

• It is the most consistent project management technique since it involves frequent testing of the project
under development.

Main article: Lean project management

se

Advocates of this technique claim that:

2.6 Lean project management

ea

tive approaches based on the principles of human interaction management and founded on a process view of human collaboration. Agile-based methodologies are“most
typically”employed in software development as well as
the“website, technology, creative, and marketing industries.”* [23] This sharply contrasts with traditional approaches such as the Waterfall method. In agile software
development or flexible product development, the project
is seen as a series of relatively small tasks conceived and
executed to conclusion as the situation demands in an
adaptive manner, rather than as a completely pre-planned
process.

Re
l

The iteration cycle in agile project management

• Scrum ban a mixed scrum and kanban approach to
project management. It focuses on taking the flexibility of kanban and adding the structure of scrum
to create a new way to manage projects.

• Scrum - A holistic approach to development that focuses on iterative goals set by the Product Owner
through a backlog, which is developed by the De- Planning and feedback loops in Extreme programming (XP) with
livery Team through the facilitation of the Scrum the time frames of the multiple loops.
Master.
noted that several PERT based models are not well suited
• Extreme Programming (XP) - A set of practices for the multi-project company environment of today.
based on a set of principles and values, with a goal Most of them are aimed at very large-scale, one-time,

3.1

Initiating

5

non-routine projects, and currently all kinds of management are expressed in terms of projects.
Using complex models for“projects”(or rather“tasks”)
spanning a few weeks has been proven to cause unnecessary costs and low maneuverability in several cases. The
generalization of Extreme Programming to other kinds
of projects is extreme project management, which may be
used in combination with the process modeling and management principles of human interaction management.

2.8

Benefits realization management

Main article: Benefits realisation management
Benefits realization management (BRM) enhances normal project management techniques through a focus on
outcomes (the benefits) of a project rather than products
or outputs, and then measuring the degree to which that
is happening to keep a project on track. This can help to
reduce the risk of a completed project being a failure by
delivering agreed upon requirements/outputs but failing
to deliver the benefits of those requirements.

The project development stages* [25]

be supplemented with decision points (go/no go decisions) at which the project's continuation is debated and
decided. An example is the Phase–gate model.

In addition, BRM practices aim to ensure the alignment
between project outcomes and business strategies. The
3.1
effectiveness of these practices is supported by recent research evidencing BRM practices influencing project success from a strategic perspective across different countries and industries.* [24]

Initiating

An example of delivering a project to requirements might
be agreeing to deliver a computer system that will process
staff data and manage payroll, holiday and staff personnel
records. Under BRM the agreement might be to achieve a
Initiating process group processes* [25]
specified reduction in staff hours required to process and
maintain staff data.
The initiating processes determine the nature and scope
of the project.* [26] If this stage is not performed well, it is
unlikely that the project will be successful in meeting the
3 Processes
businessʼneeds. The key project controls needed here are
an understanding of the business environment and makTraditionally, project management includes a number ing sure that all necessary controls are incorporated into
of elements: four to five project management process the project. Any deficiencies should be reported and a
groups, and a control system. Regardless of the method- recommendation should be made to fix them.
ology or terminology used, the same basic project man- The initiating stage should include a plan that encomagement processes will be used. Major process groups passes the following areas:
generally include:* [6]
• Initiation

• analyzing the business needs/requirements in measurable goals

• Planning

• reviewing of the current operations

• Production or execution

• financial analysis of the costs and benefits including
a budget

• Monitoring and controlling
• Closing
In project environments with a significant exploratory element (e.g., research and development), these stages may

• stakeholder analysis, including users, and support
personnel for the project
• project charter including costs, tasks, deliverables,
and schedules

6

3

3.2

PROCESSES

Planning

After the initiation stage, the project is planned to
an appropriate level of detail (see example of a flowchart).* [25] The main purpose is to plan time, cost and
resources adequately to estimate the work needed and to
effectively manage risk during project execution. As with
the Initiation process group, a failure to adequately plan
greatly reduces the project's chances of successfully accomplishing its goals.
Project planning generally consists of* [27]
Executing process group processes* [25]

• determining how to plan (e.g. by level of detail or
Rolling Wave planning);
• developing the scope statement;
• selecting the planning team;
• identifying deliverables and creating the work
breakdown structure;
• identifying the activities needed to complete those
deliverables and networking the activities in their Monitoring and controlling process group processes* [25]
logical sequence;
• estimating the resource requirements for the activi- 3.4 Monitoring and controlling
ties;
Monitoring and controlling consists of those processes
• estimating time and cost for activities;
performed to observe project execution so that potential
problems can be identified in a timely manner and correc• developing the schedule;
tive action can be taken, when necessary, to control the
execution of the project. The key benefit is that project
• developing the budget;
performance is observed and measured regularly to identify variances from the project management plan.
• risk planning;
• gaining formal approval to begin work.
Additional processes, such as planning for communications and for scope management, identifying roles and
responsibilities, determining what to purchase for the
project and holding a kick-off meeting are also generally
advisable.
For new product development projects, conceptual design
of the operation of the final product may be performed
concurrent with the project planning activities, and may
help to inform the planning team when identifying deliverables and planning activities.

3.3

Executing

Monitoring and controlling includes:* [28]
• Measuring the ongoing project activities ('where we
are');
• Monitoring the project variables (cost, effort, scope,
etc.) against the project management plan and the
project performance baseline (where we should be);
• Identify corrective actions to address issues and risks
properly (How can we get on track again);
• Influencing the factors that could circumvent integrated change control so only approved changes are
implemented.
In multi-phase projects, the monitoring and control process also provides feedback between project phases, in order to implement corrective or preventive actions to bring
the project into compliance with the project management
plan.

The execution/implementation phase ensures that the
project management planʼs deliverables are executed
accordingly. This phase involves proper allocation, coordination and management of human resources and any
other resources such as material and budgets. The output Project maintenance is an ongoing process, and it inof this phase is the project deliverables.
cludes:* [6]

3.5

Closing

• Continuing support of end-users

7

3.5 Closing

• Correction of errors
• Updates to the product over time

Closing process group processes.* [25]

Closing includes the formal acceptance of the project and
the ending thereof. Administrative activities include the
archiving of the files and documenting lessons learned.
This phase consists of:* [6]
• Contract closure: Complete and settle each contract (including the resolution of any open items)
and close each contract applicable to the project or
project phase.
Monitoring and controlling cycle

In this stage, auditors should pay attention to how effectively and quickly user problems are resolved.
Over the course of any construction project, the work
scope may change. Change is a normal and expected part
of the construction process. Changes can be the result of
necessary design modifications, differing site conditions,
material availability, contractor-requested changes, value
engineering and impacts from third parties, to name a
few. Beyond executing the change in the field, the change
normally needs to be documented to show what was actually constructed. This is referred to as change management. Hence, the owner usually requires a final record to
show all changes or, more specifically, any change that
modifies the tangible portions of the finished work. The
record is made on the contract documents – usually, but
not necessarily limited to, the design drawings. The end
product of this effort is what the industry terms as-built
drawings, or more simply, “as built.”The requirement
for providing them is a norm in construction contracts.
Construction document management is a highly important task undertaken with the aid an online or desktop
software system, or maintained through physical documentation. The increasing legality pertaining to the construction industries maintenance of correct documentation has caused the increase in the need for document
management systems.
When changes are introduced to the project, the viability of the project has to be re-assessed. It is important
not to lose sight of the initial goals and targets of the
projects. When the changes accumulate, the forecasted
result may not justify the original proposed investment
in the project. Successful project management identifies
these components, and tracks and monitors progress so
as to stay within time and budget frames already outlined
at the commencement of the project.

• Project close: Finalize all activities across all of
the process groups to formally close the project or
a project phase
Also included in this phase is the Post Implementation
Review. This is a vital phase of the project for the
project team to learn from experiences and apply to future projects. Normally a Post Implementation Review
consists of looking at things that went well and analysing
things that went badly on the project to come up with
lessons learned.

3.6 Project controlling and project control
systems
Project controlling should be established as an independent function in project management. It implements verification and controlling function during the processing of
a project in order to reinforce the defined performance
and formal goals.* [29] The tasks of project controlling
are also:
• the creation of infrastructure for the supply of the
right information and its update
• the establishment of a way to communicate disparities of project parameters
• the development of project information technology
based on an intranet or the determination of a project
key performance indicator system (KPI)
• divergence analyses and generation of proposals for
potential project regulations* [30]
• the establishment of methods to accomplish an appropriate project structure, project workflow organization, project control and governance

8

4 TOPICS

• creation of transparency among the project parame- successfully. A formal process is more effective in creatters* [31]
ing strong controls, and auditors should review this process to confirm that it is well designed and is followed in
Fulfillment and implementation of these tasks can be practice. A good formal systems development plan outachieved by applying specific methods and instruments lines:
of project controlling. The following methods of project
• A strategy to align development with the organizacontrolling can be applied:
tionʼs broader objectives
• investment analysis

• Standards for new systems

• cost–benefit analysis

• Project management policies for timing and
budgeting

• value benefit analysis

• Procedures describing the process

• expert surveys

• Evaluation of quality of change

• simulation calculations
• risk-profile analysis

4 Topics

• surcharge calculations

4.1 Project managers

• milestone trend analysis
• cost trend analysis

A project manager is a professional in the field of project
management. Project managers can have the responsibil• target/actual-comparison [32]
ity of the planning, execution, and closing of any project,
typically relating to construction industry, engineering,
Project control is that element of a project that keeps it architecture, computing, and telecommunications. Many
on-track, on-time and within budget.* [28] Project con- other fields in production engineering, design engineertrol begins early in the project with planning and ends ing, and heavy industrial have project managers.
late in the project with post-implementation review, having a thorough involvement of each step in the pro- A project manager is the person accountable for accomcess. Projects may be audited or reviewed while the plishing the stated project objectives. Key project manproject is in progress. Formal audits are generally risk or agement responsibilities include creating clear and attaincompliance-based and management will direct the objec- able project objectives, building the project requirements,
tives of the audit. An examination may include a compar- and managing the triple constraint for projects, which is
ison of approved project management processes with how cost, time, and scope.
the project is actually being managed.* [33] Each project A project manager is often a client representative and
should be assessed for the appropriate level of control has to determine and implement the exact needs of the
needed: too much control is too time consuming, too little client, based on knowledge of the firm they are reprecontrol is very risky. If project control is not implemented senting. The ability to adapt to the various internal procorrectly, the cost to the business should be clarified in cedures of the contracting party, and to form close links
terms of errors and fixes.
with the nominated representatives, is essential in ensurControl systems are needed for cost, risk, quality, com- ing that the key issues of cost, time, quality and above all,
munication, time, change, procurement, and human re- client satisfaction, can be realized.
*

sources. In addition, auditors should consider how important the projects are to the financial statements, how reliant the stakeholders are on controls, and how many controls exist. Auditors should review the development process and procedures for how they are implemented. The
process of development and the quality of the final product may also be assessed if needed or requested. A business may want the auditing firm to be involved throughout
the process to catch problems earlier on so that they can
be fixed more easily. An auditor can serve as a controls
consultant as part of the development team or as an independent auditor as part of an audit.

4.2 Project management types

Project management can apply to any project, but it is
often tailored to accommodate the specific needs of different and highly specialized industries. For example,
the construction industry, which focuses on the delivery of things like buildings, roads, and bridges, has developed its own specialized form of project management
that it refers to as Construction project management and
for which project managers can become trained and certified in.* [34] The Information technology industry has
Businesses sometimes use formal systems development also evolved to develop its own form of Project manageprocesses. These help assure that systems are developed ment that is referred to as IT Project management and

4.5

Project portfolio management

which specializes in the delivery of technical assets and
services that are required to pass through various lifecycle phases such as planning, design, development, testing, and deployment. Biotechnology project management
focuses on the intricacies of biotechnology research and
development.* [35]
For each type of project management, project managers
develop and utilize repeatable templates that are specific
to the industry they're dealing with. This allows project
plans to become very thorough and highly repeatable,
with the specific intent to increase quality, lower delivery costs, and lower time to deliver project results.

4.3

Work breakdown structure

Main article: Work breakdown structure
The work breakdown structure (WBS) is a tree structure that shows a subdivision of effort required to achieve
an objective̶for example a program, project, and contract. The WBS may be hardware-, product-, service-, or
process-oriented (see an example in a NASA reporting
structure (2001)).* [36]
A WBS can be developed by starting with the end objective and successively subdividing it into manageable
components in terms of size, duration, and responsibility
(e.g., systems, subsystems, components, tasks, sub-tasks,
and work packages), which include all steps necessary to
achieve the objective.* [20]
The work breakdown structure provides a common
framework for the natural development of the overall planning and control of a contract and is the basis
for dividing work into definable increments from which
the statement of work can be developed and technical,
schedule, cost, and labor hour reporting can be established.* [36] The work breakdown structure can be displayed in two forms one in form of a table with subdivision of tasks two in form of an organisational chart.

9
• Capability Maturity Model from the Software Engineering Institute.
• GAPPS, Global Alliance for Project Performance
Standards – an open source standard describing
COMPETENCIES for project and program managers.
• A Guide to the Project Management Body of
Knowledge from the Project Management Institute
(PMI)
• HERMES method, Swiss general project management method, selected for use in Luxembourg and
international organizations.
• The ISO standards ISO 9000, a family of standards for quality management systems, and the ISO
10006:2003, for Quality management systems and
guidelines for quality management in projects.
• PRINCE2, Projects IN Controlled Environments.
• Association for Project Management Body of
Knowledge* [38]
• Team Software Process (TSP) from the Software
Engineering Institute.
• Total Cost Management Framework, AACE International's Methodology for Integrated Portfolio,
Program and Project Management.
• V-Model, an original systems development method.
• The Logical framework approach, which is popular
in international development organizations.
• [Australian Institute of Project Management] AIPM
has 4 levels of certification; CPPP, CPPM, CPPD
& CPPE for Certified Practicing Project ... Partner,
Manager, Director and Executive.

4.5 Project portfolio management
4.4

International standards

Main article: Project portfolio management

There have been several attempts to develop project management standards, such as:
An increasing number of organizations are using, what
is referred to as, project portfolio management (PPM)
projects and then using
• ISO 21500: 2012 - Guidance on project manage- as a means of selecting the right
*
[39]
as the means for deproject
management
techniques
ment. This is the first project management ISO.
livering the outcomes in the form of benefits to the per• ISO 31000: 2009 - Risk management. Risk man- forming private or not-for-profit organization.
agement is 1 of the 10 knowledge areas of either
ISO 21500 or PMBoK5 concept of project manage4.6 Project management software
ment.
• ISO/IEC/IEEE 16326-2009 - Systems and Software Main articles: Project management software and Project
Engineering̶Life Cycle Processes̶Project Man- management information system
agement * [37]

10

6

REFERENCES

Project management software is software used to help [10] Martin Stevens (2002). Project Management Pathways.
Association for Project Management. APM Publishing
plan, organize, and manage resource pools, develop reLimited, 2002 ISBN 1-903494-01-X p.xxii
source estimates and implement plans. Depending on the
sophistication of the software, functionality may include [11] Edward R. Marsh (1975). “The Harmonogram of Karol
estimation and planning, scheduling, cost control and
Adamiecki”. In: The Academy of Management Journal.
budget management, resource allocation, collaboration
Vol. 18, No. 2 (Jun., 1975), p. 358. (online)
software, communication, decision-making, workflow,
quality management, documentation and/or administra- [12] Morgen Witzel (2003). Fifty key figures in management.
Routledge, 2003. ISBN 0-415-36977-0. p. 96-101.
tion systems.* [40]* [41]

4.7

Virtual project management

Main article: Virtual team

[13] David I. Cleland, Roland Gareis (2006). Global Project
Management Handbook.
McGraw-Hill Professional,
2006. ISBN 0-07-146045-4. p.1-4 states: "It was in the
1950s when project management was formally recognized
as a distinct contribution arising from the management discipline."

Virtual program management (VPM) is management of a [14] B. Ralph Stauber, H. M. Douty, Willard Fazar, Richard H.
project done by a virtual team, though it rarely may refer
Jordan, William Weinfeld and Allen D. Manvel. Federal
to a project implementing a virtual environment* [42] It
Statistical Activities. The American Statistician 13(2): 912 (Apr., 1959) , pp. 9-12
is noted that managing a virtual project is fundamentally
different from managing traditional projects,* [43] com[15] Bjarne Kousholt (2007). Project Management –. Theory
bining concerns of telecommuting and global collaboraand practice.. Nyt Teknisk Forlag. ISBN 87-571-2603-8.
*
tion (culture, timezones, language). [44]
p.59.
[16] ipma.ch

5

See also

6

References

[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] “What is Project Management? | Project Management
Institute”. Pmi.org. Retrieved 2014-06-04.
[3] 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.
[4] Cattani, G., Ferriani, S., Frederiksen, L. and Florian, T.
(2011) Project-Based Organizing and Strategic Management, Advances in Strategic Management, Vol 28, Emerald, ISBN 1780521936.
[5] Joseph Phillips (2003). PMP Project Management Professional Study Guide. McGraw-Hill Professional, 2003.
ISBN 0-07-223062-2 p.354.
[6] PMI (2010). A Guide to the Project Management Body of
Knowledge p.27-35
[7] Dennis Lock (2007) Project Management (9th ed.) Gower
Publishing, Ltd., 2007. ISBN 0-566-08772-3
[8] Young-Hoon Kwak (2005). “A brief History of Project
Management”. In: The story of managing projects. Elias
G. Carayannis et al. (9 eds), Greenwood Publishing
Group, 2005. ISBN 1-56720-506-2
[9] David I. Cleland, Roland Gareis (2006). Global Project
Management Handbook. “Chapter 1: “The evolution of
project management”. McGraw-Hill Professional, 2006.
ISBN 0-07-146045-4

[17] F. L. Harrison, Dennis Lock (2004). Advanced project
management: a structured approach. Gower Publishing,
Ltd., 2004. ISBN 0-566-07822-8. p.34.
[18] Wysocki, Robert K (2013). Effective Project Management: Traditional, Adaptive, Extreme (Seventh Edition).
John Wiley & Sons. ISBN 978-1118729168.
[19] Winston W. Royce (1970). “Managing the Development of Large Software Systems”in: Technical Papers of
Western Electronic Show and Convention (WesCon) August 25–28, 1970, Los Angeles, USA.
[20] Stellman, Andrew; Greene, Jennifer (2005). Applied Software Project Management. O'Reilly Media. ISBN 978-0596-00948-9.
[21] OGC – PRINCE2 – Background
[22] [Office for Government Commerce (1996) Managing Successful Projects with PRINCE2, p14]
[23] “What is Agile Project Management?". Planbox.
[24] Serra, C. E. M. & Kunc, M., 2014. Benefits Realisation Management and its influence on project success and
on the execution of business strategies. Also, no. International Journal of Project Management, Issue http:
//dx.doi.org/10.1016/j.ijproman.2014.03.011.
[25] “Project Management Guide”(PDF). VA Office of Information and Technology. 2003. Archived from the original
on January 14, 2009.
[26] Peter Nathan, Gerald Everett Jones (2003). PMP certification for dummies. p.63.
[27] Harold Kerzner (2003). Project Management: A Systems
Approach to Planning, Scheduling, and Controlling (8th
ed.). Wiley. ISBN 0-471-22577-0.

11

[28] James P. Lewis (2000). The project manager's desk reference: : a comprehensive guide to project planning, scheduling, evaluation, and systems. p.185
[29] Jörg Becker, Martin Kugeler, Michael Rosemann (2003).
Process management: a guide for the design of business
processes. ISBN 978-3-540-43499-3. p.27.
[30] Bernhard Schlagheck (2000).
Objektorientierte
Referenzmodelle für das Prozess- und Projektcontrolling.
Grundlagen – Konstruktionen – Anwendungsmöglichkeiten. ISBN 978-3-8244-7162-1. p.131.
[31] Josef E. Riedl (1990). Projekt – Controlling in Forschung
und Entwicklung. ISBN 978-3-540-51963-8. p.99.
[32] Steinle, Bruch, Lawa (1995). Projektmanagement. FAZ
Verlagsbereich Wirtschaftsbücher. p.136–143
[33] Cynthia Snyder, Frank Parth (2006). Introduction to IT
Project Management. p.393-397
[34] “Certified Construction Manager”. CMAA. Retrieved
23 November 2013.
[35] “Certificate in Biotechnology Project Management”.
University of Washington. Retrieved 23 November 2013.
[36] NASA NPR 9501.2D. May 23, 2001.
[37] ISO/IEC/IEEE
16326-2009
Systems
and
Software
Engineering--Life
Cycle
Processes-Project Management.
December 2009.
DOI:
10.1109/IEEESTD.2009.5372630.
ISBN 978-07381-6116-7
[38] Body of Knowledge 5th edition, Association for Project
Management, 2006, ISBN 1-903494-13-3
[39] Albert Hamilton (2004). Handbook of Project Management Procedures. TTL Publishing, Ltd. ISBN 0-72773258-7
[40] PMBOK 4h Ed. p. 443. ISBN 978-1933890517.
[41] Tom Kendrick. The Project Management Tool Kit:
100 Tips and Techniques for Getting the Job Done
Right, Third Edition. AMACOM Books, 2013 ISBN
9780814433454
[42] Curlee, Wanda (2011). The Virtual Project Management
Office: Best Practices, Proven Methods.
[43] Khazanchi, Deepak (2005). Patterns of Effective Project
Management in Virtual Projects: An Exploratory Study.
Project Management Institute. ISBN 9781930699830.
[44] Velagapudi, Mridula (April 13, 2012).“Why You Cannot
Avoid Virtual Project Management 2012 Onwards”.

7

External links
• Guidelines for Managing Projects from the UK Department for Business, Enterprise and Regulatory
Reform (BERR)

12

8 TEXT AND IMAGE SOURCES, CONTRIBUTORS, AND LICENSES

8

Text and image sources, contributors, and licenses

8.1

Text

• Project management Source: https://en.wikipedia.org/wiki/Project_management?oldid=713279743 Contributors: AxelBoldt, Derek
Ross, Mav, Tarquin, Ap, Hirzel, Tzartzam, Chuq, Edward, Michael Hardy, Kwertii, Norm, Nixdorf, Ixfd64, Delirium, Chadloder,
Minesweeper, Ronz, Julesd, Marco Krohn, Mkoval, Nikai, Jiang, Media lib, Mydogategodshat, Nickg, Colin Marquardt, Wik, Traroth,
Vaceituno, Lumos3, Paul W, Pigsonthewing, ChrisG, Donreed, Goethean, Hubertus~enwiki, Securiger, Chris Roy, Merovingian, Ojigiri~enwiki, Rrjanbiah, Hadal, Rubysixty6, Tobias Bergemann, Ancheta Wis, Giftlite, Graeme Bartlett, Oberiko, Zigger, Mark.murphy,
Jgritz, Niteowlneils, Craigwb, DominikusH, Redux, Solipsist, Khalid hassani, Christopherlin, ALargeElk, Wgoetsch, Utcursch, Toytoy,
Quadell, Kevin B12, Karl-Henner, Pgreenfinch, Howardjp, Mark Millard, Imroy, CALR, Discospinster, Rich Farmbrough, Phreed, Pavel
Vozenilek, ESkog, Khalid, Jaberwocky6669, Kbh3rd, S.K., Aranel, Zscout370, Mwanner, PhilHibbs, Shanes, Aaronbrick, Bobo192, Spalding, Janna Isabot, Smalljim, John Vandenberg, RAM, Maurreen, Richi, AndyBrandt, Mdd, Rernst, Alansohn, Liao, Richard Harvey,
Jeltz, Jdtoellner, Spangineer, OSUKid7, Projectmagic, Freeskies, Krappie, Twestgard, RainbowOfLight, LFaraone, Versageek, TVBZ28,
Asannuti, Eric Pement, Geoffsauer, Zntrip, Weyes, Woohookitty, Mindmatrix, Camw, Scjessey, Ruud Koot, Jeff3000, Firien, Turnstep,
RuM, Tslocum, TetsuoTheRob, Graham87, BD2412, Search4Lancer, Ketiltrout, Kinu, Trial~enwiki, Smiker, HappyCamper, Graibeard,
Sleepyhead81, Jeffmcneill, Matt Deres, Fred Bradstadt, Yamamoto Ichiro, Ian Pitchford, Paradoxic, Gurch, Tijuana Brass, EronMain,
Bmicomp, Sharkface217, DVdm, Bgwhite, Gwernol, Richman9, RussBot, Fabricationary, Van der Hoorn, Manop, Rsrikanth05, NawlinWiki, Richard Allen, Exir Kamalabadi, Gruffi~enwiki, Moe Epsilon, Stevenwmccrary58, Neurotoxic, Bob Bolin, Tony1, Dbfirs, Falcon9x5, DeadEyeArrow, Bota47, ThreePD, Mugunth Kumar, Deville, Zzuuzz, Freeformer, Closedmouth, Fang Aili, Lynbarn, GraemeL,
Aeon1006, BSJWright, Bernd in Japan, BiH, DVD R W, That Guy, From That Show!, Leonardo Aloi, Luk, ChemGardener, Sarah,
SmackBot, Mneser, Hux, Reedy, Shoy, Vald, Weatherman90, Renesis, Saros136, AstareGod, WKirschling, Jlao04, MalafayaBot, Deli
nk, Renebach, Octahedron80, FalconZero, Hongooi, Scaevus, GerK, Zsinj, Oblomoff, RandyKaelber, KaiserbBot, Rrburke, Parent5446,
RedHillian, Mr.Z-man, Thrane, Jmlk17, Radagast83, Cybercobra, Fullstop, AndrewStellman, Weregerbil, DMacks, Just plain Bill, Rspanton, RJBurkhart, Reliablesources, Gunnala, Thopper, Kuru, MagnaMopus, Scientizzle, Wissons, Tosblt, Beetstra, Ehheh, InedibleHulk,
TastyPoutine, Mgillett, RichardF, Jp361, Rcannon100, Clf99, David.alex.lamb, Hu12, Meitar, Levineps, Alessandro57, Akbradford, Shoeofdeath, Mudgen, Yendor1958, AGK, Linkspamremover, Markbassett, Tawkerbot2, The Letter J, AbsolutDan, CmdrObot, ITServiceGuy,
Garrybooker, Ale jrb, Dycedarg, Pmyteh, Kcone, Dgw, DanielRigal, Nighthawkx15, Kenstandfield, Drshields, Kanags, Pukivruki, Frankfshsu, Hudec, CFMWiki1, Xlynx, Doug Weller, Funatic~enwiki, Brion.finlay, Epbr123, Sisalto, Wikid77, Hazmat2, Teammetz, Mmpubs,
BartaS, Mojo Hand, Clad2020, Vineetgandhi, Richardgush, X201, Blathnaid, Dawnseeker2000, Pgauld, AntiVandalBot, Ron Richard,
Luna Santin, Uqjwhitt, Widefox, Seaphoto, JimGleaves, Tmopkisn, Smartse, [email protected], Deadbeef, Arsenikk, JAnDbot, Achalmeena, Barek, MrKris, Vincehk, Lundholm, Altrock78, PhilKnight, Creacon, Hroðulf, Gsaup, VoABot II, Cmaley, Dansedmonson, Englishman in Provence, Mwfnwa, Rami R, Hubbardaie, Rich257, Theroadislong, Steevm, Readysetpass, Globalprofessor, Allstarecho, Brentwills, ArmadilloFromHell, Lmarinho, DenzilS, Oicumayberight, Rwil02, Jmciver, MartinBot, Judy Payne, Davidjcmorris,
Munazanjum, Khusroks, CommonsDelinker, Earthandfire, Ocrakate, PrestonH, DBlomgren, EdBever, Mpleahy, Erkan Yilmaz, J.delanoy,
Pilgaard, Benfellows, GeoffWilson, Eshirazi, Herbythyme, Kanojia, Jonpro, Pstansbu, FactsAndFigures, Ian.thomson, Mbrylant, Shawn in
Montreal, Salliesatt, LordAnubisBOT, Xholyrelicx, Peter Reusch, Belovedfreak, SJP, RSedor, Shoessss, Jackaranga, Cometstyles, WJBscribe, DeltaOperator, Vanished user 39948282, Bonadea, Pdcook, Inwind, Pstout, Fpolack, Austinm, RJASE1, VolkovBot, DoorsAjar, TXiKiBoT, Oshwah, Ninadelis, Alex rosenberg35, Technopat, GDonato, SueHay, Peterbud, Monkey Bounce, Owain.wilson, Pixievamps, Nishalegend, Seraphim, Rwgreen1173, Claidheamohmor, Dgmoran, LeaveSleaves, The Led, PDFbot, Vgranucci, Pcremerfluno,
Kilmer-san, Jcardinal, Ykimva, Forestsmith, Haikon, Guy Van Hooveld, Falcon8765, Macoykolokoy, Project mosaic, Antillarum, Research2007, Chiefwhite, Ktlonergan, Kenmckinley, Dtarver, Gerritklaschke, Butrain, Paltpappa, The manekin, Dan Polansky, Wikke41,
SieBot, Gfani, Vigo10, Moonriddengirl, Malcolmxl5, Ghaag, RJaguar3, Pmtoolbox, Whiteghost.ink, JohnManuel, GAPPS, Mimihitam,
Deimos814, Pm master, AngelOfSadness, Aboluay, Anakin101, Protr, Dodger67, Bananaman68, Anchor Link Bot, Vcmohanonline,
FMMonty, Pinkadelica, Escape Orbit, Granite07, Faithlessthewonderboy, Mishath5, Billaronson, Loren.wilton, ClueBot, Sutanumartand,
Rlolsen, Gop 62, Cerrol, The Thing That Should Not Be, Kelemendani, Vanderzyden, Bdouthwaite, NOKESS, DanielDeibler, Xavexgoem,
Blanchardb, LizardJr8, Fxsunny, Sebasanjuan, Atif673, Auntof6, PatrickWeaver, Jetojedno, Wrduncan3, M4gnum0n, Margeru, Qatestdev, Erebus Morgaine, Eeekster, Chrispreece2007, MorrisRob, Lartoven, Acheah, VARies, Alphamu57, Wacko39, Calvadosser, CPMTutor, Jkhcanoe, IngaRea, BOTarate, Janbenes, Thingg, 9Nak, Aitias, Porchcorpter, Burner0718, Apparition11, DumZiBoT, MY2sense,
LightAnkh, XLinkBot, Lecard, Jytdog, Poli08, BodhisattvaBot, SE SME, Rror, Bmartel, ProfDEH, Trewinpa, WikHead, Overviewer,
Addbot, Pythia90, Jojhutton, Mapador, Rmp80ind, Raywil, DougsTech, Jmi41, Ronhjones, Bnorrie, Leszek Jańczuk, OliverTwisted, Itgov, Cst17, Royallarry, MrOllie, Download, Pcremer2270, Favonian, Urbanette, SpBot, Truthbro, ICSGlobal, Josemoromelon, Tephlon,
Elvismcgrady, Trout001, Wireless friend, Jarble, Radavi, Mlavannis, Waltloc, Legobot, Luckas-bot, Yobot, Tohd8BohaithuGh1, Fraggle81, Muminshawaf, ConstructionSoftwareExperts, Melashri, Pm by day, AnomieBOT, Sbugs, Bendoly, Rubinbot, Nankivel, Jburks97,
Jim1138, JackieBot, L3aa-cademy, Jnankivel, Kingpin13, Tobryant, Jmecholsky, Mann jess, Christiebiehl, Materialscientist, Dendlai, Citation bot, Alisha0512, Alsuara, Smpickens, Ngoult, Raymundsy, LilHelpa, Xqbot, Psaico, Jordiferrer, Transity, The Banner,
Seanieboy1974, Dr PDG, Kokcharov, Triz231, Crzer07, Mywikiid99, GrouchoBot, Nirjal stha, RibotBOT, Anitanandi, Anodynomine,
CarlGuass, Oldschoolosama, Skumar.rakesh, 4RugbyRd, Ylebihan, Shadowjams, Longdongniner, Sandymok, GESICC, Asoucek, Levana77, Mummy34, FrescoBot, Pepper, Padraig1888, Mark Renier, Ccorpusa, Nazmanager, Tetraedycal, Mini.here, Frontelo, HamburgerRadio, Dghutchinson, Boxplot, Pinethicket, Spartikus411, Viokiori, Guy.other, Jonesey95, RedBot, Elena1234, Serols, SpaceFlight89,
Maokart444, Doroli, Kim Kris, Reconsider the static, Plakhi24, Chris Caven, John Richard Parker, Lotje, Vrenator, Thebluemanager,
DARTH SIDIOUS 2, Mean as custard, SorenAndersen, Bento00, Kltownsend, Bertha32, Djjr, Cloud10pm, EmausBot, Orphan Wiki,
WikitanvirBot, T3dkjn89q00vl02Cxp1kqs3x7, Super48paul, Primefac, Ebe123, RenamedUser01302013, Peaceray, Dennis.wittekind,
Tswelch, KimBecker, Tommy2010, Wikipelli, Dcirovic, K6ka, Yongliang08, Danielhegglin, Fæ, Kaisersoze1, QEDK, 1959frenchy, Gbsrd, Sara050805, Sean Whitaker, Qaiassist, Donner60, Thebrownell, Orange Suede Sofa, Rangoon11, Colabtech31, Nicos interests, Ct31,
Himdey njitwill, UserHuge, Loflabr, MichaelDawin, Dennal68, Christyoc, Vans0100, Petrb, DisneyG, David VS West, ClueBot NG, Rich
Smith, Dickietr, DrDooBig, Gareth Griffith-Jones, Zugerbueb, MelbourneStar, Qarakesek, Frostbitcanadian, RoyHanney, Artemis Fowl
Rules, Theboymusic, උපුල්, Wwmarket, Widr, Helpful Pixie Bot, Jeraphine Gryphon, BG19bot, Jbcarboni, Jamezbailey, Markkh, Jurajv, Scyllagist, Binafhmz, Spyr234, AvocatoBot, Compfreak7, Scmbwis, Altaïr, Atena.kouchaki, Jn.arch, DPL bot, Buissy, Sonialoud,
Wannabemodel, A.harris0708, KGun10, BattyBot, Shokolada, Mrt3366, 05proedl, Nandak89, Cyberbot II, John.j.smitherson, Faberglas, Freepmstudy, Pjganon, Gshills, IjonTichyIjonTichy, George Huhn, Rumblesnuf, Milkau111, Fongamanda, Aidanmharrington, Hech
xwijnerj, ProgrammeUK, SFK2, Cadillac000, Phamnhatkhanh, Epicgenius, Ralfjnr, Eyesnore, Geza.molnar, Tentinator, Silverbaton,
Ashoka111, Mschmidt224, Andyrscott, Ginsuloft, Hisashiyarouin, UY Scuti, Projectlad, Aberniz, Lakun.patra, Aceofphrase, Csusarah,

8.2

Images

13

Wiki3457, John Gaziano, Editor0071, Gertdude, Red-Lips-Beauty, Pmifi, U2fanboi, YLoginov, Carlos.serra, CPPD.Projects, Amortias,
Pankajkkumar, Missross, Umesh.barclays, Shrankhla, Bagmic, Nhadji, MitchLee101, Ansonrs, Garbanea, Generalcontributor, Ajpreston,
Edwardchungweb, Khurram1190, Dbayom, Dannypm, Tess2015, KasparBot, Dlwaltz, Lilianobat, Marek Prasoł, Uzairfata, Silviu Claudiu
Ciuta, Wiki5012, Olga Tamodlina and Anonymous: 1218

8.2

Images

• File:Agile_Project_Management_by_Planbox.png Source: https://upload.wikimedia.org/wikipedia/commons/5/50/Agile_Project_
Management_by_Planbox.png License: CC BY-SA 3.0 Contributors: Own work Original artist: Planbox
• File:Closing_Process_Group_Processes.jpg Source:
https://upload.wikimedia.org/wikipedia/commons/8/8b/Closing_Process_
Group_Processes.jpg License: Public domain Contributors: Project Management Guide Original artist: DEPARTMENT OF VETERANS
AFFAIRS Office of Information and Technology
• File:Commons-logo.svg Source: https://upload.wikimedia.org/wikipedia/en/4/4a/Commons-logo.svg License: CC-BY-SA-3.0 Contributors: ? Original artist: ?
• File:Executing_Process_Group_Processes.jpg Source: https://upload.wikimedia.org/wikipedia/commons/1/1c/Executing_Process_
Group_Processes.jpg License: Public domain Contributors: Project Management Guide Original artist: DEPARTMENT OF VETERANS
AFFAIRS Office of Information and Technology
• File:Folder_Hexagonal_Icon.svg Source: https://upload.wikimedia.org/wikipedia/en/4/48/Folder_Hexagonal_Icon.svg License: Cc-bysa-3.0 Contributors: ? Original artist: ?
• File:Henri_Gannt.jpg Source: https://upload.wikimedia.org/wikipedia/commons/8/89/Henri_Gannt.jpg License: Public domain Contributors: http://www.gannt-chart.com/gnImages/H_L_Gannt.jpg Original artist: Unknown<a href='//www.wikidata.org/wiki/Q4233718'
title='wikidata:Q4233718'><img
alt='wikidata:Q4233718'
src='https://upload.wikimedia.org/wikipedia/commons/thumb/f/ff/
Wikidata-logo.svg/20px-Wikidata-logo.svg.png' width='20' height='11' srcset='https://upload.wikimedia.org/wikipedia/commons/
thumb/f/ff/Wikidata-logo.svg/30px-Wikidata-logo.svg.png
1.5x,
https://upload.wikimedia.org/wikipedia/commons/thumb/f/ff/
Wikidata-logo.svg/40px-Wikidata-logo.svg.png 2x' data-file-width='1050' data-file-height='590' /></a>
• File:Initiating_Process_Group_Processes.jpg Source: https://upload.wikimedia.org/wikipedia/commons/c/c4/Initiating_Process_
Group_Processes.jpg License: Public domain Contributors: Project Management Guide Original artist: DEPARTMENT OF VETERANS
AFFAIRS Office of Information and Technology
• File:Monitoring_and_Controlling_Process_Group_Processes.jpg Source: https://upload.wikimedia.org/wikipedia/commons/d/d0/
Monitoring_and_Controlling_Process_Group_Processes.jpg License: Public domain Contributors: Project Management Guide Original
artist: DEPARTMENT OF VETERANS AFFAIRS Office of Information and Technology
• File:Pert_chart_colored.svg Source: https://upload.wikimedia.org/wikipedia/commons/3/37/Pert_chart_colored.svg License: Public domain Contributors: This file was derived from Pert chart colored.gif: <a href='//commons.wikimedia.org/wiki/File:Pert_
chart_colored.gif' class='image'><img alt='Pert chart colored.gif' src='https://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/
Pert_chart_colored.gif/50px-Pert_chart_colored.gif' width='50' height='31' srcset='https://upload.wikimedia.org/wikipedia/commons/
thumb/b/b9/Pert_chart_colored.gif/75px-Pert_chart_colored.gif 1.5x, https://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/
Pert_chart_colored.gif/100px-Pert_chart_colored.gif 2x' data-file-width='309' data-file-height='190' /></a>
Original artist: Pert_chart_colored.gif: Original uploader was Jeremykemp at en.wikipedia
• File:Portal-puzzle.svg Source: https://upload.wikimedia.org/wikipedia/en/f/fd/Portal-puzzle.svg License: Public domain Contributors: ?
Original artist: ?
• File:Prince2_procces_model_.jpg Source: https://upload.wikimedia.org/wikipedia/en/b/bc/Prince2_procces_model_.jpg License: Ccby-sa-3.0 Contributors: ? Original artist: ?
• File:Project_Management_(phases).png Source:
https://upload.wikimedia.org/wikipedia/commons/b/bb/Project_Management_
%28phases%29.png License: GFDL Contributors: Own work Original artist: Alphamu57
• File:Project_Management_(project_control).png
Source:
https://upload.wikimedia.org/wikipedia/commons/5/57/Project_
Management_%28project_control%29.png License: GFDL Contributors: Own work Original artist: Alphamu57
• File:Project_development_stages.jpg Source: https://upload.wikimedia.org/wikipedia/commons/7/74/Project_development_stages.
jpg License: Public domain Contributors: Project Management Guide Original artist: DEPARTMENT OF VETERANS AFFAIRS Office of Information and Technology
• File:Society.svg Source: https://upload.wikimedia.org/wikipedia/commons/5/5b/Society.svg License: CC-BY-SA-3.0 Contributors: own
work based on Image:Society.png by MisterMatt originally from English Wikipedia (en:Image:Society.png) Original artist: MesserWoland
• File:Symbol_book_class2.svg Source: https://upload.wikimedia.org/wikipedia/commons/8/89/Symbol_book_class2.svg License: CC
BY-SA 2.5 Contributors: Mad by Lokal_Profil by combining: Original artist: Lokal_Profil
• File:Trajan'{}s_Column_(Roman_Soldiers_Building_a_Fortress).png Source: https://upload.wikimedia.org/wikipedia/commons/f/
f5/Trajan%27s_Column_%28Roman_Soldiers_Building_a_Fortress%29.png License: CC-BY-SA-3.0 Contributors: courtesy of F.Yegul
Original artist: Fikret Yegul
• File:Wikiquote-logo.svg Source: https://upload.wikimedia.org/wikipedia/commons/f/fa/Wikiquote-logo.svg License: Public domain
Contributors: ? Original artist: ?
• File:Xp-loop_with_time_frames.svg Source: https://upload.wikimedia.org/wikipedia/commons/1/1b/Xp-loop_with_time_frames.svg
License: CC BY-SA 3.0 Contributors: Own work by uploader, based on Image:Xp-loop.png by Michael Hüttermann Original artist: Marcel
Douwe Dekker

8.3

Content license

• Creative Commons Attribution-Share Alike 3.0

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close