[Imc-alternatives] "user stories" as alternatives site requirements specification

[Josh Marcus]

Hey folks!

(Hello!  I am a programmer from Philadelphia.)

In response to one of Jay's emails, I decided to take an initial crack
at beginning to translate some of the wishlists into requirements
documentation or at least the beginning of a development process.
Given the state & process of the project, my suggestion is that an
"agile development" approach might work better than a huge requirement
specification.  In that light, I posted up two wiki pages.

#1 --

http://www.openplans.org/projects/imc-alternatives/user-stories

These are "user stories", one to three sentence descriptions of
desired functionality without any techno-speak or technical details.
I derived them from posts to the imc-alternatives list.  Many of them
could use some work and clarification but it's a start!

#2 --

http://www.openplans.org/projects/imc-alternatives/agile-development

A quick sketch of how agile development works and how it might apply
to this project, if folks are into it.

Neither might be useful but I thought I'd throw those two documents
into the mix.

--j