Your Team Calendar Should Be Part of the Work
Most teams have some way of tracking time off.
A Confluence page. A SharePoint document. A spreadsheet. Maybe a shared calendar.
And technically, it works. The information is there.
The problem is that it’s disconnected from where planning and delivery actually happen.
A vacation entered three weeks ago may affect the next Sprint. Someone being away may require a handoff. A dependency may need to be resolved before they leave.
But when availability lives in one place and the work lives somewhere else, the Team has to connect those dots manually.
That’s where surprises happen.
We Decided to Fix That
Project Simple now includes an integrated Team Calendar.
Team members can add vacation, planned time off, holidays, or other periods when they won’t be available. That information becomes part of the Team’s operating model instead of something maintained separately from the work.
And we don’t just store it.
Project Simple reminds the Team when someone is going to be away.
That gives everyone time to finish handoffs, transfer knowledge, take over anything that needs attention, and deal with dependencies before someone leaves.
No last-minute discovery that a key person won’t be available.
No scrambling to figure out who needs to take something over.
The Team gets the information when it’s relevant, giving everyone time to prepare and helping maintain the delivery rhythm.
And the Sprint Knows Too
But we didn’t stop there. Time off schedule is important in for Teams following Scrum and we made planned time off automatically reflected in the Sprint.
If someone is going to be out for three days during the next Sprint, their availability is reduced and the Team’s Sprint capacity is updated automatically.
No copying availability into another system, or figuring out available dev time with a calculator. No manually adjusting capacity because someone happens to remember an upcoming vacation.
The information is already there, so Project Simple uses it.
Availability is Part of Planning
Time off isn’t separate from delivery. It directly affects capacity, dependencies, handoffs, and ultimately when the work gets done.
So why manage it in a document disconnected from all of those things?
Record it once. Let the Team know when it matters. And, automatically account for it when planning the work.
Give everyone enough warning to make the handoffs before someone leaves.
Time off shouldn’t create a delivery surprise.
It should simply be part of the plan.
That’s Simple.