Behavioral Driven Design and Development, part 3

User Stories aren't necessary. They can still exist, but honestly, they're just a wrapper around a set of related action items (aka tasks).

What's more, since each code path (aka vertical slice) has a Reach and Impact score and the development team is weighing in with Confidence and Ease of build, we have a full RICE score, so the system can automatically sequence our backlog for optimal delivery of business value.

We know what to build, in which order to build it, how much it will cost and when it's likely to be delivered.

All by simply sketching out a solution as a diagram.

But wait, there's more...

Unlike relying on a single Product Owner to know everything it takes to build a user story, B3D relies on each member of the "village" to bring their specific expertise to the table to build a much better diagram.

This process happens slowly as stakeholders weigh in, asking questions and refining the approach and corresponding expected behaviors. The drawing engine captures who is requesting what behaviors so test results can be traced back to customers, both internal and external. And all the while, the development team is specifying what it will take, box by box, arrow by arrow, to build the solution.

The system knows who is building what, how much they cost, how loaded with work they are and when they're likely to get to the work and complete it. No guesswork.