Using SCRUM in technical documentation

By nature, technical communication projects are rarely predictable and requirements frequently change while work is in progress. Allowing flexibility while upholding thorough project planning can become a tricky balancing act. Find out how a technical communication team tackled the issue by introducing Scrum.

Text by Martin E. Brüggemann

Inhaltsübersicht

Using SCRUM in technical documentation

Image: © nyul/ 123rf.com

Why we moved to Scrum

The main task of our team is to provide high-quality, accurate documentation across nine languages for our internal and external customers in a timely manner. With regard to content for end users, this ranges from Online Help, technical reference documentation to installation and setup guides in different output formats – from MS Office documents to PDF and even XML.

The size and complexity of the documents vary from one to 100 pages, and so does the associated effort from less than one hour to three weeks.

Traditionally our documentation was done using a best-effort approach: team members worked in parallel on different tasks as fast as they could. With only basic tracking capabilities it was not possible to extract information on resource utilization, or to reliably estimate delivery dates. However, as our organization grew more mature, it became increasingly ...