[Process / Documentation] When is a BRD useful, and when does it become unnecessary overhead?

Instruction: For this four-team project, recommend the documentation set, ownership and approval approach. Explain when a separate BRD would add value.

Context:

Four teams already share a current backlog, versioned business rules and linked test evidence. The sponsor requests an additional 80-page BRD. Internal governance requires a signed scope summary, but does not prescribe its length. Decide what to create or reference and how to keep the approved record consistent.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would confirm the signed scope summary requirement and ask what decision the proposed 80-page BRD would support. The existing backlog, versioned rules and test links already provide much of the detailed record. Copying all of them into a second document could create conflicting versions without adding clarity.

I would propose a concise scope summary containing the objective, users and process boundary, included...

Upgrade to view official answer

Related Questions