Welcome to TechWhirl Forums

Sign in or Register to get involved in our discussions.

Documenting Customer Delays

I write software user guides and training documentation for a large company.  They are only just getting into the Agile methodology and while they seem to grasp the development part, they still want the documentation to be finalised before the application is.

I have encountered many "customer induced" delays, mostly the application not being available due to upgrades or major bugs making documentation a nightmare.

They also don't understand the impact of some seemingly insignificant changes to the tech writer e.g. changing the Application name and logo after over 100 screenshots have already been taken with the old one.

Has anybody out there got a nice way of documenting work and delays so that they have evidence to provide to the customer when they say "why isn't it finished".
Sign In or Register to comment.