Posts Tagged ‘insights’

My thoughts, originally posted on LinkedIn:

Documentation must be part of your process. If you’re documenting everything when you’re leaving, you’ve failed everyone. Just like workouts, make documentation routine, and you’ll do it every time. It’s OK to reject pull requests that are missing documentation. Perhaps make proof of documentation part of closing any Feature or Epic. If people complain, ask them how they react when entering a project with no, little, or poor documentation. They tend to change their tune when looking in the mirror.