<aside> ℹ️ A User Story Template for software engineering leaders to drive QA Shift-Left strategy.

Read more on Practical Engineering Management: practicalengineering.management/p/leading-qa-shift-left-transformation

</aside>

📝 User story

As a (persona), I want (functionality), so that (benefit)

🚀 Follow INVEST model

• 🏝 Independent: The story can be built and tested without dependencies.
• 🤝 Negotiable: The story starts discussion within the team—focus on what and why, not how.
• 💎 Valuable: Clearly defines the value it brings to the user.
• ⏱ Estimable: The team can determine how much effort/time is needed to develop it.
• ⚡ Small: It can be finished quickly (fits within a single sprint).
• 🔍 Testable: Acceptance criteria describe exactly how the story will be validated.

📃 Requirements

Use to define constraints and special cases

🪲 Edge cases

Use to cover empty states, loading states, errors, edge cases

📈 Telemetry

• Must: a success metrics (what defines success and how it'll be measured)
• Traces: Steps that ends with success metric and how to measure them

✅ Acceptance Criteria

Use Gherkin syntax:

• Given (init state of the scenario)