1. Our company is not so big that anyone could get away with not pulling their weight (as they would stand out like a sore thumb), - having said that everyone here shares our culture of making the effort to get the job done so weve not had a problem with that kind of issue. Have to admit that pair programming is one of those things that tends to get 'forgotten' in the rsh to meet deadlines, Im sure other folk doing XP can identify with this ;-)
2. For those products that are out there already we still use XP, basically releasing dot point upgrades every few iterations to fix those few bugs that slipped through and to add new functionality incrementally. Our iterations tend to be about 2 weeks give or take (rather depends on what features and fixes are planned for the iteration), so that would mean a new (minor) version every month or so. Of course on the rare occasions a critical bug arises it would get priority. Basically its just a case of applying common sense. -----Original Message----- From: Kenneth Stout [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 18, 2002 01:35 To: Struts Users Mailing List Subject: Re: XP (and not the Microsoft kind) I have two questions for those using XP. 1) How is a programmers performance evaluated within the XP pair programming model? When dealing with humans you will occasionally end up someone that is simply not measuring up.(everyone on this list excluded of course ;-). The HR department will want some kind of documentation prior to terminating someones employement. 2) It appears that XP is applied to new development efforts (at least that is all I hear about). How is ongoing software maintanence addressed? Are bugs that can not wait for the next version addressed in the traditional model? Kenneth. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
