Business decision records (BDRs)

Agile values “responding to change over following a plan”. A part of that premise is that business needs and imperatives change over time, and software development should respond to these changes. This is probably something you experience day in and day out. The business makes decisions all the time - about prioritisation, roadmaps, migrations, budgets, target groups, experiments, and whatnot. 

The larger the team, the more the decisions, and the harder it is to keep track of them in our heads or through conversations. Distributed teams must adopt the discipline to document all business decisions in business decision records (BDRs). Joel Henderson has an excellent guide for general decision records, which I’m sure you’ll find useful. If you use Confluence, it has a built-in template that also allows you to populate all decisions at one place in your team handbook.

Screenshot of Confluence's decision documet
Previous
Previous

Pull requests

Next
Next

Commit messages