I have had a similar problem, where the person who would sign off on a project was telling me that she did not want to see it again until it was "fixed." In that the "problem" was the warning that flash apps give when you run them locally and you click on a link, this was a mite difficult. She did not want me to change the setting on her computer that the warning said to change. On the other hand she did not want to actually have it loaded on the server until she saw that it "worked." Worked is in quotes here because it won't write a score to a file as advertised until someone gets around to telling me the path to the Perl installation. Anyway, this particular impasse was resolved when I explained matters to the guy with the password to the webserver, and he loaded it into a test folder on the server for me. Voila, error message gone.
I guess if you are looking for us to say if you are right or wrong, I would need to know what these bugs are. Are they real bugs? Are they bugs in the sense that a user is getting a message he/she does not understand but that you are not being given the means to fix? Are they strange Windows error messages the user is getting because he/she is doing something wierd? In my opinon what you have is a project management problem, with, it sounds like, a lack of proper project management going on. You are the programmer not the project manager, sure, but in order to avoid becoming the person that these problems happen to, you may have to implement some management techniques. Agile methodolgies might avoid this in the future, yes, but for this situation... when the scope creep happened, was this documented and signed off on? What project documents were you given in the first instance? If the answer to the above questions is "not much" I'd suggest that you get the current sutuation documented --- what exactly it is that everyone wants fixed. Put the ball in their court. You can play CYA too you know, and honestly -- I have had one of these drag out over full-time work for several months. I'd be embarrassed to tell you what this made my hourly rate for the project. I became a believer. If what you are giving them is not what what they want, it is only fair that they should tell you what they do in fact want. This may take some meetings, and much as I dislike them myself, sometimes that is what you need -- a nice meeting followed by a memo of confirmation. Hope that helps Dana >Hello all, >I am soliciting opinions here. >I recently finished a few applications that are all tied in together. Once I >finished coding and testing, I released it to the manager here for testing. >The key word here is testing. I informed him that he may encounter some >bugs, but this is why I wanted him to test it. So of course he encountered >some bugs in the app. After about 4 or 5 bugs later, he got pissed and said >that he is not going to test anymore until I get all of the bugs worked out. >I tried to explain that as the programmer I am not as objective as a user, >and this is the reason for testing. He said, "Well that may be the new way >to develop, but when I as a programmer we did not release anything for >testing until we knew it was bug free". I caved in and said that I will test >it under every scenario that I can think of. >So my question is this: Who is right in this instance? Is it reasonable to >expect that a set of highly complex applications that took several months to >develop should be 100% bug free? Hell, I encounter bugs all the time on >major sites on the internet, and these are being release to millions of >folks, not like the few hundred here that will use it. > >Oh, and a little history. He says that he is getting pressure from his >managers to get these app live. When I interviewed for this contract back in >December, based on the documentation given to me (about three pages worth), >I said that this could be done within the 200 hours they budgeted. Well, >after having a couple of meeting with stakeholders, I realized that this was >going to take way longer than 200 hours, I informed my manager of this and >he was OK with it. So now we have a new assistant city general manager who >is a numbers guy and watches his budget like a hawk and apparently he is not >happy with the progress. Of course I explained all of this to him a couple >of weeks ago, but I guess since he is not a programmer he finds it hard to >understand things like scope creep and the fact that the applications were >not properly scoped out in the first place. >Not only did the initial set of meeting flesh out the inadequacy of the >original scope documentation, but I ended up meeting with the wrong person! >The guy I was supposed to meet with was on vacation and he was not made >aware of what I was doing until I had the first part of the app done and >ready for testing. So things changed drastically as a result of this, and >added a few more weeks to the development. > >My impression is that my manager is reverting to CYA mode and since I am >just a contractor, he is going to try to lay the blame on me. But then again >I may be getting paranoid here. > > >Thanks, > > > >-- >Bruce Sorge > >"I'm a mawg: half man, half dog. I'm my own best friend!" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:233479 Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
