From the course: Agile at Work: Planning with Agile User Stories

Unlock the full course today

Join today to access over 24,500 courses taught by industry experts.

Write technical stories

Write technical stories

- These are both stories. This is a user story and the other one is a technical story. From a distance, they look pretty similar. In many ways, they are similar. They both have a concise statement on the front and acceptance criteria on the back. There are two primary types of stories. The first is the user story, capturing functional requirements from a user's perspective. The other is the technical story, an approach to capture non-functional requirements. Technical stories are also known as "enabler stories", "spikes" or "architectural spikes". and "non-functional stories." They add value by identifying the work required to provide either current or future functionality and quality attributes of our system or product. Technical stories can be for exploration, security, infrastructure, privacy, performance, research, compliance, et cetera. Let's look at a few examples. "As a security chief, I want the purchasing system behind the firewall, and all access must be made using the…

Contents