The M-CaReM-AI Method: Defining Work for AI / Unit 3 MCM 066 worked example, 60 to 90 seconds
Stories, Specifications and Cards Together
The idea
The method keeps the requirement formats a team already uses and anchors them to things and cards.
In practice
Step one, user stories: keep writing them for the user's point of view, and point each story's acceptance criteria at the card that governs the behavior, instead of redefining it. Step two, traditional specifications: group functional requirements by thing, so each core thing gets a section built from its Pack and cards. Step three, behavior-driven scenarios: keep writing them, and take the meaning of every key term from the thing's Pack. Step four, test plans: tag tests by thing and card, so that when a thing changes, the right tests are found.
Where people slip
Nothing here asks a team to stop working the way it works. It asks every artifact to say which thing it is about.
Your place on the trail
Every lesson rests on earlier ones and opens later ones. Tap any to jump.
Builds on
Something wrong in this lesson? Flag it · Sources for The M-CaReM-AI Method: Defining Work for AI