Purpose:
Section titled “Purpose:”Description of required fields in a Story and what to store inside each field.
Scope:
Section titled “Scope:”Technology Dept
Responsibility:
Section titled “Responsibility:”Technology Dept - Halo Team - Halo Product Owner
Completion Criteria:
Section titled “Completion Criteria:”Steps 2 and 3 are completed.
Records:
Section titled “Records:”Story record in Halo
Steps:
Section titled “Steps:”- Convert a Demand in Accepted status into a Story or create a new Story if there is no related Demand.
- Ensure the following fields for a Story in Draft status is completed.
-
Requested by: the person writing the Story.
-
Requested for: process owner that will perform user acceptance testing.
-
Assignment group: assign to Halo Development.
-
Initiative: select the initiative that the Story best fits. Create a new initiative if 3 or more stories are written to achieve a clearly defined
business goal.
-
Value rating: not to be confused with Priority. How valuable is the work described in this story to the business using the following scale: Critical,
High, Medium, Low, Very Low? The value of a story to the business is described in the Benefit statement.
-
Ranking: using a modified Fibonnaci Sequence, rank how soon the development team should begin working on the story relative to others. The lowest
number has the highest priority in the Product and Development Backlogs.
-
Type: choose one of the following three types: User, Enabler, or Defect. User stories were submitted by a team member outside of the Halo Team.
Enabler stories are submitted by Halo Team members to faciliate further development by the team. Defect stories originate from a defect ticket and require resolution through the development process.
-
Expected result: description of what the development solution will do to enable the Requested for’s process.
-
Benefit statement: description of the value the development solution will provide the business.
-
Acceptance criteria: conditions that the developer’s solution must satisfy to be accepted by the process owner.
- Save the record and close.
Process References:
Section titled “Process References:”- Create a relationship back to related process. Note: Please add KB relationships to core process, process, SOPs or other WIs on the right.