- Team = group of people who build the project
- PL = Project Leader, team members that also plans, coordinates and motivates the team
- Client = person who defines the goals, constraints, deadlines of the project
- PMT = Project Management Tool, e.g. Trello
- PL lists 3<8 functional packages
- PL estimates the development duration of each package
- (Team can be solicited for the steps above)
- PL identifies the supply chain and its actors (e.g. sketching -> design -> dev -> QA)
- PL lists the tasks (1<7 days of development per task) of each package
- PL (with help of Team) defines each task precisely:
- what is this task supposed to do
- what's needed to finish this task (assets, wording, design, algorithms, decisions...)
- priority (relative to other tasks)
- PL creates a (editable) planning for these tasks, for each Team member, respecting the constraints of the supply chain
- PL sends an email to the team:
- Cheering the team: achievements, issues, effort...
- What was supposed to be done last week (1 line per team member)
- What must be done this week (1 line per team member)
- (optional) Word of advice
- Cheering again!
- Every meeting has an agenda, to be shared with Team before the actual meeting:
- decisions to be made
- topics to be discussed
- every item of the agenda has a time limit (e.g. 4 minutes max)
- After a meeting, highlights must be shared with the team, e.g.
- Tasks must be entered in the PMT, associated with Team members, due dates and other info...
- Decisions must be written down so that they can easily be found later (for reference)
- Decisions to be made should be asked to the relevant parties, and followed by PL
- Discussions that could not fit the time constraints can be submitted to PMT or by email, for asynchronous follow up
- During a meeting, prevent attendants from using electronic devices. Prefer paper and eye contact.
- A Watcher is elected in order to enforce the following rules:
- No use of any electronic device during the meeting;
- No discussions that are not relevant to ALL meeting participants;
- And the maximum duration of each timeslot must be respected.
- The Secretary keeps note of:
- Tasks,
- other topics to be discussed
- Intro, 5 minutes to recap:
- Last week's achievements (outstanding tasks, stats and user feedback)
- Main objective(s) and upcoming deadlines
- Each team member has 2 minutes to recap:
- tasks achieved last week (incl. pain points)
- tasks to be done this week (incl. risky points)
- misc... (new bugs, feedback, proposal to discuss an idea or other specific topic)
- Outro: the Secretary recaps his notes out loud, and shares them with the team (e.g. using Google Docs + Slack)