I always follow this. I write comments for all the methods which I write unless it is plain save/update cases. And I advise the team to follow the same. But I make it as a habit to read their comments when I am free. If I find it plain stupid or not relevant, I asked them to change it or make it more meaningful or readable. To make sure I am doing the right thing, I ask a random developer to come and read the comment and explain to me what is the actual intent of the method.
It may sound tedious, but believe this is much needed. I used to work in maintenance project, and working with the undocumented code was horrible. That is the reason, I emphasize more on comments and I make sure my team follows it. I don't call this as a guideline, but it pretty much does what I wanted to!
This is a very good approach because it works out in small to medium to even big projects. Code review is something we take up religiously and this will give some relief for future me or us!