Writing requirements requires the ability to write clearly, concisely, and succinctly so others can design, develop, and test the product. This session covers 8 characteristics of writing a good requirement, reviews 4 steps to requirements gathering, and concludes with 17 tips for writing good requirements.
Come and learn how to craft a good requirement regardless of waterfall or agile approach. Yes, agile is a bit different, yet requires the same clarity, conciseness, and succinctness.
Continue reading “Writing (Non-Agile) Business Requirements”
The information age is also the age of the short attention span. We typically write for people who must spend much of each day reading. Many readers would prefer a pill that puts the information in their brain. We can’t give them that—but we can strive to give them the prose equivalent of a pill, rather than the prose equivalent of a meatloaf.
This talk outlines the basics of minimalist writing. Technical writers will find most of the concepts familiar—active voice, short sentences, etc. Minimalist writing stresses these concepts even more than general technical writing. Understanding and practicing minimalist writing benefits any kind of communication, including marketing.
Continue reading “Minimalist Writing for Maximum Communication”
Having problems with inconsistently written documentation? Do your user manuals need some help themselves? If so, then you need a style guide for your technical writing team. We’re not talking about what they should wear, but how they should write.
Content couturier Keith Schengili-Roberts (IXIASOFT) talks about what they are, why you need them and how to use them effectively. While not exclusively focusing on DITA, Keith will also talk about why a style guide is a necessity for any team working with DITA.
Continue reading “Style Guides: Fashionable But Also Practical”