A labscrum refresh

The original labscrum document https://sel.home.blog/wp-content/uploads/2022/03/b4c3c-labscrumguide.pdf. Overall I think these meetings have worked better than expected due mainly to your engagement with them. Below is a refresh of what each meeting should be.

Sprint planning (first Monday)

Tell us your goals for this sprint. This is not a todo list. Rather it is the high level things you must/want to finish by the end of the sprint. I think we could improve the presentation of this a bit by ensuring we don’t talk in shorthand. Rather than “Finish the RNA-seq analysis”, we would explain the context a small bit and state clearly what finish means and what we need to do to do that. Equally this is to get feedback on your plan, other lab members have an active role here to think about the presenter’s plans.

Sprint standups (second Monday, Wednesdays and first Friday)

What I did since the last meeting
What I plan to do till the next meeting
Are there any blocks

Sprint review (last Friday)

This isn’t an exhaustive list of what you did in the last two weeks (we know this from the sprint standups). Rather at the beginning of the sprint you planned to complete a certain number of things. Of those, tell us something you learned. So you planned:

Finish the differential expression analysis
Establish a new stock of Nasonia
Attend the two day workshop on ageing.

Would become a presentation on what you found in your differential analysis and a report on interesting things you learned at the conference. If what you planned has no such endpoint (lots of things like new stocks), its fine to say, nothing to report. This would only become a concern if it happen multiple times in a row (that would suggest no progress).

Sprint retrospective (last Friday)

If the sprint review is reporting on the “product” produced in the sprint, the retrospective looks at the process. Three questions we should consider