Details
New Feature
Resolved
Major
Description
From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected.
Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference.
My thoughts on what would be useful in my own situation:
- A way to indicate the Author(s) of a scenario
- A way to indicate the Owner of a story
- A way to indicate the Creation Date of a scenario
- A way to indicate the Last Update Date of a scenario
- The injection phase of the scenario (eg. grooming, planning, development...)
I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta
followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text.
This would allow interesting things...
Meta:
@Author John
@Role Product Owner
@Created 2009-11-08
@Injection Backlog Grooming
OR
Meta:
@Author Fred
@Role Quality Engineer
@Created 2009-12-02
@Injection Sprint Planning
OR
Meta:
@Author Colin
@Role Developer
@Created 2009-12-10
@Injection Development
Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint.
Allowing meta-data would enable scenario management tool development.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 3.0 [ 16302 ] |
Mauro Talevi
made changes -
| Fix Version/s | 3.1 [ 16511 ] | |
| Fix Version/s | 3.0 [ 16302 ] |
Very interesting request. Don't you prefer to keep this data in your agile planning tool (like Mingle, Xplanner, etc.)?
Szczepan Faber
added a comment - Very interesting request. Don't you prefer to keep this data in your agile planning tool (like Mingle, Xplanner, etc.)? Mauro Talevi
made changes -
| Assignee | Mauro Talevi [ maurotalevi ] | |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Summary | Allow per-scenario meta-information | Allow per-story and per-scenario meta-information |
| Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Mauro Talevi
made changes -
| Description |
From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected.
Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference. My thoughts on what would be useful in my own situation: - A way to indicate the Author(s) of a scenario - A way to indicate the Owner of a story - A way to indicate the Creation Date of a scenario - A way to indicate the Last Update Date of a scenario - The injection phase of the scenario (eg. grooming, planning, development...) I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta:) followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text. This would allow interesting things... Meta: @Author John Meta: @Role Product Owner Meta: @Created 2009-11-08 Meta: @Injection Backlog Grooming -OR- Meta: @Author Fred Meta: @Role Quality Engineer Meta: @Created 2009-12-02 Meta: @Injection Sprint Planning -OR- Meta: @Author Colin Meta: @Role Developer Meta: @Created 2009-12-10 Meta: @Injection Development Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint. Allowing meta-data would enable scenario management tool development. |
From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected.
Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference. My thoughts on what would be useful in my own situation: - A way to indicate the Author(s) of a scenario - A way to indicate the Owner of a story - A way to indicate the Creation Date of a scenario - A way to indicate the Last Update Date of a scenario - The injection phase of the scenario (eg. grooming, planning, development...) I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta:) followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text. This would allow interesting things... Meta: @Author John @Role Product Owner @Created 2009-11-08 @Injection Backlog Grooming -OR- Meta: @Author Fred @Role Quality Engineer @Created 2009-12-02 @Injection Sprint Planning -OR- Meta: @Author Colin @Role Developer @Created 2009-12-10 @Injection Development Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint. Allowing meta-data would enable scenario management tool development. |
Mauro Talevi
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
At the moment, you could put meta-info in the scenario title, which is free-text.
But specific meta info is an interesting suggestion, which we should consider.