"Self-promotion is never a replacement for quality work." Could not agree more. It's crucial to focus on delivering excellent results. Keeping a brag doc to track your accomplishments is also a great way to keep track of your contributions and share them when needed.
Okay, thanks for sharing, it's very useful and makes sense.
One question, I'm curious, if I understood correctly, do you write this "launch" write-up at the end of a feature or project you worked on, or do you write it for all tasks at the end of the sprint that you closed?
I create this writeup when I have results to share. This means I write something for most features or projects since I focus on work that has impact/results.
I wouldn't create a writeup of my tasks unless there was some outcome or milestone progress worth sharing about.
Okay, so it's only for something you think is meaningful to share, that has enough value and impact, and that managers should know about... Thanks! :))
"Self-promotion is never a replacement for quality work." Could not agree more. It's crucial to focus on delivering excellent results. Keeping a brag doc to track your accomplishments is also a great way to keep track of your contributions and share them when needed.
Okay, thanks for sharing, it's very useful and makes sense.
One question, I'm curious, if I understood correctly, do you write this "launch" write-up at the end of a feature or project you worked on, or do you write it for all tasks at the end of the sprint that you closed?
I create this writeup when I have results to share. This means I write something for most features or projects since I focus on work that has impact/results.
I wouldn't create a writeup of my tasks unless there was some outcome or milestone progress worth sharing about.
Okay, so it's only for something you think is meaningful to share, that has enough value and impact, and that managers should know about... Thanks! :))