My Custom Application has bugs - Management Bad-Mouthing it - GRRRR! 2

[MeGustaXL]

My Program Manager wanted a data-collection and analysis tool suitable for use by an Excel novice. I offered to produce a menu-driven spreadsheet with forms for data entry, automatic report production, etc.

I gave him a disk with a Beta version on it, saying "Here's an evaluation copy of the database - have a play and let me know if there are any snags or improvements you need making". The Splash screen and Main Menu both had diagonal text boxes across them saying "BETA VERSION - NOT FOR CONTRACTUAL USE"

He subsequently got another Excel "Guru" to remove the warnings and mandated its use during a reliability demonstration, the original intended User having left the company. Of course, there are snags, and the users bleat at me regularly; "This bit didn't work.." "That chart doesn't update when I add new data..." etc, etc, etc...

I don't mind that so much, because it's usually down to my finger-trouble. What really grips my SH*T is the way the ProgMan constantly digs at it and bad-mouths it to other (non-user) people at his level.

Short of taking the Career-Damaging course of punching both his faces, what does the panel suggest I do about it?

Or am I just being sensitive and over-protective of my (flawed) brainchild?

Chris

Varium et mutabile semper Excel

 

[dyarwood]

How did you give it to your boss? Did you put in writing the path of development?

 

[MeGustaXL]

Hi dyarwood,

I gave it to him by hand, zipped on a floppy. No written development path - D'Oh!

Chris

Varium et mutabile semper Excel

 

[MeGustaXL]

Hi dyarwood,

Gave it to him by hand, zipped on a floppy.
No paper trail of development, D'OH!

Chris

Varium et mutabile semper Excel

 

[dyarwood]

Do you still have a copy of the code you gave him? Have you stated to your boss that the version being used was not your version and so you can not accept responsible for the release version. Copy your boss's boss in on a email to this effect so he is aware of it. Was there any reason why another person finished the app?

 

[MeGustaXL]

Yes I have a copy of the original version as given. Apart from the removal of the Beta caveat, the only changes to the version in use have been done by me, at the Users' request(s). So, in effect, I still have 'ownership' of it.

As I say, I volunteered to do it, more or less as a VBA programming exercise, so I don't mind the frequent squeals of pain from the Users, as I'm still kind of responsible for it. It's just the snide remarks at meetings that I hate.

Chris

Varium et mutabile semper Excel

 

[dyarwood]

If you write test documents for the app then make sure the users perform them and both the user who tested and the line manager of the user sign and return this document to you if the test was successful. If there are errors have an error form which the user fills in and returns to you. Once all the test forms (which should try to cover everything) have been returned, signed off, then the app has been accepted by the users and possibly more importantly their managers. Therefore there will be no come back to you as if the testing was completed then all the bugs should have been worked out.

 

[MeGustaXL]

Yeah, that'd be the way to formalise it I suppose. It's just a shame that what started as a mutual back-scratching and no-cost informal solution to a potentially costly problem, has turned into a source of such snidey merriment.
Teach me to be helpful! {Deep Sigh..}

Chris

Varium et mutabile semper Excel

 

[MeGustaXL]

Sorted!

Mostly it was just me being hyper-protective and sensitive.
Spoke to the PM concerned, and he apologised for any ill-feeling and embarrassment caused by his "heartless and ill-considered remarks" (his exact words!)

He's promised to highlight my "invaluable contribution to the project" when he comes to do my annual appraisal in May - Super Result!

Thanks for listening, dyarwood, I would have stewed for months if I hadn't got it off my chest- STAR for you!

Chris

Varium et mutabile semper Excel

 

[dyarwood]

Happy to help and glad you got it sorted. Here's to a very good apraisal.

 

[willir]

In future, document things you provide. The best way is in an email where you copy a suitable manager, and copy / blind copy your self, or store the message so how. Be very specific in your email that the application is a "proof of concept" version, and this is not a working version, and does not including error checking, etc.

When providing an evaluation copy, you expose yourself to a huge risk. In the past, when I demo an evaluation copy, I will not release it until I have reviewed it somewhat. I have no problem in deomonstrating the working version because I am able to explain this or that, but it is very hard to explain things when the "boss plays" (bosses dont play do they?? ;-) ) and come across something they do not understand.

Why?
Well, usually the evaluation copy will be given to mangement who is a bit non-technical to totally non-technical. Management is more likely to take an evaluation copy as a working copy without much consideration. And, they will look at cosmetic issues with a more discriminating eye. And, they will get easily confused about this or that. And.... And....

When you have adding more meat to the application, and tested it further, and have more confidence in the application, then release it to the boss ... but still ensure that he is well aware that this still an evaluation copy.

 

[Katy44]

I have had a similar problem - there is a site with some reports on it that i have written. When the site went live initially, it was run alongside the existing system by a small group of users for testing. I tried to make it extra clear that the reports also were in a testing period, and that I had generated them based on my understanding of what they wanted, I would welcome feedback and any errors they spotted. They all nodded, said they would and went away. Months pass, no errors are reported. Then all of a sudden - you guessed it - "Why are the reports wrong?! I've just sent this to the head of .... and it's completely wrong!"
I am fuming.

N.B the reports weren't wrong in the slightest, they had just changed their minds about what they wanted them to show.

 

[MeGustaXL]

I feel your anger, Katy! My app wasn't 'wrong', per se, it just didn't work the way the users thought it should - functions they wanted but hadn't asked for, Excel doesn't have that capability, etc.
Mostly I was able to pacify them by providing the functions they wanted, but it would be nice to know from day one!

Chris

Varium et mutabile semper Excel

 

[Katy44]

Exactly!
But that was a sneaky trick taking your BETA VERSION - NOT FOR CONTRACTUAL USE off the app! But...it has made me think that in future I will put that on, I think in my case it would have backed up our argument a bit, a very good idea!

"functions they wanted but hadn't asked for, Excel doesn't have that capability"
I get this a lot too, and I also love it when they request the impossible "Why can't the report show X?"

"Because you don't ever record X anywhere and it can't be worked out from anything else"

"But I thought computers were meant to be clever!

 

[lgarner]

If you continue making changes for the users, then I'd suggest putting your BETA disclaimer back in with each release. The users should definitely be advised that the program is for evaluation, and isn't production-ready. After all, they're the ones depending upon it.

 

[Albion]

I would tell the users...

"I don't know what you're talking about, I never released a production copy of my copywritten software. Maybe you should take it up with the person who gave it to you."

-Al

 

[billbredbenner]

Things like this don't really happen in life, do they??
The world is all peachy-keen,sunshine and lollipops, isn't
it??? (ROFLMAO). After spending 24+ years in state
government service, the old addage " CYA " has never been
MORE important.

Hope those buggers get what they deserve!

Bill

(these comments were in no way meant to belittle or lessen
the importance of stated problems,just my way of saying
we've all been there at one time or another and truely
feel your pain!)