Imagined headings: (borrowing heavily from Kelsey ❤️ )
Who and what is this about?
Landscape (formerly known as Problem)
Stakeholders//collaborators
Why we should take this on?
We are uniquely suited to solve this problem because...
Why it matters?
What already exists in this space? (what does it fail to address?)
How we’re going to do it
We address this problematic _with_...
We define these use cases
We see these requirements as design priorities
(Features -- prioritize use case)
"functional"
"NFRs" (look, usability, humanity, (values), ease of use, learning, environmental/operational, maintainability, support, sustainability, security, cultural)
We will intervene (?) through...
How do we assess our involvement with this project?
This is a success if...
We see these potential concerns & blockers...
Timeline and Work Plan <--- made tentative deadlines already!
Lets take inspiration from @Frijol's wonderful product requirementing over in https://github.com/edgi-govdata-archiving and draft a pretty nice statement of concerns and project requirements: https://hackmd.io/s/rk4qe2E27#
Imagined headings: (borrowing heavily from Kelsey ❤️ )