Over the last 4 months or so, I've been building up the documentation at
http://housebot.sourceforge.net/index.php/Agile_Development
I've tried to keep it at a fairly high quality level by polling for
feedback from friends and family and hunting down tools for graphical
documentation. I think they're at a good enough of a level to solicit
feedback from a larger audience. I've been told by another computer go
developer that
http://housebot.sourceforge.net/index.php/Agile_Development/Block_2 was
of particular interest.
Just to seed feedback:
* Can the information for each block be organized in a better way? What
should I do differently in block 3?
* Which diagrams are most effective? Least effective?
* What additional information should be included?
* Is the design sound? Any fatal flaws? Over-engineered?
_______________________________________________
computer-go mailing list
[email protected]
http://www.computer-go.org/mailman/listinfo/computer-go/
