I am trying to build out an automated(ish) roadmap and resource planning base that will schedule features based on sprint start/end dates and resource availability.
- I used this base as a starting point: https://airtable.com/universe/expcKQVYLmFG3RF1l/resource-planning
- Linkk to a testing base with my setup: https://airtable.com/shrRQBkuBOdeFIIFJ/tblYzc5ekhJZLVcL5
This google sheet is the auto-scheduling functionality that I am trying to mimic. The sheet takes in to account available headcount and automatically schedules dates based on availability. I’d like to accomplish something similar in airtable , but using the sprint table start and end date data to drive roadmap dates and assign features to the team based on availability. https://docs.google.com/spreadsheets/d/1r-lJg2TAsQdrhrTFR0U-pEuwgXbmZ6dK0XgDMYCLAgM/edit?usp=sharing T
The problem that I have are as follows.
- Automatically scheduling features based on resource availability. For example, if I’ve planned for Feature A thru E below, and need to plan for the next 5, how could I make Airtable do some based on availability.
- Showing overlap in availability if an engineer is double booked. If an engineer is overbooked such as Person 2 below, how can I highlight that or better yet, auto-schedule these features based on sprint start and end dates to avoid the overbooking?
The base consists of three parts:
Roadmap - contains features and the allocation record that ties the feature to the engineer(s) working on the feature. Start and end dates of the features are driven based on the associated sprints.
Team - All available engineers and associated feature and sprints they are assigned to based on the Roadmap and Allocation table.
Allocation - Breaks down the engineer’s feature distribution by row with start and end data for each feature.