Originally posted by Scott Ambler:
I think that people with tech writing experience should be included on the team because it's an important skill which every IT person should have. But, that doesn't mean that this person will only do tech writing. They should be prepared to roll up their sleeves and be actively involved in modeling, testing, programming, ... just like any other team member.
Also, you'll find that user documentation is typically written one iteration behind the functionality -- you want to wait until a feature has stabilized before you write about it.
Originally posted by Stan James:
Ilja, do you find the story to user doc granularity or fit is off some times? We may get a story that affects several use cases and user doc scenarios, or a whole series of stories that affect the same doc iteration after iteration. It can be kind of rough on the doc maintenance folks.