Latest posts by techwriter (see all)
- Test Your Knowledge of 4 Basic Fonts – Drag & Drop - January 27, 2017
- How NOT to Design a Web Site - January 25, 2017
- Hazards of Poorly Written Technical Documentation - December 26, 2016
(A great introduction to this relatively little-known resource for technical communicators)
Developing documentation (both end-user and internal) in an Agile software development environment can present a few challenges, but overall presents many opportunities for technical communicators.
Agile, by its nature, provides relatively short cycles for developing end-user documentation. However, Agile projects succeed or fail based on their internal documentation, so technical communicators are a required part of the process. In fact, we are involved from day one.
Overview of Agile
When I was first introduced to Agile over 10 years ago, the original “Agile Manifesto” for software development (http://agilemanifesto.org/) struck a bit of fear in my heart. The Manifesto values “Working software over comprehensive documentation.” But the seventeen signatories were not referring to end-user documentation, but internal documentation. (After I started breathing again… I learned more. Our company’s owner had purchased each team member one of the few books on Agile available at the time and made it required reading. There has been quite a bit written since.)