Github style READMEs can be turned to personal use. A Personal README, aka Personal Manual, is a document that describes how a person likes to communicate (Slack, email, text message, …), their timezone, the hours they like to work, etc. Most include enough information that a new teammate knows a little bit about their new colleague on a personal level as well.
Having looked at 10–15 examples to write this glossary, I’ve noticed the following attributes:
- Preferred Communication channel – one person even said, “I prefer Slack but if I don’t respond in 24 hrs use email.”
- Collaboration – several people talk about how to collaborate. “If it requires more than one round of emails let’s do a zoom call.”
- How and when to book a meeting on this person’s calendar.
- Several had a “What makes me grumpy” section.
- Their thoughts around giving and receiving feedback.
- Leaders shared their management style.
- Another author shared his personal work history and how it shaped him.
Are they needed? No. Are they fun? Yes. Do they give an avenue to sharing a bit more about yourself? Yes.
Examples:
- How to Rands
- Jeremiah Lee’s Manager ReadMe
- kevinleung.com/personal-readme
- molly/manager-README
- KatieLo / My leadership readme/operating manual
- My README.md
- petro.blog/my-personal-readme/
- shawinnes.com/personal-readme/
- Working with Brendan Best: A Manual
See also:
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index