APPNEURAL - PROJECT BRIEF
Editable planning worksheet
Source: https://appneural.com/resources/templates

Use this worksheet to describe a requirement before comparing proposals.
Replace the bracketed fields, identify unknowns and agree who can approve scope.

1. PROJECT AND OWNERSHIP
Project name: [fill in]
Brief owner and role: [fill in]
Decision maker: [fill in]
Version and review date: [fill in]
Target start and delivery dates: [fill in]

2. GOAL AND AUDIENCE
What problem should this project solve? [fill in]
Who experiences it, and in which situation? [fill in]
What happens today? [describe the current workflow]
What evidence shows the problem matters? [record observations or a baseline]
Desired outcome: [fill in]
Success measure, baseline and target: [fill in]
Who will decide whether the outcome has been achieved? [fill in]

3. CURRENT SYSTEMS AND CONSTRAINTS
Systems, applications and manual steps involved: [fill in]
Required integrations and their owners: [fill in]
Relevant data, quality and access constraints: [fill in]
Hosting, device, browser or environment requirements: [fill in]
Permissions and accessibility needs: [fill in]
Existing documentation or approved sample material: [list references]

4. SCOPE
Must deliver in this engagement: [list the required deliverables]
Could deliver if budget and time permit: [fill in]
Explicitly outside scope: [fill in]
What existing behavior must continue to work? [fill in]
Who supplies content, access, tools and approvals? [fill in]
How will new requirements be reviewed and priced? [fill in]

5. DEPENDENCIES AND DELIVERY
Dependency | Owner | Needed by | Current status
[fill in] | [fill in] | [fill in] | [fill in]

Milestone | Deliverable | Review owner | Target date
[fill in] | [fill in] | [fill in] | [fill in]

Budget range and currency: [fill in]
Third-party licensing, usage or hosting costs: [list assumptions]
Review frequency and communication route: [fill in]
Known risks and proposed response: [fill in]
Open question | Person to resolve it | Decision date
[fill in] | [fill in] | [fill in]

6. ACCEPTANCE AND HANDOVER
For each deliverable, describe an observable pass/fail check.
Deliverable | Acceptance check | Evidence required | Approver
[fill in] | [fill in] | [fill in] | [fill in]

Critical journeys to demonstrate: [fill in]
Documentation and training required: [fill in]
Operational owner after handover: [fill in]
Support or maintenance scope to agree separately: [fill in]

7. REVIEW DECISION
Decision: [ready for proposal / revise / defer]
Remaining assumptions: [fill in]
Approved scope version: [fill in]
Approver and review date: [fill in]
Next action, owner and due date: [fill in]

This worksheet is a planning aid. Adapt it to the project and agree delivery
terms separately; completing it does not create an engagement or guarantee an outcome.