Stand-ups are meetings recommended by the SCRUM methodology. In these small meetings of fifteen minutes maximum, everyone takes the floor to say quickly what they worked on the previous day, the work planned for the same day and the blocking points (if any).
The goal is to keep it short because the main drift of these meetings is to drag out the work and thus demotivate everyone. It is normally the role of the SCRUM master to manage speaking time but in order to better manage my speaking time I use my
So I start the day by defining the tasks I want to do during the day in a Markdown file like this:
Monday, September 1st - [ ] end feature A - [ ] define requirements for a feature B
Then, as the day progresses, I tick off the tasks that have been completed. If I have completed additional tasks, I add them.
Monday, September 1st - [x] end feature - [x] debug problem on staging server - [ ] define requirements for a feature Be
The next day, I do the same thing by adding the new day. All the tasks I didn’t do the day before can be found in my forecast for the day.
Monday, September 1st - [x] end feature - [x] debug problem on staging server - [ ] define requirements for a feature B Tuesday, September 2nd - [ ] define requirements for a feature B - [ ] start new feature C - [ ] take ticket QA
What is practical is that for the Daily Stand I can consult this file and thus be more concise about what I did without trying to remember the day before or the Friday before.
I find that this method has several advantages:
I don’t pretend to say that it is the miracle method but it seems useful to me.
Cet article de Alexandre Rousseau est mise à disposition selon les termes de la licence Creative Commons Attribution - Pas d’Utilisation Commerciale - Partage dans les Mêmes Conditions 4.0 International.