[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226733#action_226733 ]
Szczepan Faber commented on JBEHAVE-220: ---------------------------------------- Very interesting request. Don't you prefer to keep this data in your agile planning tool (like Mingle, Xplanner, etc.)? > Allow per-scenario meta-information > ----------------------------------- > > Key: JBEHAVE-220 > URL: http://jira.codehaus.org/browse/JBEHAVE-220 > Project: JBehave > Issue Type: Improvement > Components: Core > Reporter: Chris Jensen > Priority: Minor > Fix For: 3.1 > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email