HeraTech

About This Blog

There are lots of resources out there for developers who want to learn how to be successful with Agile, Scrum, and XP: books, blogs, workshops, courses, conferences, people offering their services as consultants and coaches. But when I started researching Agile, I did not find the same level of support for the technical writers trying to integrate with Agile teams.

Agile is a process that was designed to address the pain points of developers, not of technical writers. But we don’t have a choice of whether or not to “go Agile.” If our development team adopts Agile practices, then we have to follow along or fall behind. This blog is about trying to figure out how to succeed in an Agile environment. I’m not an expert, but I like to think that my thoughts and experiences may be of value to other TWs.

We (meaning Agile Technical Writers) need to start putting more information out there to help each other learn how to make Agile work for documentation, and how to avoid the things that don’t work. Especially since Agile has been around for a decade. By now there really ought to be more resources out there for Agile TWs. I hope this blog will grow to be one of them.

Standard Disclaimer – This blog is solely the opinions and thoughts of Julie Stickler. It does not reflect the opinions of any of my employers, past, present, or future.

I used to work for a company that was bought by a certain Big Blue corporation. Since I’d love to work for them again, I’m going to try to adhere to their Social Computing Guidelines, the most important of which I think is the last “Try to add value.” My goal is to avoid whining and ranting in this blog (I have a personal blog for that) and instead to give something back to the Agile and Technical Writing communities.

Advertisements

Create a free website or blog at WordPress.com.

%d bloggers like this: