You do realize there are development methodologies this is incompatible prior and post creation of Agile, right?
What that means for a technical writer is that if you UXtards are still fucking with six UX designs in 12 colors, I'd much rather let the screenshots get out of date for a couple of weeks while you fuck around with the UX, than to spend every fucking day taking 100 screenshots that will be obsolete by tomorrow's standup.
I only ever had one project doing that (constant UI redesigns) and that was while the product was still going through significant R&D work before it would ever reach real world users. Nobody was expecting user documentation to be produced for that stage.
You give me a shippable product, I give you docs.
Funny you should complain about Agile then, considering the ethos behind it is to deliver something frequently. Personally, as someone whom has done documentation, I found Agile easier to work with, small changes to documentation for each cycle, rather than blatant complete rewriting of documentation that has to be rushed for each release due to significant changes which often don't quite match the documentation that was written against original requirements since the original requirements were insufficient / badly architected / didn't take certain things into account.