Do you inform others when deleting or making fundamental content changes?
Last updated by Tiago Araújo [SSW] 9 months ago.See historyWhen it comes to making significant alterations or deletions to someone else's content, it's a good practice to inform them and document it, by sending an "as per our conversation email" as a safety step.
Clear communication helps maintain transparency and respect for the original author's work.
This is especially important in collaborative environments, where changes can impact the overall project or its documentation. Keeping others informed allows for discussions or adjustments if needed.
Understanding the history of content is essential for context, accuracy, and informed decision-making.
Being diligent about content deletion not only respects contributions but also mitigates risks and fosters a culture of understanding and problem-solving.
| To: | Dave |
| Cc: | John, Danny |
| Subject: | FAQ - Removed irrelevant section |
Hi Dave,
As per our conversation, I have removed the section below from the FAQs since it is redundant, as you no longer join Daily Scrums.
I have CC'd others who have edited this page.
From
FAQ
Q: What if your team already does Daily Scrums?
A: Prior to the Daily Scrum, ping Dave and say "Starting our Daily Scrum in a minute". Do your Daily Scrum as normal and add in Dave/Product Owner. After the call, one person (called the Scribe) should send an email to the whole team. :
Q: What if I only have one day until I go on client work?
...
To
FAQ
Q: What if I only have one day until I go on client work?
...
Figure: Good example - Being considerate and documenting content deletion
