Create a story in Agile Development 2.0 There are several ways to create a story in Agile Development 2.0. Before you beginRole required: scrum_story_creator, scrum_admin About this taskStories can be associated to a product or a project, but this is not mandatory. Procedure Create a story in one of these ways: OptionAction From the stories list Navigate to Agile Development > All Stories. Click New in the record list. From a product, release, sprint, theme, or epic form Select the Stories related list and click New. From the release, or group backlog list Navigate to Release Backlog, or Group Backlog. Click New in the record list. From an enhancement record Navigate to Agile Development > Enhancements. Open the required enhancement. Right-click the header and select Create story. The product owner reviews enhancement requests and decides which ones require stories. From a defect record Navigate to Agile Development > Defects. Open the defect record. Right-click the header and select Create story. Fill in the fields, as appropriate. Note: Some of the fields on the story form may already be filled up depending on from where the story is created. Table 1. Story form fields Field Description Number A system generated number for the story. Theme Theme associated with the story. A theme can have one or more stories, but a story can belong to only one theme at a time.Select the theme for this story from a list of themes associated with the selected Product. Epic Epic associated with the story. An epic can have one or more stories, but a story can belong to only one epic at a time.Select an epic for this story from the epics associated with the selected Product. Type The type of story: Development Documentation Spike, for example, research activity Classification The type of development the story involves. The default is Feature. This field has no connection to the Defect and Enhancement fields in the Related Records tab. State Current state of the story. The default for a new story is Draft. Points The number of points indicating the estimated effort required to complete the story. A larger point value indicates that a greater amount of effort is required. Priority The priority assigned to the story. A product owner can use priorities to rank stories in the planning board. Product The product with which this story is associated. This field is required if the story is part of product. Release The release with which this story is associated. The release can be from the releases associated with the selected Product. Assignment group The group to which the story belongs. Sprint The sprint with which this story is associated. This field becomes active when an Assignment group is selected. Assigned to The user who is working on the story. Users on this list have appropriate scrum roles. Demand The demand with which this story is associated. When the demand is converted to project, the demand stories move from demand to project. Project The project with which this story is associated. This field is required if the story is executed as part of a project. Project phase The name of the agile project phase with which this story is associated. This field becomes active when a Project is selected. If a project has only one phase, then the story automatically gets tagged to the only phase.Note: An agile phase can have stories belonging to more than one group. Blocked An indicator that shows that there are issues that are preventing the story from making progress. Clear the check box if there are no blocking issues. Short description A brief description of the story. Description A more detailed description of the story. Acceptance criteria The functional criteria or testing results required to move this story to a state of Complete. Work notes Notes about the work being performed for this story. Related lists Defect The defect associated with the story. This is a reference field from the Defect [rm_defect] table. This field is required if the story is created for a defect.Click the magnifier icon in this field to display the defects created and to open a new defect. Only users with the feature_user role can open a defect. The admin must grant the feature_user role to all users who are expected to open defects in the Agile Development application. This is the only location in the Agile Development application where records from this table appear. Enhancement The enhancement associated with the story. This is a reference field from the Enhancement [rm_enhancement] table. This field is required if the story is created for an enhancement.Click the magnifier icon in this field to display the enhancement requests created and to open a new enhancement. Only users with the feature_user role can open an enhancement. The admin must grant the feature_user role to all users who are expected to open enhancement requests in the Agile Development application. This is the only location in the Agile Development application where records from this table appear. Click Submit. Result The story is created and the form reopens with related lists. The story is listed in the respective backlog list depending on the fields filled in the story form. What to do nextCreate the necessary scrum tasks for this story, or specify one or more stories where the current story is dependent using these related lists and links. Table 2. Story form related list Field Description Related lists Scrum Tasks Lists the scrum tasks created for the story. Click New to create a scrum task. Prerequisite Stories Lists the stories that must be completed before the current story can be completed. Click Edit to add a prerequisite stories. Dependent Stories Lists the stories that depend on the current story. Click Edit to add a dependent story. Related links Add Scrum Tasks Allows to add multiple tasks tasks to the current story from the Add Scrum Tasks dialog box. Fill in the fields and then click OK. The tasks are added to the Scrum Tasks related list.