Comments on: Writing user stories for agile (Scrum) projects – revisited http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/ Technology, mobility and software development Thu, 17 May 2012 03:13:05 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Writing user stories for agile (Scrum) projects – revisited | Agile Software Development http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/comment-page-1/#comment-51198 Writing user stories for agile (Scrum) projects – revisited | Agile Software Development Tue, 21 Feb 2012 20:27:41 +0000 http://breathingtech.com/?p=1220#comment-51198 [...] Writing user stories for agile (Scrum) projects – revisited via breathingtech.com [...] [...] Writing user stories for agile (Scrum) projects – revisited via breathingtech.com [...]

]]> By: Per Ola Sæther http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/comment-page-1/#comment-12725 Per Ola Sæther Mon, 01 Nov 2010 20:29:52 +0000 http://breathingtech.com/?p=1220#comment-12725 Hi Rad, I will try to answer your questions. 1. I think that the easiest will be to not use the chapter numbering and just use the user story ID. I see that the chapter numbering can be confusing and I guess that the best would be to only use the story name as heading. 2. I'm not very familiar to BDD so I do not think I can help you there. This post was just about user stories. It is possible to expand the template so that each user story will have one or several acceptance criteria. It is also possible to write Epics that consists of several user stories. But I guess the BDD guys have some best practices on how to do this? Hi Rad, I will try to answer your questions.

1. I think that the easiest will be to not use the chapter numbering and just use the user story ID. I see that the chapter numbering can be confusing and I guess that the best would be to only use the story name as heading.

2. I’m not very familiar to BDD so I do not think I can help you there. This post was just about user stories. It is possible to expand the template so that each user story will have one or several acceptance criteria. It is also possible to write Epics that consists of several user stories. But I guess the BDD guys have some best practices on how to do this?

]]> By: Rad http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/comment-page-1/#comment-12715 Rad Mon, 01 Nov 2010 18:24:30 +0000 http://breathingtech.com/?p=1220#comment-12715 I have two questions: 1. How would you incorporate sub stories like the once in May's post: 1.1 Most popular blue-ray discs sold, 1.1.1 Sort by price, 1.1.2 Sort by popularity. I know these user stories are not quite connected with once shown here, but you can probably extend it to make a case). What confuses me if I add a sub story after I have written user stories per actor then adding a new sub story as 1.1.1 will mess up my existing user stores heading. 2. I am learning BDD with Specflow (Cucumber) and I want to use your template as the source for my feature, scenario1, ...scenarioN acceptance testing. Can you elaborate on this how I would transition from your template to BDD feature specifications. In BDD they break down the requirements to Business Goal>Actor-Goal>Epics>User Stories>Acceptance Criteria and then write Code as can be seen in "bridging the gap between requirements and code" pdf from a bdd talk handout: http://www.devcamp.at/CMSPages/getFile.aspx?nodeguid=13f4952c-fe15-449e-a510-34fb7fe89035&disposition=attachment If you see pages: 25, 43-54 (you will know what I mean) Thanks Rad I have two questions:
1. How would you incorporate sub stories like the once in May’s post:
1.1 Most popular blue-ray discs sold, 1.1.1 Sort by price, 1.1.2 Sort by popularity. I know these user stories are not quite connected with once shown here, but you can probably extend it to make a case). What confuses me if I add a sub story after I have written user stories per actor then adding a new sub story as 1.1.1 will mess up my existing user stores heading.

2. I am learning BDD with Specflow (Cucumber) and I want to use your template as the source for my feature, scenario1, …scenarioN acceptance testing. Can you elaborate on this how I would transition from your template to BDD feature specifications.
In BDD they break down the requirements to Business Goal>Actor-Goal>Epics>User Stories>Acceptance Criteria and then write Code as can be seen in “bridging the gap between requirements and code” pdf from a bdd talk handout:
http://www.devcamp.at/CMSPages/getFile.aspx?nodeguid=13f4952c-fe15-449e-a510-34fb7fe89035&disposition=attachment
If you see pages: 25, 43-54 (you will know what I mean)

Thanks
Rad

]]> By: User stories versus use cases http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/comment-page-1/#comment-8265 User stories versus use cases Wed, 25 Aug 2010 20:23:44 +0000 http://breathingtech.com/?p=1220#comment-8265 [...] You can read more about user stories in a previous post: Writing user stories for agile (Scrum) projects and the follow up post Writing user stories for agile (Scrum) projects – revisited [...] [...] You can read more about user stories in a previous post: Writing user stories for agile (Scrum) projects and the follow up post Writing user stories for agile (Scrum) projects – revisited [...]

]]> By: Writing user stories for agile (Scrum) projects http://breathingtech.com/2009/writing-user-stories-for-agile-scrum-projects-revisited/comment-page-1/#comment-3275 Writing user stories for agile (Scrum) projects Sun, 24 Jan 2010 19:07:19 +0000 http://breathingtech.com/?p=1220#comment-3275 [...] Update: I have revisted this subject and written a follow up post: Writing user stories for agile (Scrum) projects – revisited [...] [...] Update: I have revisted this subject and written a follow up post: Writing user stories for agile (Scrum) projects – revisited [...]

]]>