amadou/SecondBrain
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2026-07-23 15:17:59

Browse Source
This commit is contained in:
amadou
2026-07-23 15:17:59 +02:00
parent 8526cf4212
commit f35c5873fe
15 changed files with 74 additions and 124 deletions
Download Patch File Download Diff File Expand all files Collapse all files
10 Knowledge/CTO Academy/Project Management/Building My PM System.md
+15 -17
View File
@@ -1,5 +1,3 @@
# Building My PM System
Duration: 30--40 minutes
## Definition
@@ -253,18 +251,18 @@ stale because you are still expected to update everything.
## Related Concepts
- \[\[Projects vs Operations\]\]
- \[\[Outcomes and Definition of Done\]\]
- \[\[Scope and Scope Creep\]\]
- \[\[Milestones vs Tasks\]\]
- \[\[Dependencies\]\]
- \[\[Estimation and Forecasting\]\]
- \[\[Prioritization\]\]
- \[\[Capacity and WIP\]\]
- \[\[Risk Management\]\]
- \[\[Project Health\]\]
- \[\[Status Reporting\]\]
- \[\[Meetings and Follow-up\]\]
- \[\[Ownership and Delegation\]\]
- \[\[Portfolio Management\]\]
- \[\[Closing Projects\]\]
- [[Projects vs Operations]]
- [[Outcomes and Definition of Done]]
- [[Scope and Scope Creep]]
- [[Milestones vs Tasks]]
- [[Dependencies]]
- [[Estimation and Forecasting]]
- [[Prioritization]]
- [[Capacity and WIP]]
- [[Risk Management]]
- [[Project Health]]
- [[Status Reporting]]
- [[Meetings and Follow-up]]
- [[Ownership and Delegation]]
- [[Portfolio Management]]
- [[Closing Projects]]
10 Knowledge/CTO Academy/Project Management/Capacity and WIP.md
+8 -13
View File
@@ -1,5 +1,3 @@
# Capacity and WIP
Duration: 30--40 minutes
## Definition
@@ -80,18 +78,15 @@ operational load, improving automation, or accepting risk.
## How It Fits Into the Bigger Picture
This lesson builds on \[\[Projects vs Operations\]\], \[\[Outcomes and
Definition of Done\]\], \[\[Scope and Scope Creep\]\], and
\[\[Milestones vs Tasks\]\]. It prepares the project system to become
This lesson builds on [[Projects vs Operations]], [[Outcomes and Definition of Done]], [[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
more predictable and scalable.
## Related Concepts
- \[\[Milestones vs Tasks\]\]
- \[\[Dependencies\]\]
- \[\[Estimation and Forecasting\]\]
- \[\[Prioritization\]\]
- \[[Capacity and WIP](#capacity-and-wip)\]
- \[\[Risk Management\]\]
- \[\[Project Health\]\]
- \[\[Portfolio Management\]\]
- [[Milestones vs Tasks]]
- [[Dependencies]]
- [[Estimation and Forecasting]]
- [[Prioritization]]
- [[Risk Management]]
- [[Project Health]]
- [[Portfolio Management]]
10 Knowledge/CTO Academy/Project Management/Closing Projects.md
-1
View File
@@ -1,4 +1,3 @@
Duration: 30--40 minutes
## Definition
10 Knowledge/CTO Academy/Project Management/Estimation and Forecasting.md
+1 -3
View File
@@ -89,9 +89,7 @@ dependency acceleration, or increased risk.
## How It Fits Into the Bigger Picture
This lesson builds on [[Projects vs Operations]], [[Outcomes and
Definition of Done]], [[Scope and Scope Creep]], and
[[Milestones vs Tasks]]. It prepares the project system to become
This lesson builds on [[Projects vs Operations]], [[Outcomes and Definition of Done]], [[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
more predictable and scalable.
## Related Concepts
10 Knowledge/CTO Academy/Project Management/Meetings and Follow-up.md
+6 -8
View File
@@ -1,5 +1,3 @@
# Meetings and Follow-up
Duration: 30--40 minutes
## Definition
@@ -49,8 +47,8 @@ and use synchronous time for two blockers and one scope decision.
## How It Fits Into the Bigger Picture
Status reporting communicates project state. Meetings resolve what
cannot efficiently be resolved asynchronously. \[\[Ownership and
Delegation\]\] determines who follows through afterward.
cannot efficiently be resolved asynchronously. [[Ownership and
Delegation]] determines who follows through afterward.
## My Company / Real-World Context
@@ -98,7 +96,7 @@ most discussion is detailed implementation.
## Related Concepts
- \[\[Status Reporting\]\]
- \[\[Ownership and Delegation\]\]
- \[\[Decision Log\]\]
- \[\[Project Health\]\]
- [[Status Reporting]]
- [[Ownership and Delegation]]
- [[Decision Log]]
- [[Project Health]]
10 Knowledge/CTO Academy/Project Management/Milestones vs Tasks.md
-7
View File
@@ -657,17 +657,10 @@ And because DevOps doesn't report to the project owner, that may be exactly the
## Related Concepts
- [[Projects vs Operations]]
- [[Outcomes and Definition of Done]]
- [[Scope and Scope Creep]]
- [[Milestones vs Tasks]]
- [[Dependencies]]
- [[Capacity and WIP]]
- [[Project Health]]
- [[Portfolio Management]]
10 Knowledge/CTO Academy/Project Management/Outcomes and Definition of Done.md
+4 -13
View File
@@ -542,17 +542,8 @@ Even better is preventing this situation by defining those criteria **when the p
## Related Concepts
- [[Projects vs Operations]]
- [[Project Outcome]]
- [[Definition of Done]]
- [[Scope]]
- [[Scope Creep]]
- [[Milestone]]
- [[Outcomes and Definition of Done]]
- [[Scope and Scope Creep]]
- [[Milestones vs Tasks]]
- [[Project Health]]
- [[Stakeholder Management]]
- [[Stakeholder Managemen]]
10 Knowledge/CTO Academy/Project Management/Ownership and Delegation.md
+4 -6
View File
@@ -1,5 +1,3 @@
# Ownership and Delegation
Duration: 30--40 minutes
## Definition
@@ -128,7 +126,7 @@ immediately asks you what to do.
## Related Concepts
- \[\[Portfolio Management\]\]
- \[\[Meetings and Follow-up\]\]
- \[\[Status Reporting\]\]
- \[\[Project Health\]\]
- [[Portfolio Management]]
- [[Meetings and Follow-up]]
- [[Status Reporting]]
- [[Project Health]]
10 Knowledge/CTO Academy/Project Management/Portfolio Management.md
+7 -9
View File
@@ -1,5 +1,3 @@
# Portfolio Management
Duration: 30--40 minutes
## Definition
@@ -68,8 +66,8 @@ six, queue the others, and make the trade-off explicit.
## How It Fits Into the Bigger Picture
\[\[Prioritization\]\] decides relative importance. \[\[Capacity and
WIP\]\] determines how much can be active. \[\[Project Health\]\]
\[\[Prioritization]] decides relative importance.[[Capacity and
WIP]] determines how much can be active.[[Project Health]]
identifies where intervention is needed. Portfolio management combines
them.
@@ -129,8 +127,8 @@ team can begin.
## Related Concepts
- \[\[Prioritization\]\]
- \[\[Capacity and WIP\]\]
- \[\[Project Health\]\]
- \[\[Status Reporting\]\]
- \[\[Ownership and Delegation\]\]
- [[Prioritization]]
- [[Capacity and WIP]]
- [[Project Health]]
- [[Status Reporting]]
- [[Ownership and Delegation]]
10 Knowledge/CTO Academy/Project Management/Prioritization.md
+8 -13
View File
@@ -1,5 +1,3 @@
# Prioritization
Duration: 30--40 minutes
## Definition
@@ -81,18 +79,15 @@ items are valuable. Ask:
## How It Fits Into the Bigger Picture
This lesson builds on \[\[Projects vs Operations\]\], \[\[Outcomes and
Definition of Done\]\], \[\[Scope and Scope Creep\]\], and
\[\[Milestones vs Tasks\]\]. It prepares the project system to become
This lesson builds on [[Projects vs Operations]],[[Outcomes and Definition of Done]],[[Scope and Scope Creep]], and [[Milestones vs Tasks]]. It prepares the project system to become
more predictable and scalable.
## Related Concepts
- \[\[Milestones vs Tasks\]\]
- \[\[Dependencies\]\]
- \[\[Estimation and Forecasting\]\]
- \[[Prioritization](#prioritization)\]
- \[\[Capacity and WIP\]\]
- \[\[Risk Management\]\]
- \[\[Project Health\]\]
- \[\[Portfolio Management\]\]
- [[Milestones vs Tasks]]
- [[Dependencies]]
- [[Estimation and Forecasting]]
- [[Capacity and WIP]]
- [[Risk Management]]
- [[Project Health]]
- [[Portfolio Management]]
10 Knowledge/CTO Academy/Project Management/Project Health.md
+5 -7
View File
@@ -1,5 +1,3 @@
# Project Health
Duration: 30--40 minutes
## Definition
@@ -108,8 +106,8 @@ been missed, but a critical vendor deliverable has no confirmed date.
## Related Concepts
- \[\[Milestones vs Tasks\]\]
- \[\[Risk Management\]\]
- \[\[Dependencies\]\]
- \[\[Status Reporting\]\]
- \[\[Portfolio Management\]\]
- [[Milestones vs Tasks]]
- [[Risk Management]]
- [[Dependencies]]
- [[Status Reporting]]
- [[Portfolio Management]]
10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md
+4 -12
View File
@@ -449,16 +449,8 @@ That is considerably more useful than simply saying the team is busy.
## Related Concepts
- [[Project Outcome]]
- [[Definition of Done]]
- [[Scope]]
- [[Milestone]]
- [[Capacity]]
- [[WIP]]
- [[Outcomes and Definition of Done]]
- [[Scope and Scope Creep]]
- [[Milestones vs Tasks]]
- [[Capacity and WIP]]
- [[Portfolio Management]]
10 Knowledge/CTO Academy/Project Management/Risk Management.md
+6 -8
View File
@@ -1,5 +1,3 @@
# Risk Management
Duration: 30--40 minutes
## Definition
@@ -53,7 +51,7 @@ deserve Yellow health.
Dependencies tell you what the project needs. Estimation exposes
assumptions. Risk management asks what could make those assumptions
fail. \[\[Project Health\]\] then reflects important risks before
fail. [[Project Health]] then reflects important risks before
deadlines are actually missed.
## My Company / Real-World Context
@@ -103,8 +101,8 @@ production is approaching.
## Related Concepts
- \[\[Dependencies\]\]
- \[\[Project Health\]\]
- \[\[Estimation and Forecasting\]\]
- \[\[Capacity and WIP\]\]
- \[\[RAID\]\]
- [[Dependencies]]
- [[Project Health]]
- [[Estimation and Forecasting]]
- [[Capacity and WIP]]
- [[RAID]]
10 Knowledge/CTO Academy/Project Management/Status Reporting.md
+5 -7
View File
@@ -1,5 +1,3 @@
# Status Reporting
Duration: 30--40 minutes
## Definition
@@ -61,7 +59,7 @@ Better:
## How It Fits Into the Bigger Picture
\[\[Project Health\]\] tells you whether attention is required. Status
[[Project Health]] tells you whether attention is required. Status
reporting explains why, what changed, and what action is needed.
## My Company / Real-World Context
@@ -115,7 +113,7 @@ blocker.
## Related Concepts
- \[\[Project Health\]\]
- \[\[Milestones vs Tasks\]\]
- \[\[Risk Management\]\]
- \[\[Portfolio Management\]\]
- [[Project Health]]
- [[Milestones vs Tasks]]
- [[Risk Management]]
- [[Portfolio Management]]
Untitled.canvas
+1
View File
@@ -0,0 +1 @@
{}