Re: "use-case based documentation"

Subject: Re: "use-case based documentation"
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: Mike Starr <mike -at- writestarr -dot- com>
Date: Tue, 3 Feb 2015 10:19:25 -0800

Use cases are sometimes formally defined, true. Often they're not. In
an agile environment, if you're doing it right, the use cases should
be clear from the user story and acceptance criteria.

Without a use case, a feature is useless. If nobody can come up with a
use case for something, probably it shouldn't be documented or exposed
to the customer.

On Tue, Feb 3, 2015 at 10:11 AM, Mike Starr <mike -at- writestarr -dot- com> wrote:
> Many development processes are based on use cases... the use cases are
> developed before coding is started and guide the programmers in how the
> software should enable the user to use it. The product manager must provide
> you access to the use cases in order for you to develop documentation based
> on them.
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


"use-case based documentation": From: Julie Stickler
Re: "use-case based documentation": From: Mike Starr

Previous by Author: Re: "use-case based documentation"
Next by Author: Re: "use-case based documentation"
Previous by Thread: Re: "use-case based documentation"
Next by Thread: RE: "use-case based documentation"

What this post helpful? Share it with friends and colleagues:

Sponsored Ads