:zap: As a role I can capability, so that receive benefit.
Monitor metrics, Blackbox exporter
Add link to bookmarks repo
Acceptance Criteria (executable specification)
:zap: Write the Acceptance Criteria ... The Scenarios names are pointing in the right direction, but are nowhere near ready for implementation.
Feature: todo ...
As a _role_ I can _capability_, so that _receive benefit_.
Background:
Given todo ...
Scenario: todo ...
Given todo ...
When todo ...
Then todo ...
Acceptance Criteria (additional / manual)
:zap: Memo (remove when story is ready)
[ ] :zap: Translate the user story into executable specifications
:zap: If you cannot think about phrasing these tests, check if you really understand the problem
:zap: Use ubiquitous language based on the language of the problem domain
:zap: When a dedicated file from the code repository is used to define the acceptance criteria, do not repeat here. Just link to the proper definitions
Post-Implementation Tasks (Examples)
[ ] :zap: Measure related metric after implementation for period of time.
[ ] :zap: Track the reduction in related metric related to the feature for period of time.
:zap: As a role I can capability, so that receive benefit.
Monitor metrics, Blackbox exporter
Add link to bookmarks repo
Acceptance Criteria (executable specification)
:zap: Write the Acceptance Criteria ... The Scenarios names are pointing in the right direction, but are nowhere near ready for implementation.
Acceptance Criteria (additional / manual)
:zap: Memo (remove when story is ready)
Post-Implementation Tasks (Examples)