Every day: A senior developer (for now Geo) will aim to spend 90 minutes with the junior developers. The aim of these sessions is to:
- upskill the team
- set priorities
- solve the subtasks which the junior developers can’t solve themselves
Preparation
For these sessions to be effective, projects need to be assigned to developers, generally this will be done at a User Story Level. See here for MW: Sprint Planning
The developer will look at the sub tasks below their User Story and identify which ones they can do themselves and which ones they need support on. This categorisations needs to happen before the meeting.
Meeting Structure
- Senior Dev selects a project to do overview.
- Junior Devs list the following
- which User Story they have been assigned.
- the list of subtasks with the categorisation of do themselves or need support on.
- Repeat for all projects and junior developers
- Senior Developer Defines Game plan for the next 90 minutes
- Analyse all the tasks which need your support and not.
- Choose which project you will focus on first.
- Break off with relevant developers to this project and support for tasks. Tell other developers when they can expect a call to support them.
- Repeat process with other projects.
- Senior Developer aim is to have the developers be able to do a full work day without being blocked.