My 2 cents:
A lot depends on the size and nature of the work. if your project is big enough it needs multiple PMs then there's a lot of time needed for coordination and cross communication.
I do find that asking if a task is 50% done is kind of random and that task should be broken down into something that's more concrete and binary(is it done or not). so it's ok to report 8 of 10 tasks are complete but asking an individual 80% of X is complete is probably not helpful.
daily standups help because it uncovers blockers and helps people admit when their stuck. and can help with redistributing the work.
as for documentation, I feel if you can't commit to documenting what it is you want then it's probably not a priority.
document discovery is a big problem in a large project/org.
you wouldn't write a book without an editor so it's probably good to have a qa person be another set of eyes on what needs to be done.
having a BA/product owner on the business side helps the business own the product and takes alot of the prioritization off of the development side. Having a BA that's done the job using the software helps.
