# How to use Airtable ###### tags: `lab` `planning` This refer to the new base ([EngageLab sandbox](https://airtable.com/tblR5fLCioXtRDBp2/viwDPuv7esd25GdOK?blocks=hide)) ## Projects Main views are: * Active * Planned * Applications Projects are organised as a set of themes (at least one). All projects have an internal project manager. ## Themes A more general term than ‘epics’ and iterations. Can be an epic, i.e. a set of user stories that comprise an epic. Could also be a kind of development done in a project, e.g. design, testing, pilot, survey, etc. Anything that goes into a theme is an important part of customer communication and also a basis for the expectation of deliveries. A theme can contain a set of user stories or other kinds of specifications, typically as a checklist. A theme should refer to a hackMD document that details any specification, needs, requirements, etc. for that theme. Themes are the basis for both time reporting and budgets. Themes have a status: * Backlog = things we know need to be done, but is not scheduled * Placeholder = we have set aside time in the calendar to do stuff, but don’t know exactly what * Planned = We have a good idea of what needs to be done, and time is set aside for it * Active = A theme that we care about right now * Delayed = A theme that was active, but is put on hold for the moment. Themes are visualised on the Project timeline. ## Features Anything that needs to be done, such as tasks, bugs, todos, etc. Features have a priority rating and a complexity rating, and may be estimated in hours. Features belong to one developer, or several. Features have a status and are typically displayed in a kanban board for a partucular theme. Status is one of: * Uncategorised = no categorisation has been done yet * Selected = Is in a sprint, or will be put into a sprint shortly * Review = Sprint is done, test and review needed > [name=Richard Nesnass] Which status to use if the Sprint did not complete the Feature? e.g. partially done? > Perhaps unfinished 'Review' Features may be moved back to 'Selected' on Tuesdays, after discussion? * Done = This feature is tested/reviewed and found to be OK * Bug = Some issue is found, needs attention ## Sprints Typically planned on a weekly meeting (Tuesdays) Everyone selects a number of features that can be done within four days work. Any feature can be put into a sprint. > [name=Richard Nesnass] This needs to also work the other way round i.e. A number of Sprints may be needed to complete one Feature; describing the breakdown of a feature into Sprints. Some Features are too big for four days, so this is necessary. * Goal: States the goal (intention) of a sprint that will help to achieve the Feature requirement * Feature: The Feature(s) that are relevant to this sprint * Start / End: When the sprint begins and should end with the Goal completed * Who: The worker rsponsible for the Sprint ## Little things Like a sprint, but a set of features that can be done in one day (such as a bug, or minor change). Inspiration: https://www.themuse.com/advice/a-better-todo-list-the-135-rule Divided into Urgent, Should, and Nice ## Time spent Select Theme, add yourself and the number of hours spent for that theme Repeat for each theme being worked on ## Budgets These are numbers coming from Trine and state the number of hours in the budgets (such as frikjøp).