From b0fbd99b92f7612e3bbc2d1dfe3543577f24bc5a Mon Sep 17 00:00:00 2001 From: modji Date: Thu, 23 Jul 2026 10:32:18 +0200 Subject: [PATCH] vault backup: 2026-07-23 10:32:18 --- .../Project Management/Projects vs Operations.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md b/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md index d1bfda8..1e4ecc0 100644 --- a/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md +++ b/10 Knowledge/CTO Academy/Project Management/Projects vs Operations.md @@ -242,6 +242,21 @@ You shouldn't necessarily measure both types of work the same way. ## My Company / Real-World Context +### My organizational context + +My team's capacity is shared between several types of work: + +- Departmental projects +- Product initiatives and continuous product work +- Operational responsibilities and incidents +- Tickets and requests +- Work dependent on IT teams such as DevOps and Security + +This means that project delays cannot be understood only by looking at project timelines. Project work competes with operational and product work for the same finite team capacity. + +---- + + Your Monday board gives us several good examples. ### Umami