Uniqueness of a project
(Created page with "==Abstract== Here you will write your draft for your wiki article, include at least 1 reference. After add your abstract down in this page there is three buttons: Save page ...") |
|||
| Line 1: | Line 1: | ||
==Abstract== | ==Abstract== | ||
| − | + | Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as: | |
| − | + | “A project consists of a '''unique''' set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”<ref name="ISO">ISO-21500, 2013.</ref>. | |
| − | + | ||
| − | + | ||
| − | + | Furthermore, the Project Management Institute (PMI) defines a project as: | |
| − | + | “A project is a temporary endeavor undertaken to create a '''unique''' product or service”. <ref name="PMBOK"> Project Management Institute, '''A Guide to the Project Management Body of Knowledge (PMBOK® Guide)''', 5th Edition, 2013.</ref> | |
| + | |||
| + | Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”. | ||
| + | |||
| + | In short the "Volume vs Variety" <ref name="HARVEY"> Harvey Maylor, '''Project Management''', 4th Edition, 2010, page 7-9.</ref> of processes in the project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted subject to the benefits and challenges of having a unique project vs. a non-unique project. | ||
| + | |||
| + | |||
| + | |||
| + | ==The Big Idea== | ||
| + | |||
| + | ==Applications== | ||
| + | |||
| + | ==Limitations== | ||
| + | |||
| + | |||
| + | |||
| + | ==Annotated bibliography== | ||
| + | <references/> | ||
Revision as of 01:57, 13 February 2018
Contents |
Abstract
Projects are per definition unique. According to the worldwide federation of national standards bodies, International Organization for Standardization (ISO), a project is defined as:
“A project consists of a unique set of processes consisting of coordinated and controlled activities with start and end dates, performed to achieve project objectives…”[1].
Furthermore, the Project Management Institute (PMI) defines a project as:
“A project is a temporary endeavor undertaken to create a unique product or service”. [2]
Likewise, many other definitions state that projects are unique, and must have a degree of novelty in terms of time, team carrying out the task or product being provided. But since some project are more unique than others, how should the project manager decide whether to address and handle the task as a project or as a business activity? In other words, how does one distinguish between what is a project and what is not, subject to the uniqueness? This article strive to answer these questions based on a project management methode described in Maylor, H “Project Management”.
In short the "Volume vs Variety" [3] of processes in the project are considered in order to thoroughly define the uniqueness of a that particular project. A further discussion is thus conducted subject to the benefits and challenges of having a unique project vs. a non-unique project.
