Founders are answering questions live on Product Hunt (https://www.producthunt.com/posts/me3)Making genuine new friends as an adult is HARD. Not only are there fewer opportunities to meet new people, but we become busier and pickier as we grow older. So we built Me3(https://www.me3app.co/): a free mobile app that connects you with shockingly similar people in your area through group chats of...
The closest thing I found on some guidelines is this: https://jacobian.org/writing/great-documentation/.Tools like Asana seem to take a high level approach: https://asana.com/guide. Tools like Dropbox seem to take a more granular approach: https://www.dropbox.com/help/topics/sharing_files_and_folders
Sure it helps managers do their jobs, but I think that in some cases we might not even need a manager at all.
The value I see for developers is to get some objective metrics on a feeling they have. If they think something is inefficient, they should be able to be able experiment with their process. But that needs to be done a bit more objectively.
I think developers could also use this as proof that that the problem is not always with the team but sometimes it may come from management.
The scope creep is a good example of this. A manager keeps adding stuff to the current iteration and the dev team gets swamped. A widget could clearly show the impact of that scope variation.
I see value for the dev team, end-users and management if it's done right.