When would it make sense to craft acceptance criteria, and where would you incorporate it, e.g., the first ~2 weeks of a six-week build cycle during task discovery or at the finished pitch stage and embed it into a breadboard that is ready for the next build cycle?
In Scrumban, for example, product managers, with their cross-functional team, add acceptance criteria (to support, for example, BDD ) to their prioritized stories (validated high-value opportunities) and only when a trigger point (minimum WIP limit on your To-Do (or, To-Try status) on the team’s kanban board is approaching. (I realize some teams split stories (functionally decompose user stories) in such a way that achieve similar results.).
How would specification by example (requirements by collaboration/collaborative analysis, which, traditionally, like in Scrumban, is working well when delivery teams spend no more than 5–10% of their iteration on backlog refinement) work in Shape Up when there is no backlog or indication of acceptance criteria?