Paul Penrod wrote:
If this is purely a conceptual exercise, then someone from HQ needs to
lead the discussion, starting with a set of business requirements, and
fleshing
things out from there - AND not letting the discussion tail off into the
weeds.
Many of the people on this list are programmers first, designers second,
if at all.
They can give you elegant and clever solutions, but those solutions have no
meaning without a framework to hang them on.
Otherwise you will get the "wounded duck, spiraling into the pond" exercise
from what was a good starting point.
As one who has been shooting at the duck <grin>, this is an excellent point!
Would it make sense for this group to write up some use-cases/scenarios
or simple stories as a means of driving out the requirements?
That way, people could define the feature or issue that is of a concern
to them in a use-case or story.
ex: write-up a use-case for a parent who choses to opt-out, or a story
of a data-voyeur trying to access someone else's information (whatever
that may be), or of a district leader trying to validate the merit
badges for an Eagle Scout candidate.
All those who want to contribute could write up the stories, the actual
folks who want to code the solution decide which ones they care about
and want to do first and you have the beginnings of a set of functional
requirements. Non-functional requirements can be driven out the same
way, but most programmers don't want to think of those :-)
--
A. Rick Anderson
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
