A daily scrum shouldn't require any type of formal documentation. If there are any actions related to a specific work item which emerge, those can be captured in the journal notes for that work item (or if using a physical work board attached to the work item as a sticky note).
For retros, if you are using a virtual information management tool such as Confluence, you could have a Wiki page per retro with the improvement ideas identified. Given that the other discussions within a retro are "by the team, for the team", I'd hesitate to have anything further documented.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Amy,
in addition to Kiron.
It is always good to use visualisation, e.g. a whiteboard when f2f or an electronic tool when you are remote. You can capture this and store it away.
Some use video recording in virtual environments, might be critical in GDPR work environments, regarding privacy. Also it may inhibit open discussion. For me it is better to document results not disputes. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The documentation each ones consider the best to stay clear about what next. Saving Changes...
Daily scrums sometimes include an element of backlog refinement. That's something you should be able to accomplish in whatever collaboration / backlog management tools you use, so it may just be worth viewing the backlog on screen during the scrum.
