This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:handbuch:kapitel_a:glossar [2009/12/16 16:50] admin |
en:handbuch:kapitel_a:glossar [2019/10/25 14:11] (current) |
||
---|---|---|---|
Line 14: | Line 14: | ||
- | ===== Approval(Freigabe)===== | + | ===== Approval ===== |
Approval refers to, depending on the context, approving a plan, sharing something for certain purposes or granting certain rights to a person. In project management, approval is described as the authorization to carry out subsequent work with defined contents. An approval is often associated with quality control and is usually defined as a milestone in the project plan. | Approval refers to, depending on the context, approving a plan, sharing something for certain purposes or granting certain rights to a person. In project management, approval is described as the authorization to carry out subsequent work with defined contents. An approval is often associated with quality control and is usually defined as a milestone in the project plan. | ||
Line 154: | Line 154: | ||
The milestone-trend-analysis is a future-related tool for controlling the schedule of a [[#Project|project]]: On periodical reporting dates the [[#Schedule|schedule]] of the project is re-estimated through retrieving trend data of the estimated milestone achievement. From the curve progression, a trend can be inferred through the adherence of deadlines of the project. The deadlines for the milestones can be administered in the document type [[en:handbuch:kapitel_2:2.02.06_trendtermin|deadlines]] and the analysis is visualized in the [[en:handbuch:kapitel_2:2.5.09_projektauswertung|project chart]]. | The milestone-trend-analysis is a future-related tool for controlling the schedule of a [[#Project|project]]: On periodical reporting dates the [[#Schedule|schedule]] of the project is re-estimated through retrieving trend data of the estimated milestone achievement. From the curve progression, a trend can be inferred through the adherence of deadlines of the project. The deadlines for the milestones can be administered in the document type [[en:handbuch:kapitel_2:2.02.06_trendtermin|deadlines]] and the analysis is visualized in the [[en:handbuch:kapitel_2:2.5.09_projektauswertung|project chart]]. | ||
- | {{:en:handbuch:kapitel_a:chart_mta1.jpg|}} | + | {{:en:handbuch:kapitel_a:mta1_sm.jpg|}} |
===== Multi-Project Management (=Program Management) ===== | ===== Multi-Project Management (=Program Management) ===== | ||
Line 343: | Line 343: | ||
===== SPI ===== | ===== SPI ===== | ||
- | The SPI (Schedule Performance Index) is the time-related performance key figure of the earned value analysis. It is formed from the ratio of earned value and estimated effort. This means that with a SPI of greater than 1.00 (100%) the project results are delivered faster than originally planned, and with a value of less than 1.00 (100%), the project is progressing too slowly. | + | The SPI (Schedule Performance Index) is the time-related performance key figure of the earned value analysis. It is formed from the ratio of earned value and estimated effort. This means that with an SPI of greater than 1.00 (100%) the project results are delivered faster than originally planned, and with a value of less than 1.00 (100%), the project is progressing too slowly. |
===== Sub-Project ===== | ===== Sub-Project ===== |