Open jmaestas7 opened 8 hours ago
As discussed, the story appears to specify an implementation (data structure) rather than an objective (output needed). The acceptance criteria are then written from the perspective of the story's user.
The choice of how the objective is accomplished is best left up to the implementer. (Our TDD model will account for automated testing of the implementation.)
Consider what the stakeholder (developer) is trying to achieve rather than a specific way to achieve it. For example, producing output of a collection of things in a particular order does not require that those things be stored in that order. This is particularly true when different presentation orderings may be desired or the cost of rearranging items is high.
User Story
Story
As a Developer
I want to create a data structure to store decisions by priority
so that decisions by priority can be stored in a way where higher-priority decisions are at the top.
Acceptance Criteria
Rules
Supporting Information
[Relevant information, context, resources, references]
Dependencies
Dependents
60