The problem with "processes".. is they were probably built around the anti-pattern of design by committee... I remember one group back in NEC, require code review meetings to be scheduled at least a day before the review and require at least 5 roles for the meeting... there are practical reasons for it, but I believe as the group grew, they forgot the practical logic behind those contraints and just followed the rules to the letter :D
----- Original Message ---- From: Carl Mañoso <[email protected]> To: Kagay-Anon Linux Users' Group (KLUG) Mailing List <[email protected]> Sent: Wednesday, September 16, 2009 12:19:23 AM Subject: Re: [klug] request for estimate for snake program in C Don't know how long the freshmen can do it, but probably much much shorter than what it would take me. :) But I think 15 hours should be reasonable. Slightly more interesting is how long would it take a CMMi level 5 organization to deliver the same program? -- Carl _________________________________________________ Kagay-Anon Linux Users' Group (KLUG) Mailing List [email protected] (http://lists.linux.org.ph/mailman/listinfo/klug) Searchable Archives: http://archives.free.net.ph _________________________________________________ Kagay-Anon Linux Users' Group (KLUG) Mailing List [email protected] (http://lists.linux.org.ph/mailman/listinfo/klug) Searchable Archives: http://archives.free.net.ph
