Plan/Manual/Definitions: Difference between revisions

From KDE Wiki Sandbox
< Plan‎ | Manual
m (remove the anchors from the translation domain)
(Add prevtex, nexttext to help translators)
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<languages />
<languages />
<translate>
<translate>
==Introduction==
==Definitions== <!--T:29-->


===Introduction=== <!--T:1-->
<!--T:2-->
In project management, terms may be used in different ways in different programs or different companies or project types. Looking at more exhaustive project management glossaries, one will find alternative definitions for most terms.
In project management, terms may be used in different ways in different programs or different companies or project types. Looking at more exhaustive project management glossaries, one will find alternative definitions for most terms.


<!--T:3-->
This list defines how certain terms are used in '''Plan'''.
This list defines how certain terms are used in '''Plan'''.


==Terms==
===Terms=== <!--T:4-->
</translate>
</translate>


<span id="Account"></span>
<span id="Account"></span>
<translate>
<translate>
<!--T:5-->
;Account
;Account
:An account is used in a ''Cost Breakdown Structure'' ([[#CBS|CBS]]) to represent a place where cost from [[#Task|tasks]] or [[#Resource|resources]] can be aggregated.
:An account is used in a ''Cost Breakdown Structure'' ([[#CBS|CBS]]) to represent a place where cost from [[#Task|tasks]] or [[#Resource|resources]] can be aggregated.
Line 18: Line 23:
<span id="Allocation"></span>
<span id="Allocation"></span>
<translate>
<translate>
<!--T:6-->
;Allocation
;Allocation
:Tasks are allocated to [[#Resource|Resources]] during the planning stage of the project. The actual assigment is done during scheduling. Note that assignment is not guaranteed as the resource may not be available.
:Tasks are allocated to [[#Resource|Resources]] during the planning stage of the project. The actual assignment is done during scheduling. Note that assignment is not guaranteed as the resource may not be available.
</translate>
</translate>


<span id="Assignment"></span>
<span id="Assignment"></span>
<translate>
<translate>
<!--T:7-->
;Assignment
;Assignment
:Tasks are assigned to [[#Resource|Resources]] during scheduling.
:Tasks are assigned to [[#Resource|Resources]] during scheduling.
Line 30: Line 37:
<span id="CBS"></span>
<span id="CBS"></span>
<translate>
<translate>
<!--T:8-->
;CBS
;CBS
:[[#Cost Breakdown Structure|Cost Breakdown Structure]]
:[[#Cost Breakdown Structure|Cost Breakdown Structure]]
Line 36: Line 44:
<span id="CPI"></span>
<span id="CPI"></span>
<translate>
<translate>
<!--T:9-->
;CPI
;CPI
:Is the ''Cost Performance Index'' and is equal to BCWP/ACWP. When this index is below 1, means that you are over budget. If the index is greater than 1 means that the costs are under budget.
:Is the ''Cost Performance Index'' and is equal to BCWP/ACWP. When this index is below 1, means that you are over budget. If the index is greater than 1 means that the costs are under budget.
Line 42: Line 51:
<span id="Cost_Breakdown_Structure"></span>
<span id="Cost_Breakdown_Structure"></span>
<translate>
<translate>
<!--T:10-->
;Cost Breakdown structure
;Cost Breakdown structure
:The CBS organizes [[#Account|accounts]] into a structure to enable cost to be aggregated independent of the [[#WBS|WBS]] and [[#RBS|RBS]].
:The CBS organizes [[#Account|accounts]] into a structure to enable cost to be aggregated independent of the [[#WBS|WBS]] and [[#RBS|RBS]].
Line 48: Line 58:
<span id="Estimate"></span>
<span id="Estimate"></span>
<translate>
<translate>
<!--T:11-->
;Estimate
;Estimate
:The estimate is the expected amount of effort or time needed to complete a [[#Task|task]].
:The estimate is the expected amount of effort or time needed to complete a [[#Task|task]].
Line 54: Line 65:
<span id="Milestone"></span>
<span id="Milestone"></span>
<translate>
<translate>
<!--T:12-->
;Milestone
;Milestone
:Todo
:A milestone is a [[#Task|task]] with an effort of 0.00h. It is typically used to mark a major outcome, for example the completion of a deliverable upon customer acceptance.
</translate>
</translate>


<span id="PERT"></span>
<span id="PERT"></span>
<translate>
<translate>
<!--T:13-->
;PERT
;PERT
:[[#Program Evaluation and Review Technique|Program Evaluation and Review Technique]]
:[[#Program Evaluation and Review Technique|Program Evaluation and Review Technique]]
Line 66: Line 79:
<span id="Program_Evaluation_and_Review_Technique"></span>
<span id="Program_Evaluation_and_Review_Technique"></span>
<translate>
<translate>
<!--T:14-->
;Program Evaluation and Review Technique
;Program Evaluation and Review Technique
:TODO
:The Program Evaluation and Review Technique is an enhancement to the Critical Path Method. [[#Task|Task]] effort estimates in CPM are point estimates, while [[#Task|task]] effort estimates in PERT are computed by weighting the Optimistic, Most Likely, and Pessimistic estimates (O+(4*M)+P)/6.
</translate>
</translate>


<span id="PERT_Distribution"></span>
<span id="PERT_Distribution"></span>
<translate>
<translate>
<!--T:15-->
;PERT Distribution
;PERT Distribution
:A simplified way to calculate Expected estimate from Optimistic-, Most Likely- and Pessimistic estimate.
:A simplified way to calculate Expected estimate from Optimistic-, Most Likely- and Pessimistic estimate.
Line 78: Line 93:
<span id="RBS"></span>
<span id="RBS"></span>
<translate>
<translate>
<!--T:16-->
;RBS
;RBS
:[[#Resource Breakdown Structure|Resource Breakdown Structure]]
:[[#Resource Breakdown Structure|Resource Breakdown Structure]]
Line 84: Line 100:
<span id="Resource_Breakdown_Structure"></span>
<span id="Resource_Breakdown_Structure"></span>
<translate>
<translate>
<!--T:17-->
;Resource Breakdown Structure
;Resource Breakdown Structure
:The RBS organizes resources into [[#Resource Group|resource groups]].
:The RBS organizes resources into [[#Resource Group|resource groups]].
Line 90: Line 107:
<span id="Resource"></span>
<span id="Resource"></span>
<translate>
<translate>
<!--T:18-->
;Resource
;Resource
:A resource can be of type ''Work'', ''Material'' or ''Team''. A resource must always belong to a [[#Resource Group|Resource Group]].
:A resource can be of type ''Work'', ''Material'' or ''Team''. A resource must always belong to a [[#Resource Group|Resource Group]].
Line 96: Line 114:
<span id="Resource_Group"></span>
<span id="Resource_Group"></span>
<translate>
<translate>
<!--T:19-->
;Resource Group
;Resource Group
:A resource group is used to group similar [[#Resource|resources]].
:A resource group is used to group similar [[#Resource|resources]].
Line 102: Line 121:
<span id="Resource_Team"></span>
<span id="Resource_Team"></span>
<translate>
<translate>
<!--T:20-->
;Resource Team
;Resource Team
:A [[#Resource|resource]] team is a resource that consists of a number of other resources.
:A [[#Resource|resource]] team is a resource that consists of a number of other resources.
Line 108: Line 128:
<span id="SPI"></span>
<span id="SPI"></span>
<translate>
<translate>
<!--T:21-->
;SPI
;SPI
:Is the Schedule Performance Index and is equal to BCWP/BCWS. When this index is below 1, means that you are behind schedule. If the index is greater than 1 means that you are ahead of the schedule.
:Is the Schedule Performance Index and is equal to BCWP/BCWS. When this index is below 1, means that you are behind schedule. If the index is greater than 1 means that you are ahead of the schedule.
Line 114: Line 135:
<span id="Summary_Task"></span>
<span id="Summary_Task"></span>
<translate>
<translate>
<!--T:22-->
;Summary Task
;Summary Task
:Todo
:A Summary Task has subordinate Sub-Tasks, and rolls up information based on the Sub-Tasks.
</translate>
</translate>


<span id="Task"></span>
<span id="Task"></span>
<translate>
<translate>
<!--T:23-->
;Task
;Task
:Todo
:A Task is a unit of work. [[#Resource|Resources]] are generally allocated at the Task level.
</translate>
</translate>


<span id="vCard"></span>
<span id="vCard"></span>
<translate>
<translate>
<!--T:24-->
;vCard
;vCard
:vCard is a file format standard for electronic business cards.
:vCard is a file format standard for electronic business cards.
Line 132: Line 156:
<span id="WBS"></span>
<span id="WBS"></span>
<translate>
<translate>
<!--T:25-->
;WBS
;WBS
:[[#Work Breakdown Structure|Work Breakdown Structure]]
:[[#Work Breakdown Structure|Work Breakdown Structure]]
Line 138: Line 163:
<span id="Work_Breakdown_Structure"></span>
<span id="Work_Breakdown_Structure"></span>
<translate>
<translate>
<!--T:26-->
;Work Breakdown Structure
;Work Breakdown Structure
:The WBS is used to break down large projects into manageable chuncks to ease planning and management.
:The WBS is used to break down large projects into manageable chunks to ease planning and management.


{|width="95%"
<!--T:28-->
| || ||align="right"|[[Plan/Manual/Main Work Area|Next]]
----
|-
{{Plan/Prevnext|prevpage=Introduction|prevtext=Introduction|indextext=Contents|nextpage=Context Help|nexttext=Context Help}}
| || ||align="right"|Main Work Area
|}
[[Category:Office]]
[[Category:Office]]
</translate>
</translate>

Latest revision as of 09:48, 7 April 2020

Other languages:

Definitions

Introduction

In project management, terms may be used in different ways in different programs or different companies or project types. Looking at more exhaustive project management glossaries, one will find alternative definitions for most terms.

This list defines how certain terms are used in Plan.

Terms

Account
An account is used in a Cost Breakdown Structure (CBS) to represent a place where cost from tasks or resources can be aggregated.

Allocation
Tasks are allocated to Resources during the planning stage of the project. The actual assignment is done during scheduling. Note that assignment is not guaranteed as the resource may not be available.

Assignment
Tasks are assigned to Resources during scheduling.

CBS
Cost Breakdown Structure

CPI
Is the Cost Performance Index and is equal to BCWP/ACWP. When this index is below 1, means that you are over budget. If the index is greater than 1 means that the costs are under budget.

Cost Breakdown structure
The CBS organizes accounts into a structure to enable cost to be aggregated independent of the WBS and RBS.

Estimate
The estimate is the expected amount of effort or time needed to complete a task.

Milestone
A milestone is a task with an effort of 0.00h. It is typically used to mark a major outcome, for example the completion of a deliverable upon customer acceptance.

PERT
Program Evaluation and Review Technique

Program Evaluation and Review Technique
The Program Evaluation and Review Technique is an enhancement to the Critical Path Method. Task effort estimates in CPM are point estimates, while task effort estimates in PERT are computed by weighting the Optimistic, Most Likely, and Pessimistic estimates (O+(4*M)+P)/6.

PERT Distribution
A simplified way to calculate Expected estimate from Optimistic-, Most Likely- and Pessimistic estimate.

RBS
Resource Breakdown Structure

Resource Breakdown Structure
The RBS organizes resources into resource groups.

Resource
A resource can be of type Work, Material or Team. A resource must always belong to a Resource Group.

Resource Group
A resource group is used to group similar resources.

Resource Team
A resource team is a resource that consists of a number of other resources.

SPI
Is the Schedule Performance Index and is equal to BCWP/BCWS. When this index is below 1, means that you are behind schedule. If the index is greater than 1 means that you are ahead of the schedule.

Summary Task
A Summary Task has subordinate Sub-Tasks, and rolls up information based on the Sub-Tasks.

Task
A Task is a unit of work. Resources are generally allocated at the Task level.

vCard
vCard is a file format standard for electronic business cards.

WBS
Work Breakdown Structure

Work Breakdown Structure
The WBS is used to break down large projects into manageable chunks to ease planning and management.