Project Management: Difference between revisions

From IT Process Wiki
No edit summary
Line 1: Line 1:
<seo metakeywords="project management, what is project management" metadescription="In recent years, project management has become more and more important. The reason is that very often for modern enterprises it is vital to ..." />
<itpmch><title>Project Management | IT Process Wiki</title>
<meta name="keywords" content="project management basics, what is project management, how to define project managment" />
<meta name="description" content="Project Management Basics: What is project management? How to structure and manage a project? Which roles are involved? ..." />
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - Project Management|100px
Image:ITIL-Wiki-de-es.jpg|DE - ES - Project Management|100px
Line 6: Line 9:
desc none
desc none
</imagemap>
</imagemap>
<br style="clear:both;"/>


=== What is Project Management? ===
<html><div itemscope="itemscope" itemtype="https://schema.org/WebPage"><!-- define schema.org/WebPage --><p></html>
<p id="Project-Management-Basics">&nbsp;</p>
 
<imagemap>
Image:Project-management-basics.jpg|left|[[#Project-Management-Basics|Project Management Basics]]|699px|thumb|alt=Project management basics: What is project management - project management roles, project management stages and templates/ checklists.
rect 18 86 171 366 [[Project Management#What_is_Project_Management.3F|How to define project management]]
rect 187 85 342 367 [[Project Management#Project_Organization|Who is responsibel/ involved?]]
rect 356 85 510 367 [[Project Management#Project_Stages:_Objectives_and_Tasks|How to structure a project]]
rect 525 84 679 367 [[Project Management - Templates, Checklists and Tips|How to manage a project? - Templates and checklists]]
rect 0 0 699 401 [[Project Management|What is project management?]]
desc bottom-left
</imagemap>
<br style="clear:both;"/>


In recent years, '''project management''' has become more and more important. The reason is that very often for modern enterprises it is vital to respond quickly and flexibly to new requirements.  
In recent years, '''project management''' has become more and more important. The reason is that very often for modern enterprises it is vital to respond quickly and flexibly to new requirements.  
<p>&nbsp;</p>
===What is Project Management?===
----


When a business has to address a completely new task it is usually necessary that specialists from very different areas and corporate sectors work together. Here the definition of a project would make sense: It ensures a higher degree of flexibility as it goes beyond day-to-day operations. Project work provides the benefit of finding common solutions rapidly and effectively.  
When a business has to address a completely new task it is usually necessary that specialists from very different areas and corporate sectors work together. Here the definition of a project would make sense: It ensures a higher degree of flexibility as it goes beyond day-to-day operations. Project work provides the benefit of finding common solutions rapidly and effectively.  
Line 15: Line 36:
On the other hand, success of the project is not guaranteed, since its content is always new, contrary to business operations which are repetitive and have long been practiced in the company. Even when several approaches have been developed to achieve the project goal, the result is often incalculable.  
On the other hand, success of the project is not guaranteed, since its content is always new, contrary to business operations which are repetitive and have long been practiced in the company. Even when several approaches have been developed to achieve the project goal, the result is often incalculable.  


For these reasons, it is essential to have access to reliable project planning, concrete commitment of the necessary resources and, most important, clear rules for the project work (see: [[Project Management - Templates, Checklists and Tips|templates, checklists and tips for project management]]).  
<html><p>For these reasons, it is essential to have access to reliable project planning, concrete commitment of the necessary resources and, most important, clear rules for the project work (see: <a itemprop="significantLinks" href="https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Templates,_Checklists_and_Tips" title="Project Management - Templates, Checklists and Tips">templates, checklists and tips for project management</a>).  
 
</p><p>All these activities are summarized under the term <i><b><span itemprop="name Headline">Project Management</span></b></i>:
All these activities are summarized under the term "project management".
</p>
 
<ul><li> <i><b><span itemprop="description">Project management encompasses organization, planning, control and monitoring of all tasks and resources required to achieve the defined project goals and objectives.</span></b></i>
'''Project management encompasses organization, planning, control and monitoring of all tasks and resources required to achieve the defined project goals and objectives. '''
</li></ul><p></html>


Project management is a [[Project Management Checklist - Leadership techniques in a project|managerial task]] and must be distinguished from the practical tasks of the operational project work.
Project management is a [[Project Management Checklist - Leadership techniques in a project|managerial task]] and must be distinguished from the practical tasks of the operational project work.


<p>&nbsp;</p>


 
==What is a Project?==
=== What is a Project? ===


Frequently, a task is misleadingly classified as a '''project'''. As a rule, the following general conditions should be fulfilled for tasks to be completed in the form of a project:  
Frequently, a task is misleadingly classified as a '''project'''. As a rule, the following general conditions should be fulfilled for tasks to be completed in the form of a project:  
Line 31: Line 52:
The task
The task


* is unique, i.e. no routine task to be completed as part of the day-to-day operational business,  
*is unique, i.e. no routine task to be completed as part of the day-to-day operational business,  
* is a novelty,  
*is a novelty,  
* is subject  to constraints by timescale, funding and staff,  
*is subject  to constraints by timescale, funding and staff,  
* has a complex technical and organizational structure,  
*has a complex technical and organizational structure,  
* has [[Project Management Checklist - Defining the Project Goal|clear performance targets]] with regard to the agreed specification and quality,  
*has [[Project Management Checklist - Defining the Project Goal|clear performance targets]] with regard to the agreed specification and quality,  
* is implemented in teamwork, generally by cross-disciplinary and cross-hierarchy [[Project Management Checklist - Competencies of the team members|project teams]].
*is implemented in teamwork, generally by cross-disciplinary and cross-hierarchy [[Project Management Checklist - Competencies of the team members|project teams]].


<p>&nbsp;</p>


 
==Successful Implementation of Projects==
==== Successful Implementation of Projects ====


A project can be considered successful if the output as defined in the project order has been delivered within the scheduled time frame and budgets and with the planned resources.  
A project can be considered successful if the output as defined in the project order has been delivered within the scheduled time frame and budgets and with the planned resources.  
Line 48: Line 69:
However, the risk of failing can be considerably reduced through rigorous project management ensuring that  
However, the risk of failing can be considerably reduced through rigorous project management ensuring that  


* the various people involved act in a co-ordinated way,  
*the various people involved act in a co-ordinated way,  
* the complexity of the tasks is reduced through structuring,  
*the complexity of the tasks is reduced through structuring,  
* the project contents are subdivided into meaningful units to ensure clarity and ease of handling,
*the project contents are subdivided into meaningful units to ensure clarity and ease of handling,
* the goals are achieved and  
*the goals are achieved and  
* neither deadlines nor financial limits are exceeded.  
*neither deadlines nor financial limits are exceeded.  


Ultimately, very different factors contribute to the success of a project. These factors range from technical issues to organizational agreements and interpersonal aspects.  
Ultimately, very different factors contribute to the success of a project. These factors range from technical issues to organizational agreements and interpersonal aspects.  


<p>&nbsp;</p>


 
==Project Organization==
=== Project Organization ===


So as we can see from the above, a project cannot be executed as part of the usual day-to-day business, but has its own rules.
So as we can see from the above, a project cannot be executed as part of the usual day-to-day business, but has its own rules.
Line 64: Line 85:
An appropriate project organization helps minimize frictional losses and delays in the project. It serves to
An appropriate project organization helps minimize frictional losses and delays in the project. It serves to


* assign authority, tasks and responsibilities clearly,
*assign authority, tasks and responsibilities clearly,
* manage the co-operation, communication and co-ordination of all people involved in the project,  
*manage the co-operation, communication and co-ordination of all people involved in the project,  
* ensure rapid response to changes in the general conditions or the project goals and objectives.
*ensure rapid response to changes in the general conditions or the project goals and objectives.
 


<p>&nbsp;</p>


==== Organizational Structure (Definition of Project Tasks and Responsibilities) ====
====Organizational Structure (Definition of Project Tasks and Responsibilities)====


When it comes to multidisciplinary and multi-department teams working together on individual tasks for a limited period of time, it is essential that the organizational structures in the company are flexible, e.g. to allow direct co-operation between specialists. The inclusion of people from different areas of expertise, organizational structures and hierarchical levels raises the issue of clearly defined project responsibilities. Moreover, a rapid flow of information and close communication is required.  
When it comes to multidisciplinary and multi-department teams working together on individual tasks for a limited period of time, it is essential that the organizational structures in the company are flexible, e.g. to allow direct co-operation between specialists. The inclusion of people from different areas of expertise, organizational structures and hierarchical levels raises the issue of clearly defined project responsibilities. Moreover, a rapid flow of information and close communication is required.  
Line 80: Line 101:
It has proved useful to define distinct tasks and responsibilities, i.e. project roles in an organizational structure:
It has proved useful to define distinct tasks and responsibilities, i.e. project roles in an organizational structure:


* The [[Project Management Checklist - Project Organization#Project Executive|Executive]] is the person or group of persons who allocates funding to the project. He is the key decision-maker and is ultimately responsible for the success of the project.  
*The [[Project Management Checklist - Project Organization#Project Executive|Executive]] is the person or group of persons who allocates funding to the project. He is the key decision-maker and is ultimately responsible for the success of the project.  


* The [[Project Management Checklist - Project Organization#Project Board Steering Committee|Project Board (often referred to as Steering Committee)]] represents the Executive and, as the highest-level body, is responsible for providing guidance on the overall strategic direction of the project. It makes the most important decisions with regard to the goal and the scope of the project.  
*The [[Project Management Checklist - Project Organization#Project Board Steering Committee|Project Board (often referred to as Steering Committee)]] represents the Executive and, as the highest-level body, is responsible for providing guidance on the overall strategic direction of the project. It makes the most important decisions with regard to the goal and the scope of the project.  


* The [[Project Management Checklist - Competencies of the project manager|Project Manager]] is responsible for the [[Project Management Checklist - Project Organization#Project Manager|operational management]] of the project.  
*The [[Project Management Checklist - Competencies of the project manager|Project Manager]] is responsible for the [[Project Management Checklist - Project Organization#Project Manager|operational management]] of the project.  


* The [[Project Management Checklist - Competencies of the team members|Project Team]] is in charge of the technical project work.
*The [[Project Management Checklist - Competencies of the team members|Project Team]] is in charge of the technical project work.


<p>&nbsp;</p>


 
====Operational Structure (Planning of the Project Structure)====
==== Operational Structure (Planning of the Project Structure) ====


It is proven practice to break down the project cycle into different stages. It is a planning approach that provides the possibility of obtaining measurable interim results during project execution, thus lowering the project risks considerably. Moreover, it is much easier to discuss and decide on the course to be set for the project if data regarding milestone results and deviations from plans are available.
It is proven practice to break down the project cycle into different stages. It is a planning approach that provides the possibility of obtaining measurable interim results during project execution, thus lowering the project risks considerably. Moreover, it is much easier to discuss and decide on the course to be set for the project if data regarding milestone results and deviations from plans are available.
Line 96: Line 117:
The aim of stage planning is to make the project progress transparent.  
The aim of stage planning is to make the project progress transparent.  


<p>&nbsp;</p>


 
==Project Stages: Objectives and Tasks==
=== Project stages: objectives and tasks ===
<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" valign="top"
{| border="1" cellpadding="5" cellspacing="0" valign="top"
|-
|-
| valign="top"  colspan="3" style="background:#ffffdd;" align="center"| '''Overview: Operational Organization of Project Processes ''' <br />Project stages: objectives and tasks<br />
| colspan="3" style="vertical-align:top; background:#ffcc66;text-align:center;" | '''Overview: Operational Organization of Project Processes ''' <br />Project stages: objectives and tasks<br />
|-
|-
! width="20%" align="center" style="background:#ffffbb;" | Project Stage  
!style="background:#ffffdd; width: 20%; text-align:center" | Project Stage  
! width="35%" align="center" style="background:#ffffbb;" | Objectives
!style="background:#ffffdd; width: 35%; text-align:center" | Objectives
! align="center" style="background:#ffffbb;" | Tasks
!style="background:#ffffdd; vertical-align:top; text-align:center" | Tasks
|-
|-
| valign="top" | '''Project Initiation'''
|style="vertical-align:top;" | '''Project Initiation'''
| valign="top" |  
|style="vertical-align:top;" |  
* Project goal is identified  
*Project goal is identified  
* Feasibility is checked  
*Feasibility is checked  
* Decision about execution of the project is taken
*Decision about execution of the project is taken


|
|
* Clarify assignments and tasks
*Clarify assignments and tasks
* Perform cost assessment  
*Perform cost assessment  
* Carry out risk and PESTLE analysis (P=Political, E=Economic, S=Sociological, T=Technological, L=Legal, E=Environmental)  
*Carry out risk and PESTLE analysis (P=Political, E=Economic, S=Sociological, T=Technological, L=Legal, E=Environmental)  
* Set-up rough project planning  
*Set-up rough project planning  
* Build up project organization  
*Build up project organization  
* Hold kick-off meeting
*Hold kick-off meeting


|-
|-
| valign="top" | '''Project Planning'''
|style="vertical-align:top;" | '''Project Planning'''
| valign="top" |  
|style="vertical-align:top;" |  
* Work packages are defined  
*Work packages are defined  
* Foundations for successful completion of the project within the execution phase are laid
*Foundations for successful completion of the project within the execution phase are laid


|
|
* Define, evaluate and assign work packages  
*Define, evaluate and assign work packages  
* Set up time schedule  
*Set up time schedule  
* Establish cost schedule
*Establish cost schedule
* Prepare the working environment (project infrastructure)  
*Prepare the working environment (project infrastructure)  


|-
|-
| valign="top" | '''Project Execution'''
|style="vertical-align:top;" | '''Project Execution'''
| valign="top" |  
|style="vertical-align:top;" |  
* Project outcomes are defined and approved
*Project outcomes are defined and approved


|
|
* Execute work packages  
*Execute work packages  
* Carry out project controlling  
*Carry out project controlling  
* Continuous risk and quality management  
*Continuous risk and quality management  
* Initiate and co-ordinate project changes, as required
*Initiate and co-ordinate project changes, as required
* Carry out the technical acceptance  
*Carry out the technical acceptance  


|-
|-
| valign="top" | '''Project Closure'''
|style="vertical-align:top;" | '''Project Closure'''
| valign="top" |  
|style="vertical-align:top;" |  
* Critical project retrospective (dates, costs, project development) is done  
*Critical project retrospective (dates, costs, project development) is done  
* Project organization is dissolved
*Project organization is dissolved
* Project is formally completed
*Project is formally completed


| valign="top" |
|style="vertical-align:top;" |
* Prepare end project report  
*Prepare end project report  
* Final presentation  
*Final presentation  
* Hand over and assure results
*Hand over and assure results


|}
|}
Line 162: Line 183:
<p>&nbsp;</p>
<p>&nbsp;</p>


=== Project Management Standards ===
==Project Management Standards==


The following three Project Management standards have been accepted worldwide:
The following three Project Management standards have been accepted worldwide:


* Project Management Body of Knowledge ([http://www.pmi.org/PMBOK-Guide-and-Standards.aspx PMBOK]), Project Management Institute (PMI),  
*Project Management Body of Knowledge ([http://www.pmi.org/PMBOK-Guide-and-Standards.aspx PMBOK]), Project Management Institute (PMI),  
* PRojects IN Controlled Environments ([http://www.prince-officialsite.com PRINCE2]), a standard which, like [[ITIL Processes|ITIL]], was developed by the Office of Government Commerce (OGC)  
*PRojects IN Controlled Environments ([http://www.prince-officialsite.com PRINCE2]), a standard which, like [[ITIL Processes|ITIL]], was developed by the Office of Government Commerce (OGC)  
* the IPMA Competence Baseline ([http://ipma.ch/certification/competence/ipma-competence-baseline/ ICB]) of the International Project Management Association (IPMA).
*the IPMA Competence Baseline ([http://ipma.ch/certification/competence/ipma-competence-baseline/ ICB]) of the International Project Management Association (IPMA).


<p>&nbsp;</p>
<p>&nbsp;</p>


=== Links and additional information ===
==Links==


[1] John S Stewart. "[http://internationalbestpracticeinstitute.wordpress.com/2013/02/22/quick-guide-to-prince2/ Quick Guide to PRINCE2]". -- Blog IBPI (The International Best Practice Institute) www.ibpi.org, February 22, 2013. Retrieved February 27, 2013.
[1] John S Stewart. "[http://internationalbestpracticeinstitute.wordpress.com/2013/02/22/quick-guide-to-prince2/ Quick Guide to PRINCE2&reg;]". -- Blog IBPI (The International Best Practice Institute) www.ibpi.org, February 22, 2013. Retrieved February 27, 2013.
 
[2] Axelos - Global Best Practice. "[http://www.axelos.com/Knowledge-Centre/White-Papers/#GEMS6541916 PRINCE2&reg; Introductory Overview and Business Benefits White Papers]"; "[http://www.axelos.com/Knowledge-Centre/White-Papers/#GEMS6541875 PRINCE2&reg; Technical White Papers]". -- Axelos, www.axelos.com. Retrieved January 29, 2014.


<p>&nbsp;</p>
<p>&nbsp;</p>


''' Forward to: '''
==IT Process Wiki: Project Management Templates==


&#8594; '''[[Project Management - Templates, Checklists and Tips|Templates, checklists and tips for project management]]'''
&#8594; '''[[Project Management - Templates, Checklists and Tips|Templates, checklists and tips for project management]]'''
Line 184: Line 207:
<p>&nbsp;</p>
<p>&nbsp;</p>


<html><a rel="author" href="https://plus.google.com/113316270668629760475"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a></html>
==[ Infobox ]==
 
<html><table class="wikitable">
<tr>
<td>Link to this page:</td>
<td><a itemprop="url" href="https://wiki.en.it-processmaps.com/index.php/Project_Management">https://wiki.en.it-processmaps.com/index.php/Project_Management</a></td>
</tr>
<tr>
<td>Languages:</td>
<td><span itemprop="inLanguage" content="en">English</span> | <span><a itemprop="citation" class="external text" href="https://wiki.de.it-processmaps.com/index.php/Projektmanagement" title="Projektmanagement">Deutsch</a></span> | <span><a itemprop="citation" class="external text" href="https://wiki.es.it-processmaps.com/index.php/Gesti%C3%B3n_de_proyectos" title="Gestión de proyectos">espa&#xf1;ol</a></span></td>
</tr>
<tr>
<td>Image:</td>
<td style="vertical-align:top"><a itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/d/d1/Project-management-basics.jpg" title="What is Project Management">Project Management Basics (.JPG)</a></td>
</tr>
<tr>
<td>Author:</td>
<td><span itemprop="author">Andrea Kempter</span>, <span itemprop="creator copyrightHolder publisher">IT Process Maps</span> &nbsp;&nbsp; <a rel="author" href="https://plus.google.com/113316270668629760475"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a></td>
</tr>
</table>
 
<p>&nbsp;</p>
 
<p><small>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Project_Management#What_is_Project_Management.3F" itemprop="url"><span itemprop="title">Definition</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Project_Management#Successful_Implementation_of_Projects" itemprop="url"><span itemprop="title">Success factors</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Project_Management#Project_Organization" itemprop="url"><span itemprop="title">Project Organization</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Project_Management#Project_Stages:_Objectives_and_Tasks" itemprop="url"><span itemprop="title">Project Stages</span></a> ›
</span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a href="https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Templates,_Checklists_and_Tips" itemprop="url"><span itemprop="title">PM Templates</span></a>
</span>
</small></p>
</div><!-- end of schema.org/WebPage --><p></html>


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:Project Management|!]]
[[Category:Project Management|!]]
<!-- --- -->
<!-- --- -->

Revision as of 18:24, 29 January 2014

DE - ES - Project Managementdiese Seite auf Deutschesta página en español
DE - ES - Project Management


 

Project management basics: What is project management - project management roles, project management stages and templates/ checklists.How to define project managementWho is responsibel/ involved?How to structure a projectHow to manage a project? - Templates and checklistsWhat is project management?
Project Management Basics


In recent years, project management has become more and more important. The reason is that very often for modern enterprises it is vital to respond quickly and flexibly to new requirements.

 

What is Project Management?


When a business has to address a completely new task it is usually necessary that specialists from very different areas and corporate sectors work together. Here the definition of a project would make sense: It ensures a higher degree of flexibility as it goes beyond day-to-day operations. Project work provides the benefit of finding common solutions rapidly and effectively.

On the other hand, success of the project is not guaranteed, since its content is always new, contrary to business operations which are repetitive and have long been practiced in the company. Even when several approaches have been developed to achieve the project goal, the result is often incalculable.

For these reasons, it is essential to have access to reliable project planning, concrete commitment of the necessary resources and, most important, clear rules for the project work (see: templates, checklists and tips for project management).

All these activities are summarized under the term Project Management:

  • Project management encompasses organization, planning, control and monitoring of all tasks and resources required to achieve the defined project goals and objectives.

Project management is a managerial task and must be distinguished from the practical tasks of the operational project work.

 

What is a Project?

Frequently, a task is misleadingly classified as a project. As a rule, the following general conditions should be fulfilled for tasks to be completed in the form of a project:

The task

  • is unique, i.e. no routine task to be completed as part of the day-to-day operational business,
  • is a novelty,
  • is subject to constraints by timescale, funding and staff,
  • has a complex technical and organizational structure,
  • has clear performance targets with regard to the agreed specification and quality,
  • is implemented in teamwork, generally by cross-disciplinary and cross-hierarchy project teams.

 

Successful Implementation of Projects

A project can be considered successful if the output as defined in the project order has been delivered within the scheduled time frame and budgets and with the planned resources.

But careful: Due to the fact that a project is unique and complex, it also bears the risk of not yielding the desired results.

However, the risk of failing can be considerably reduced through rigorous project management ensuring that

  • the various people involved act in a co-ordinated way,
  • the complexity of the tasks is reduced through structuring,
  • the project contents are subdivided into meaningful units to ensure clarity and ease of handling,
  • the goals are achieved and
  • neither deadlines nor financial limits are exceeded.

Ultimately, very different factors contribute to the success of a project. These factors range from technical issues to organizational agreements and interpersonal aspects.

 

Project Organization

So as we can see from the above, a project cannot be executed as part of the usual day-to-day business, but has its own rules.

An appropriate project organization helps minimize frictional losses and delays in the project. It serves to

  • assign authority, tasks and responsibilities clearly,
  • manage the co-operation, communication and co-ordination of all people involved in the project,
  • ensure rapid response to changes in the general conditions or the project goals and objectives.

 

Organizational Structure (Definition of Project Tasks and Responsibilities)

When it comes to multidisciplinary and multi-department teams working together on individual tasks for a limited period of time, it is essential that the organizational structures in the company are flexible, e.g. to allow direct co-operation between specialists. The inclusion of people from different areas of expertise, organizational structures and hierarchical levels raises the issue of clearly defined project responsibilities. Moreover, a rapid flow of information and close communication is required.

When working together on the successful completion of a project, it is therefore necessary to determine right from the beginning who will participate in the project. It must be defined what their respective functions, responsibilities and competencies will be. Likewise, the information flow between the members of the project team must be determined.

Communication within the project team is often taken for granted; people tend to assume that this will function more or less automatically. However, guidelines may be helpful, here too, and may in the long run help to considerably reduce the amount of time which the members of the project team invest in the project.

It has proved useful to define distinct tasks and responsibilities, i.e. project roles in an organizational structure:

  • The Executive is the person or group of persons who allocates funding to the project. He is the key decision-maker and is ultimately responsible for the success of the project.
  • The Project Board (often referred to as Steering Committee) represents the Executive and, as the highest-level body, is responsible for providing guidance on the overall strategic direction of the project. It makes the most important decisions with regard to the goal and the scope of the project.
  • The Project Team is in charge of the technical project work.

 

Operational Structure (Planning of the Project Structure)

It is proven practice to break down the project cycle into different stages. It is a planning approach that provides the possibility of obtaining measurable interim results during project execution, thus lowering the project risks considerably. Moreover, it is much easier to discuss and decide on the course to be set for the project if data regarding milestone results and deviations from plans are available.

The aim of stage planning is to make the project progress transparent.

 

Project Stages: Objectives and Tasks


Overview: Operational Organization of Project Processes
Project stages: objectives and tasks
Project Stage Objectives Tasks
Project Initiation
  • Project goal is identified
  • Feasibility is checked
  • Decision about execution of the project is taken
  • Clarify assignments and tasks
  • Perform cost assessment
  • Carry out risk and PESTLE analysis (P=Political, E=Economic, S=Sociological, T=Technological, L=Legal, E=Environmental)
  • Set-up rough project planning
  • Build up project organization
  • Hold kick-off meeting
Project Planning
  • Work packages are defined
  • Foundations for successful completion of the project within the execution phase are laid
  • Define, evaluate and assign work packages
  • Set up time schedule
  • Establish cost schedule
  • Prepare the working environment (project infrastructure)
Project Execution
  • Project outcomes are defined and approved
  • Execute work packages
  • Carry out project controlling
  • Continuous risk and quality management
  • Initiate and co-ordinate project changes, as required
  • Carry out the technical acceptance
Project Closure
  • Critical project retrospective (dates, costs, project development) is done
  • Project organization is dissolved
  • Project is formally completed
  • Prepare end project report
  • Final presentation
  • Hand over and assure results

 

Project Management Standards

The following three Project Management standards have been accepted worldwide:

  • Project Management Body of Knowledge (PMBOK), Project Management Institute (PMI),
  • PRojects IN Controlled Environments (PRINCE2), a standard which, like ITIL, was developed by the Office of Government Commerce (OGC)
  • the IPMA Competence Baseline (ICB) of the International Project Management Association (IPMA).

 

Links

[1] John S Stewart. "Quick Guide to PRINCE2®". -- Blog IBPI (The International Best Practice Institute) www.ibpi.org, February 22, 2013. Retrieved February 27, 2013.

[2] Axelos - Global Best Practice. "PRINCE2® Introductory Overview and Business Benefits White Papers"; "PRINCE2® Technical White Papers". -- Axelos, www.axelos.com. Retrieved January 29, 2014.

 

IT Process Wiki: Project Management Templates

Templates, checklists and tips for project management

 

[ Infobox ]

Link to this page:
Languages: English | Deutsch | español
Image: Project Management Basics (.JPG)
Author: , IT Process Maps   

 

 ›  ›  ›  ›