FDD and JIRA: Working with Features

In this post I will talk how to work with features. The following points are explained:

• Create a Feature
• Add a Bug or a Change to a Feature

Create a Feature
This is done like with any other JIRA-issue.

Just choose the Type Feature. A Feature is a defined Issue Type. They are (will be) explained in posts about administration.

The following fields are to set:

• Feature ID: this is a unique identifier like a number, to reference the feature in other sources like reporting, model etc.
• Summary: the sentence that describes the feature, in the pattern: {action} the {result} {by|for|of|to} a(n) {object}
• Business Activity: choose the Business Activity where to add the feature
  
• Description: a detailed description of the feature
• Open Issues: if there are assumptions or open questions this is the place. whenever the issue is solved remove them here. So this field should indicate in an overview if there are open points.
• Orginal Estimate: Estimation of the feature - this can also be edited at a later time.
• Concerns: a Feature is about some business logic (domain), but it needs sometimes a GUI, a client, persistence or some integration.

These fields can be edited on the way. Add a Bug or a Change to a Feature As a feature is the entry-point for any further work we have the possibility to add sub-task to a feature. We have defined at the moment:

• FeatureConcern: a feature describes mainly the business logic in a technology independent way. To describe the user interaction (GUI) or the integration with other technologies (INT) you can define a FeatureAddon. These can than be used in reporting to indicate if the feature has a GUI or needs integration.
• FeatureScenario: it is possible to describe different scenarios. This allows for example the direct export into a testing tool.
• FeatureBug: if a Bug is detected that is related to that feature you want to add a FeatureBug.
• FeatureChange: whenever the customer is not happy with the result, or they change their mind a FeatureChange can record that.

At the moment we haven't different screens for sub-tasks, we will adjust that when needed.