December 22, 2005

Communicating a delivery schedule with use cases

Posted in Communication, Requirements, RM Software, Use case at 12:12 am by Scott Sehlhorst

We’ve moved to – this post is now here


1 Comment »

  1. Good observation regarding features versus use cases. As you mention, users don’t care so much about features per se; they care about accomplishing their goals. Scheduling around use cases helps product developers keep their eyes on the ball (focus on what matters to the prospective customer).

    In many cases, use cases often aren’t sufficiently granular (nor should they be) for scheduling. Craig Larman recommends dividing use cases into versions in such cases. I touch on this approach here:

    An example is a Purchase Items use case. You can break it into versions as follows:

    Purchase Items (cash only, no receipt)
    Purchase Items (cash, receipt)
    Purchase Items (cash and check, receipt)
    Purchase Items (cash, check, credit, receipt)

    That way you’re delivering end-to-end value to the user after every version.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: