Describe the current problem
Explain what happens today, who is involved and where work gets delayed or duplicated. Include a representative example without confidential or personal information.
Separate the essentials from the later ideas
List the work the application must support at launch. Keep optional enhancements visible, but separate them from the acceptance criteria for the first release.
Make integration and access part of the brief
Name the systems involved, the information that must move between them and the roles that need access. Identify the people who can confirm these requirements.
Agree what a successful handover looks like
Define the business scenarios to validate, the training needed and the support responsibilities after release. A clear brief covers operation as well as development.
