I am the lone technical writer at JTV. I am presently supporting just over 100 IT engineers, product owners, and project managers. In early 2007, our management decided to move from the waterfall approach for development to an agile/scrum method.

"The Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping other do it. Through this work we have come to value:
Individuals and interactions - over - processes and tools
Working software - over - comprehensive documentation
Customer collaboration - over - contract negotiation
Responding to change - over - following a plan
Thit is, while there is value in the items on the right, we value the items on the left more."

I did not write this and I'm not sure who is responsible. Note the comprehensive documentation statement. Some engineers in the organization have taken that statement as a go ahead not to document anything. "Our software is so easy to use and intuitive that we do not need any instructions."

I have had to start a PR campaign throughout all the scrum groups. "Use the tech writer" posters are on each cubicle section and are tailored to the scrum teams logo.

More later on Scrum, scrum teams, and how a tech writer became a scrum master.