|
I agree. Once the project goes into QA, it is completely out of my hands. Unfourtunately, the "bean counters", I.S. dept manager, CIO etc. etc. ONLY tend to see that it has been in QA for n weeks/months, and they ALWAYS approach the programmer, NEVER the User as to why it is STILL in QA. One of the may reasons I hate to try and measure productivity of programmers. >>> <D.BALE@handleman.com> 11/09 4:56 PM >>> I'm no project management guru, mind you, but if a project's mired in QA, that *should* never have any bearing on a programmer's productivity. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 -------------------------- Original Message -------------------------- As Elmer Fudd has been known to say "Be careful, VEWY - VEWY careful" I've been through this attempt to measure a programmers productivity so many times, its ridiculous. The best method I've come across, is still nowhere near perfect. Will you be asking the programmer to create/write one program at a time, when there could be ten or more programs involved in the entire project? What happens when the user turns around and says, "yes that's what we asked for, but its not what we need". Who will be responsible for final testing? If not the programmer, will they be able to turn it around in a timely fashion? I've had a project in QA (User acceptance testing) for 4 months. The users have been too busy to work on the testing, due to higher priority projects. As the user is payroll and benefits, and the higher priority projects affects them getting me my money, I'm not complaining. However, my status report shows that I have a project that is 4 months late. The list could go on and on - but I hope you get my drift. >>> "midrange" <midrange.mail@sfmco.com> 11/09 2:28 PM >>> I have been ask by accountants to provide them with a way to measure our programmers productivity. I know what I think is productive. fast accurate turnaround on projects. does anyone one else have any comments. thank you jeff grace +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.