From the course: Agile at Work: Planning with Agile User Stories
Unlock the full course today
Join today to access over 24,100 courses taught by industry experts.
Acceptance criteria
From the course: Agile at Work: Planning with Agile User Stories
Acceptance criteria
- Let's take a look at a story. As a customer, I want to search for a product so that I can purchase it. How does that sound to you? Do you get a decent picture of what's being asked for? I think so. However, if I were to implement this requirement, I would need more. Ah, here are some of the details and a little bit of helpful context. This is what we call acceptance criteria. I see a note, this is for a text-based search. Next, I see some scenarios, such as customer initiates a text-based search for a product, given no preconditions. When? Customer types words into the search input area and customer initiates the search. Then, customer is presented with products matching the words. Ah, and here's another one. Scenario, customer initiates a text-based search for a product. Same thing, no preconditions. When? Customer types words into the search input area and customer initiates the search, same as the other one. However, then if no products match the words, the customer is notified…
Contents
-
-
-
-
-
(Locked)
Ready to implement1m 56s
-
(Locked)
Identified state1m 15s
-
(Locked)
Sized state1m 5s
-
(Locked)
Relative sizing techniques3m 34s
-
(Locked)
Team estimation5m 37s
-
(Locked)
Size with points vs. estimate with hours2m 13s
-
(Locked)
Understand velocity3m 10s
-
(Locked)
Prioritized state52s
-
(Locked)
Input to backlog prioritization and planning3m 25s
-
(Locked)
Ready to implement state1m
-
(Locked)
Acceptance criteria4m 38s
-
(Locked)
Story quality and the definition of ready4m 39s
-
(Locked)
-
-