Loading
Because the plan is built before the people are checked. Phases get dates, the dates look reasonable, and staffing is assumed to work out — usually by the person who wrote the plan and is not the one who has to deliver it.
The collision appears in week two, when two projects need the same specialist and neither knew about the other.
Phases carry the roles and hours they need. Availability comes from assignments and approved leave in Nest, so the shortfall is arithmetic rather than an opinion.
Booking a person against a phase reserves their hours, and any other plan relying on them shows the effect immediately.
It will not choose who does the work. Skills, development and client relationships all matter and none of them is in the numbers.
It also cannot staff work that has no estimate.
Dates get promised against people who exist and are free. A plan that cannot be staffed says so while it is still a draft.
Hiring and subcontracting conversations start from a number — these hours, of this skill, in these weeks — rather than from a general sense of being busy.
Yes, until the person is decided, and capacity counts it.
Both show the conflict; the priority call is yours.
Yes, at the ramp you configure in Nest.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.