This base gives you an inside look at how Expedia’s Flights UX team is using Airtable to organize and automate tracking of projects, tasks, sprints, and workload capacity. All information is redacted and fictionalized for the purposes of this template.
To customize this base to your needs, please view the full base description 👉
All projects originate as backlog items in the Projects table. They are inputted by UX team members directly, or by external stakeholders via the Project Submission form. Each project is assigned a unique identifier and tagged with all appropriate team members, workstreams, epics, sprints, etc.
After a job story and acceptance criteria have been defined, projects are prioritized and pointed as a team using our custom 6-tier pointing system. Projects should be completable within the sprint period (in our case, 2 weeks). Any time required for post-UX teamwork (i.e. dev or A/B testing) is not included in that estimate but should be tracked via the Project Status field.
Projects move from Backlog to In Progress, and tagged with the appropriate sprint from the Sprints table, in our bi-weekly grooming sessions. We estimate workload capacity using the Capacity Planning table/dashboards, along with average completion stats in the Sprints table. Our team runs on 2-week sprints, but this base can be configured to fit any sprint cadence.
Once a project moves to In Progress, team members use the Tasks table to track the micro-items required to complete a project. It is recommended that tasks be assigned to one team member. Each task is tagged with a unique identifier, project, priority, estimated start/end dates, and task dependencies. Team members can create private views within the Tasks table to use as their personal to-do list and reference the Tasks Blocks dashboard to view timelines and charts.
Thank you for checking out our base. Come work with us: expedia.com/jobs.