# Retrospective Log ###### tags: `Meetings` ## January 12 * Roman * Small company, people are not aware that is happening in the other parts of the org * There have been cases when information has been missed * Do not know what to do when blocked * Not enough releases * Standups are not fulfilling their purpose * Richard * There was friction with putting together a feature * There was misalignment behind the feature * No understanding of the design * Designs were not properly captured * A lot of back and forth because the requirements and design we not clear * Meetings are at the right time * Ben * CI infrastructure in not mature * Meetings are at the right time * Harald * Meeting time is good because it is in the afternoon Go over the issues Have a clear agenda Issue tracker was used a way to create an agenda ## Decision Summary * We will start to triage again * We will use the project board * We will add the column for priorities - Epics * We will run sprints 2 weeks * We will have a release every 2 weeks * We work on features the first week and bugfix the second. * We will have feature freeze - * Create release branches - for every bump of minor or major (not patch) version * We will decompose the epics - have a planning meeting for a sprint * Every first standup of a sprint we do planning * Monday Demo * Tuesday release party * Wednesday planning next sprint * Thursday design meeting of the release week is retro * We will update the board columns to make it more useful to meet the flow * If you do not like the reviewers change them * Add a column for the reviews