Hi all, I'm just in the process of researching Agile, especially as it relates to my profession (technical documentation). Can you recommend any books that address specifically the role and processes of the technical writer in an Agile environment? Thanks!

I have two openings for technical communications interns this summer. I'm really excited about the chance to bring fresh ideas into my group.

I'm looking for summer internship candidates who are passionate about technology, possess strong written communication skills, and have a knack for simplifying complex programming and server administration concepts for customers. Interested students can contact me at juliemac@microsoft.com with questions or to s… Continue

Before my development teams moved to Agile, I had a difficult time getting my books completed in time for an editorial review. The compressed schedules near the end of the release also made it difficult to provide beta documentation with the confidence that the documentation included features that Product Management wanted to showcase for the customer.

Since our move to Agile, the iterative reviews by QA have increased the technical accuracy of the documentation. Our editor's willingne

… Continue

You know, where you keep doing the same old thing over and over again, expecting to see different results…

Some projects seem to have it all: a clear vision of where they’re going, a clear roadmap to get there, clear requirements, clear objectives. Others never seem to quite get it together: the market changes, priorities change regularly, customers want something other than what you are creating, and oh yes, they want it now! Do either of these sound familiar? I hope for your sake you have som… Continue

The biggest reason was to try to gain visibility into what seemed like a very large workload. Our product was v1, and hadn't released yet. Churn was the word of the day. Features moved in and out of the product so fast it seemed like our doc plans were obsolete before we even reviewed them. Writers were holed up in their offices, not talking to each other.

We were pioneers of a sort; although we were working on a product that encouraged the use of a process in software development, and shipped… Continue