Skip to content

Commit 1c2b570

Browse files
Copilotrdmueller
andcommitted
Add PERT semantic anchor (English & German) with catalog entry
Co-authored-by: rdmueller <1856308+rdmueller@users.noreply.github.com> Agent-Logs-Url: https://github.com/LLM-Coding/Semantic-Anchors/sessions/918f688f-5676-406b-b848-a17d79474519
1 parent 3b84bf8 commit 1c2b570

7 files changed

Lines changed: 153 additions & 5 deletions

File tree

docs/anchors/pert.adoc

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
= PERT
2+
:categories: strategic-planning
3+
:roles: product-owner, business-analyst, team-lead, consultant, educator
4+
:related: moscow, user-story-mapping, impact-mapping
5+
:proponents: D.G. Malcolm, J.H. Roseboom, C.E. Clark, W. Fazar
6+
:tags: pert, project-planning, estimation, schedule, uncertainty, three-point-estimation, critical-path, network-diagram
7+
:tier: 2
8+
9+
[%collapsible]
10+
====
11+
Full Name:: Program Evaluation and Review Technique
12+
13+
Also known as:: Three-Point Estimation, PERT Network Analysis
14+
15+
[discrete]
16+
== *Core Concepts*:
17+
18+
Three-Time Estimation:: Each activity requires three duration estimates: Optimistic (O) — best case if everything goes well; Most Likely (M) — realistic expected duration; Pessimistic (P) — worst case if problems arise
19+
20+
PERT Formula:: Weighted average: *E = (O + 4M + P) / 6* — weights the most likely estimate four times more than the extreme estimates
21+
22+
Standard Deviation:: *σ = (P − O) / 6* — quantifies schedule uncertainty per activity; used to calculate confidence intervals for the project completion date
23+
24+
Network Diagram:: Activities are represented as nodes or arrows in a directed acyclic graph; dependencies between activities are modelled explicitly
25+
26+
Critical Path:: The longest path through the network determines the minimum project duration; any delay on the critical path delays the whole project
27+
28+
Float / Slack:: Time an activity can be delayed without affecting the project end date; activities on the critical path have zero float
29+
30+
Probabilistic Scheduling:: Unlike CPM (which uses single-point estimates), PERT treats duration as a random variable, enabling statistical confidence ranges for milestones
31+
32+
Origin:: Developed in 1958 by D.G. Malcolm, J.H. Roseboom, C.E. Clark, and W. Fazar at Booz Allen Hamilton for the US Navy's Polaris submarine missile programme
33+
34+
Key Proponents:: D.G. Malcolm, J.H. Roseboom, C.E. Clark, W. Fazar ("Application of a Technique for Research and Development Program Evaluation", 1959)
35+
36+
[discrete]
37+
== *When to Use*:
38+
39+
* Estimating effort and schedule for projects with significant uncertainty
40+
* Planning R&D, software development, or any novel work where duration is hard to predict
41+
* Communicating schedule risk and confidence levels to stakeholders
42+
* Identifying the critical path to focus risk management and resource allocation
43+
* Complementing Story Points or T-shirt sizing with a probabilistic time dimension
44+
45+
[discrete]
46+
== *Related Anchors*:
47+
48+
* <<moscow,MoSCoW>>
49+
* <<user-story-mapping,User Story Mapping>>
50+
* <<impact-mapping,Impact Mapping>>
51+
====

docs/anchors/pert.de.adoc

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
= PERT
2+
:categories: strategic-planning
3+
:roles: product-owner, business-analyst, team-lead, consultant, educator
4+
:related: moscow, user-story-mapping, impact-mapping
5+
:proponents: D.G. Malcolm, J.H. Roseboom, C.E. Clark, W. Fazar
6+
:tags: pert, project-planning, estimation, schedule, uncertainty, three-point-estimation, critical-path, network-diagram
7+
8+
[%collapsible]
9+
====
10+
Vollständiger Name:: Program Evaluation and Review Technique (Programmbewertungs- und Überprüfungstechnik)
11+
12+
Auch bekannt als:: Drei-Punkte-Schätzung, PERT-Netzplananalyse
13+
14+
[discrete]
15+
== *Kernkonzepte*:
16+
17+
Drei-Punkte-Schätzung:: Jede Aktivität benötigt drei Dauerschätzungen: Optimistisch (O) — bester Fall, wenn alles reibungslos läuft; Wahrscheinlichst (M) — realistisch erwartete Dauer; Pessimistisch (P) — schlimmster Fall bei auftretenden Problemen
18+
19+
PERT-Formel:: Gewichteter Mittelwert: *E = (O + 4M + P) / 6* — die wahrscheinlichste Schätzung wird viermal stärker gewichtet als die Extremwerte
20+
21+
Standardabweichung:: *σ = (P − O) / 6* — quantifiziert die Terminunsicherheit je Aktivität; wird zur Berechnung von Konfidenzintervallen für den Projektabschlusstermin verwendet
22+
23+
Netzplan:: Aktivitäten werden als Knoten oder Pfeile in einem gerichteten azyklischen Graphen dargestellt; Abhängigkeiten zwischen Aktivitäten werden explizit modelliert
24+
25+
Kritischer Pfad:: Der längste Pfad durch das Netzwerk bestimmt die minimale Projektdauer; jede Verzögerung auf dem kritischen Pfad verzögert das gesamte Projekt
26+
27+
Puffer / Schlupf:: Zeit, um die eine Aktivität verzögert werden kann, ohne den Projektendtermin zu beeinflussen; Aktivitäten auf dem kritischen Pfad haben keinen Puffer
28+
29+
Probabilistische Terminplanung:: Im Gegensatz zur CPM (die Einzelpunktschätzungen verwendet) behandelt PERT Dauern als Zufallsvariablen und ermöglicht statistische Konfidenzintervalle für Meilensteine
30+
31+
Ursprung:: 1958 von D.G. Malcolm, J.H. Roseboom, C.E. Clark und W. Fazar bei Booz Allen Hamilton für das Polaris-U-Boot-Raketenprogramm der US Navy entwickelt
32+
33+
Schlüsselvertreter:: D.G. Malcolm, J.H. Roseboom, C.E. Clark, W. Fazar („Application of a Technique for Research and Development Program Evaluation", 1959)
34+
35+
[discrete]
36+
== *Wann zu verwenden*:
37+
38+
* Aufwands- und Terminschätzung für Projekte mit erheblicher Unsicherheit
39+
* Planung von F&E-, Softwareentwicklungs- oder anderen neuartigen Vorhaben, bei denen Dauern schwer vorherzusagen sind
40+
* Kommunikation von Terminrisiken und Konfidenzwerten gegenüber Stakeholdern
41+
* Identifikation des kritischen Pfads zur gezielten Risikobewältigung und Ressourcenzuteilung
42+
* Ergänzung von Story Points oder T-Shirt-Größen um eine probabilistische Zeitdimension
43+
44+
*Verwandte Anker*:
45+
46+
* <<moscow,MoSCoW>>
47+
* <<user-story-mapping,User Story Mapping>>
48+
* <<impact-mapping,Impact Mapping>>
49+
====

skill/semantic-anchor-translator/references/catalog.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -351,3 +351,8 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
351351
### SWOT
352352
- **Proponents:** Albert Humphrey
353353
- **Core:** Strengths, Weaknesses, Opportunities, Threats — internal vs. external strategic analysis
354+
355+
### PERT (Program Evaluation and Review Technique)
356+
- **Also known as:** Three-Point Estimation, PERT Network Analysis
357+
- **Proponents:** D.G. Malcolm, J.H. Roseboom, C.E. Clark, W. Fazar
358+
- **Core:** Stochastic project scheduling using three-point estimates per activity (Optimistic, Most Likely, Pessimistic); weighted average formula E = (O + 4M + P) / 6; standard deviation σ = (P − O) / 6; critical path analysis; probabilistic milestone confidence intervals

website/public/data/anchors.json

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1903,6 +1903,43 @@
19031903
"filePath": "docs/anchors/owasp-top-10.adoc",
19041904
"tier": 3
19051905
},
1906+
{
1907+
"id": "pert",
1908+
"title": "PERT",
1909+
"categories": [
1910+
"strategic-planning"
1911+
],
1912+
"roles": [
1913+
"product-owner",
1914+
"business-analyst",
1915+
"team-lead",
1916+
"consultant",
1917+
"educator"
1918+
],
1919+
"related": [
1920+
"moscow",
1921+
"user-story-mapping",
1922+
"impact-mapping"
1923+
],
1924+
"proponents": [
1925+
"D.G. Malcolm",
1926+
"J.H. Roseboom",
1927+
"C.E. Clark",
1928+
"W. Fazar"
1929+
],
1930+
"tags": [
1931+
"pert",
1932+
"project-planning",
1933+
"estimation",
1934+
"schedule",
1935+
"uncertainty",
1936+
"three-point-estimation",
1937+
"critical-path",
1938+
"network-diagram"
1939+
],
1940+
"filePath": "docs/anchors/pert.adoc",
1941+
"tier": 2
1942+
},
19061943
{
19071944
"id": "plain-english-strunk-white",
19081945
"title": "Plain English according to Strunk & White",

website/public/data/categories.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,7 @@
148148
"cynefin-framework",
149149
"impact-mapping",
150150
"jobs-to-be-done",
151+
"pert",
151152
"pugh-matrix",
152153
"swot",
153154
"wardley-mapping"

website/public/data/metadata.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
{
2-
"generatedAt": "2026-03-23T13:51:09.826Z",
2+
"generatedAt": "2026-03-26T09:24:28.368Z",
33
"version": "1.0.0",
44
"counts": {
5-
"anchors": 106,
5+
"anchors": 107,
66
"categories": 12,
77
"roles": 12
88
},
99
"statistics": {
10-
"averageRolesPerAnchor": "3.10",
10+
"averageRolesPerAnchor": "3.12",
1111
"averageCategoriesPerAnchor": "1.01",
12-
"anchorsWithTags": 66,
13-
"anchorsWithRelated": 37
12+
"anchorsWithTags": 67,
13+
"anchorsWithRelated": 38
1414
}
1515
}

website/public/data/roles.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@
1818
"linddun",
1919
"mece",
2020
"moscow",
21+
"pert",
2122
"plain-english-strunk-white",
2223
"prd",
2324
"problem-space-nvc",
@@ -49,6 +50,7 @@
4950
"moscow",
5051
"myers-briggs-type-indicator",
5152
"owasp-top-10",
53+
"pert",
5254
"plain-english-strunk-white",
5355
"problem-space-nvc",
5456
"pyramid-principle",
@@ -109,6 +111,7 @@
109111
"gutes-deutsch-wolf-schneider",
110112
"mental-model-according-to-naur",
111113
"myers-briggs-type-indicator",
114+
"pert",
112115
"plain-english-strunk-white",
113116
"socratic-method",
114117
"solid-principles",
@@ -133,6 +136,7 @@
133136
"morphological-box",
134137
"moscow",
135138
"myers-briggs-type-indicator",
139+
"pert",
136140
"prd",
137141
"problem-space-nvc",
138142
"pugh-matrix",
@@ -357,6 +361,7 @@
357361
"moscow",
358362
"myers-briggs-type-indicator",
359363
"owasp-top-10",
364+
"pert",
360365
"prd",
361366
"problem-space-nvc",
362367
"pugh-matrix",

0 commit comments

Comments
 (0)