Comments on: Writing use cases for agile (Scrum) projects

By: Agile | Pearltrees

Agile | Pearltrees — Fri, 16 Mar 2012 22:06:19 +0000

[...] Writing use cases for agile (Scrum) projects [...]

By: Use cases vs User stories in Agile/Scrum development

Use cases vs User stories in Agile/Scrum development — Tue, 17 Jan 2012 23:03:44 +0000

[...] a use cases to flesh out user stories in Agile projects is certainly not unheard of (see here, and here). But it becomes clear as we move through the workshop is that user stories are just the [...]

By: Per Ola Sæther

Per Ola Sæther — Wed, 29 Jun 2011 14:08:34 +0000

Hi Scott,

There is nothing wrong with writing detailed use cases. All information that are added and that devs find useful when implementing the use case is a good thing. I think that the answer on the question “what is the correct level of details” will differ from projects to projects.

By: Scott

Scott — Wed, 22 Jun 2011 17:00:39 +0000

We use SCRUM and write pretty detailed use cases. For example, we would specify the data elements to be included in the step “Webshop Displays the Details.” We sometimes go as far as specifying a display format, for a date for example. We sometimes worry about line between requirements specification and design, but it always seems to work for us.

By: Per Ola Sæther

Per Ola Sæther — Wed, 22 Jun 2011 10:49:47 +0000

Hi Chris,
In this case we choose to write the use case description pretty much as a user story. We left out the part “so that..” because it didn’t add any value to the description. I you think that “so that” adds value to your description you should include it. You can also take a look at a post I wrote about User Stories, there I am using “so that…” http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/

By: Chris Velevitch

Chris Velevitch — Wed, 22 Jun 2011 01:12:18 +0000

I see you descriptions are similar to user stories. In your example descriptions, you’ve left out the ‘so that…’ part. Is there a reason for this? I would have thought the ‘so that’ part of the user story would have helped in writing the flows.

By: Per Ola Sæther

Per Ola Sæther — Mon, 09 May 2011 11:44:07 +0000

Thank you for the many Thank Yous. I’m glad you found the article helpful

By: Athar Bilal

Athar Bilal — Fri, 06 May 2011 15:42:38 +0000

THANK YOU.THANK YOU.THANK YOU.THANK YOU.THANK YOU.THANK YOU.THANK YOU.THANK YOU. you have no idea how much help this article has given me. i wish i could give you a $1000 but unfortunately i dont have that much .. thanks alot and will be back here for some more info

By: Working with requirements and use cases

Working with requirements and use cases — Fri, 02 Jul 2010 12:29:48 +0000

[...] Next step is to make sure that the developers and architects know what functionality you are about to develop and how this can be technically implemented. It is time to start writing Use Cases. When writing use cases you extract use cases from the functional description you wrote earlier. It is OK to start of with writing large use cases and make sure that all major functionality are covered with use cases. Now it is an good idea to start splitting your use cases into smaller and more specific use cases. While doing this it is also smart to identify common/general functionality and place this in other use cases. You can now refer to this use case from other use cases when you need to describe this kind of functionality. You can read more about how to write use cases in a previous post I wrote on this subject: Writing use cases for agile (Scrum) projects. [...]

By: Per Ola Sæther

Per Ola Sæther — Thu, 18 Mar 2010 12:40:14 +0000

Hi Ricardo,
I have never used the essential use case technique, but of course (curious as I am) I read some articles about essential use cases thanx to your comment

My way of writing use case are quite similar in some sections. I think that the most important when writing use cases is to write them in a manner suitable for your project.
Often when I am starting a new project and are about to write use cases I collect best practices from earlier projects and adjusts my template based on that.