Software Planning & Technical Documentation - Acceptance Criteria: How to Meet User Expectations

In software development, instructions are important. While user stories themselves are great for motivation, communication, and collaboration purposes, they are not all that’s needed to ensure that the product works as expected. That’s why we have to document acceptable system behavior. Let's talk about acceptance criteria and how they're written. 0:00 Instructions in software development 0:47 User Stories 2:25 Acceptance criteria 2:55 Rule-oriented acceptance criteria 3:30 Scenario-oriented acceptance criteria 4:40 Who creates acceptance criteria? 5:22 General recommendations More about Non-functional Requirements: https://www.altexsoft.com/blog/business/acceptance-criteria-purposes-formats-and-best-practices/ Learn more about AltexSoft: https://www.altexsoft.com Follow us on LinkedIn: https://www.linkedin.com/company/altexsoft Follow us on Facebook: https://www.facebook.com/altexsoft/ Follow us on Twitter: https://twitter.com/altexsoft Follow us on Instagram: https://www.instagram.com/altexsoftcom/ Music in video by EpidemicSound (www.epidemicsound.com) In this video we use characters from “Harry Potter” (www.warnerbros.com) #acceptancecriteria #softwaredocumentation #functionalrequirements #nonfunctionalrequirements