I must say I like this. In some real sense the Work In Progress
in the construction of any software is "decisions". Now since
decisions require "questions" I suggest it may be more useful
to characterize the "questions."
Cockburn has broken his model of the software manufacturing
process down into the following elements:
1) Sponsors
2) Business Analysts
3) UI Designers
4) Programmers
5) Database Designers
6) Testers
Not a bad decomposition. So what are the "questions"
each group must pose to the other in order to generate
"decisions?"
BobLQ
BTW. If this post by Jim generates a coherrent thread someone
might edit it and post it as a commnet at Cockburn's blog.
On 3/2/07, James G. Sack (jim) <[EMAIL PROTECTED]> wrote:
In _some_ sense, a rebuttal to oft-expressed ideas that software
"engineering" is not really engineering.
http://alistair.cockburn.us/index.php/What_engineering_has_in_common_with_manufacturing_and_why_it_matters
In case his name is unfamiliar, Cockburn is someone whose name has
appeared in previous posts about agile programming. He is one of the
more visible preachers in that tent.
Regards,
..jim
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
