LEARN. PRACTICE. GROW.Convert percentages into executable commitments
An allocation percentage is a planning assumption, not a guarantee of untouched hours. In the exercise, ten hours are reserved for project work during the week. An incident uses three of those hours and resumption requires one more, explicitly excluded from the three. Six hours remain. Record losses once and distinguish time consumed in support from effort actually applied to the project. If several initiatives share the reservation, compare combined demand with common capacity before confirming any commitment.
Check continuity and skill
Four one-hour slots cannot support a rehearsal requiring three consecutive hours. The arithmetic sum can be correct while the plan remains infeasible. Likewise, six Linux-engineering hours do not automatically replace two missing DBA hours when the task requires that skill. For each package, record effort, duration, required role, dependencies, and calendar constraints. Seek a qualified alternative, a different sequence, or a deadline decision. Do not turn generic availability into specialist capacity or invent overtime outside your authority.
Level the shared resource
Two packages may have no logical dependency while still competing for one person. If A occupies the only DBA for two days and B for three, minimum combined duration is five days under the stated conditions. Using only the longest branch, three days, assumes simultaneous resources that do not exist. At work, also check unavailability, operational tasks, and approvals. When two projects reserve six and five hours from a shared eight-hour allocation, demand is eleven. Bring that difference to the owners with options and consequences.
Contribute technically during an incident
In a hybrid role, you may be asked to diagnose WebSphere while managing the project that delivered the application. Confirm your task and the structure coordinating the incident. A project-manager title does not automatically transfer response command. Share observations, coordinate changes, and keep state accessible to participants. If work spans shifts, handoff should include explicit role acceptance and notification to the other participants. A sent document is useful, but it does not establish that someone assumed the next operational responsibility.
Protect focus with defined coverage
Recurring interruptions warrant an organizational response alongside individual effort. One possible experiment defines qualified triage and protected design blocks with clear escalation. Measure service response time and work completion to check whether the arrangement improves the overall situation. Do not copy another organization’s rota as a universal obligation. Separately record incidents, planned operational activities, and project work over a useful period. History helps review allocation but does not guarantee identical future distribution. Operational demand may vary and require a new decision.
Guided practice: reconstruct the week
Use the figures below to prepare a short update. After the incident and resumption, the specialist has six hours against seven hours of combined demand. Both tasks can be split, but that does not create the missing hour. Identify options such as deferring an authorized portion or obtaining additional qualified capacity, and confirm priority with the owners. In the message, separate restored service, cause still under investigation, and rehearsal awaiting rescheduling. Summarize demonstrated capacity, constraint, expected impact, requested decision, and the useful deadline for making it.
Synthetic capacity exercise / Exercício fictício de capacidade
reserved = 10 hours
incident_inside_reservation = 3 hours
additional_resumption = 1 hour
remaining = 10 - 3 - 1 = 6 hours
project_A = 4 hours; project_B = 3 hours
gap = 4 + 3 - 6 = 1 hour
exclusive_DBA_packages = 2 days + 3 days = 5 days
A restored service does not restore a missed calendar slot.10 reserved hours minus 3 incident and 1 resumption leave 6; two projects request 4+3=7, one hour above capacity.
Common pitfalls
Adding incompatible hours, double-counting a reservation, assuming overtime, or confusing incident command with project responsibility.
Related topics: Capacity and dependencies · Governance and suppliers · Handover to RUN
A project commitment requires usable hours, qualified people, and confirmed execution conditions, even after service recovers.
Reference: Dealing with Interrupts · PM² reference practices and cloud operational governance; primary guidance reviewed 2026-09-30