Want a powerful trick for better acceptance criteria? πŸ€”

by Apr 24, 2023

Want a powerful trick for better acceptance criteria? πŸ€”

I often see Backlog Items without acceptance criteria, while the team is asking for them in every retrospective meeting. πŸ˜₯

Often the problem is not unwillingness but not knowing how to write them. πŸ“

πŸ’‘Tip: Write them as scenarios in Given-When-Then style! πŸ“‹

Think about how you would validate what is being delivered. How do you expect it to work? Write these expectations in a Given-When-Then style.

❓What is the Given-When-Then style
1️⃣ Given {context before the action (preconditions and initial state) πŸ”}
2️⃣ When {some action is carried out πŸš€}
3️⃣ Then {expected changes (outcomes) 🎯}

βœ… Example scenario: Borrow Book
1️⃣ Given Book that has not been checked out
And User who is registered on the system
2️⃣ When User checks out a book
3️⃣ Then Book is marked as checked out

Try this tip next time you’re writing acceptance criteria πŸš€

Do you have tips for writing better acceptance criteria?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mixβ€”a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality βš–οΈ

The Trade-off Between Budgets and Quality βš–οΈ In my previous post, I talked about shifting from Estimates to Budgets for feature development πŸ’‘. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more