The whiteboard template [1] has a section called "scope", which is a pretty
ambiguous term.
The way I see it, the scope defines the qualities our final design should
have.
For example, the scope on the whiteboard template states that the final
whiteboard template design should be "Easy to browse through," feature
"Terse phrases", and have a "Space for multiple proposals", and shouldn't
feature sections for tracking development (as a design whiteboard is for
fleshing out design ideas).
The scope is tricky because, if you're not careful, you can easily
introduce unwanted constraints. For example, I could have easily put
"Section for Scope" under the scope of the whiteboard, but that would rule
out all the proposals with an alternative to scope, such as those that
incorporate the scope into the summary, or such as those with "Goals" and
"Non-goals", or "Musts", "Wishes", and "Restrictions", etc. If I knew that
the whiteboard template should definitely have some place for the qualities
that the final design should have, I should have put something like
"Required qualities of the final design" under the Scope section.

If you can't think of qualities for the scope, leave it blank -- it's for
the better. If you can't think of what to put in the "Out of Scope"
section, you might want to put in something that seems blatantly obvious to
you, like "Be able to ban community participation" on a whiteboard template
whiteboard.

So my final definition for scope is this: "A list of qualities the final
design should have. The scope should be broad enough to restrict proposals
as little as possible."

[1]
https://wiki.documentfoundation.org/Design/Whiteboards/Whiteboard_Template

-- 
Unsubscribe instructions: E-mail to [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to