Don’t Lean on Development’s Agile Process

Don’t just try to fit into development’s agile process. Create your own lean content development process.

Technical writers are increasingly finding themselves involved in the agile process of the development organization.  The most common way this happens is that a writer gets assigned to the team for a sprint and is expected to produce documentation in the same sprint as the developers produce the feature.

This has one huge plus for writers: development cannot declare the sprint complete until the documentation is done. This means that it is in the interest of every developer to help ensure that the tech writer has what they need to get their work done. Given that getting information when needed is a major issue for many tech writers, this can be a very big win. read more

We Can’t Use “In Tray” Definitions for Content Roles

Everyone in the content industry seems to be trying to define their roles these days. There are a number of new roles and titles being described, and everyone wants to know where to draw the boundaries around them.

Commenting on my recent post on Content Engineering, Jonatan Lundin asked, “So is an information architect a sort of content engineer?” On LinkedIn, Bob Newman protests “I am the Technical Writer – NOT the SME!”. And in the first meeting of the nascent Content Strategy Collective, defining content strategy and content strategy roles was the first thing proposed as a goal for the group. read more