vault backup: 2026-07-23 10:32:18
This commit is contained in:
@@ -242,6 +242,21 @@ You shouldn't necessarily measure both types of work the same way.
|
|||||||
|
|
||||||
## My Company / Real-World Context
|
## 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.
|
Your Monday board gives us several good examples.
|
||||||
|
|
||||||
### Umami
|
### Umami
|
||||||
|
|||||||
Reference in New Issue
Block a user