View Single Post
  #23  
Old 04-09-2007, 11:35 PM
frommagio frommagio is offline
Senior Member
 
Join Date: Jan 2005
Posts: 976
Default Re: Lessons from a Botched Upgrade

To Phil153, the lovable idiot non-savant who just deleted his post:

Quoting Phil's deleted response:

[ QUOTE ]
I don't know a damn thing about 2+2's backend/business but I can say most of these points are worthless.
[ QUOTE ]
Choose your technical staff wisely.

[/ QUOTE ]
As opposed to unwisely?

[/ QUOTE ]
Well, yes.

[ QUOTE ]
[ QUOTE ]
You know your business, techies know technology.

[/ QUOTE ]
From what I understand, they paid the freaking development guy to work on parts of the upgrade for them.

[/ QUOTE ]
From what you understand, did they get what they paid for?

[ QUOTE ]
[ QUOTE ]
Many techies will be able to understand your business.

[/ QUOTE ]
And?

[/ QUOTE ]
And they would know that shaving 1 day from a 3 day procedure won't cut it when the business requires a transparent procedure?

[ QUOTE ]
[ QUOTE ]
It's your job to find one.
-- Remember that your techie works for you.

[/ QUOTE ]
But I thought that technies know technology...shouldn't you tell them what you want and leave them be?

[/ QUOTE ]
Absolutely not - you manage them. The technical plan they develop must meet your business requirements, and it must pass review. You need to arrange to provide whatever is needed for the plan, and you need to monitor the testing results on an ongoing basis. That's what managers do.

[ QUOTE ]
[ QUOTE ]
Consider your reasons for upgrading.

[/ QUOTE ]
Better performance, version able to receive security updates, coincides with site design upgrade, improved features requested by many members, enables future tweaks.

[/ QUOTE ]
Very good.

[ QUOTE ]
[ QUOTE ]
-- What are you trying to accomplish? What are you risking?

[/ QUOTE ]
1. See above. 2. Nothing.

[/ QUOTE ]
Nothing? That's pretty funny, Phil, given the experience of the last three days.

[ QUOTE ]
[ QUOTE ]
What are the drawbacks to upgrading? The benefits?

[/ QUOTE ]
I'm sure this question occurred to them. I mean...

[/ QUOTE ]
I'm sure you'd be surprised at how many businesses have been crushed by far less.

[ QUOTE ]
[ QUOTE ]
What if you decided just to stand still? Any problems?

[/ QUOTE ]

[ QUOTE ]
Is this for business reasons, or for your techie?

[/ QUOTE ]
Wait, I thought technies knew their stuff, and we know business. If a technie says an upgrade is good, should we not listen?

[/ QUOTE ]
If you've taken the time to read through this thread, you now have learned enough to answer this question. I bet Ryan could set you straight on this.

[ QUOTE ]
[ QUOTE ]
Plan your upgrade.

[/ QUOTE ]
Plenty of planning went into this upgrade.

[/ QUOTE ]
I have a problem with either the word "plenty" or "planning"; I just don't know which one.

[ QUOTE ]
[ QUOTE ]
Test your upgrade first

[/ QUOTE ]
Um, putting it one the archiver server doesn't count??

[/ QUOTE ]
Um, apparently not!!

[ QUOTE ]
[ QUOTE ]
Your customers are not a testbed.
-- Use a separate staging area.

[/ QUOTE ]
That's not always easy or viable. 2+2 isn't a multi billion dollar company.

[/ QUOTE ]
LOL at multi billion.

[ QUOTE ]
[ QUOTE ]
-- Use artificial load generation to simulate real life.

[/ QUOTE ]
This is where they may have had room for improvement; hard to know without specifics.

[ QUOTE ]
Be sure that the new features are working as you hope.
-- Remember to check that the basic stuff still works.
-- Make a testbed beta available to some helpful customers.

[/ QUOTE ]
They did all this.

[/ QUOTE ]
I'm sure they tried to address what they thought of. Next time, they'll think of more.

[ QUOTE ]
[ QUOTE ]
-- Review the planned benefits, every point. All proven?
-- Review the risks, every point. Satisfied?
-- If your techie didn't do all of this, you screwed up; bad hire, learn the lesson.
- If things look good, announce your planned upgrade
-- Give plenty of warning to your customers
-- Give yourself plenty of time to back out
-- Remember that the software works for you, not vice-versa
- Finish your testing
-- Don't hurry.
-- Don't be afraid to back out; believe your own eyes.
-- Accept a schedule slip if it's too early to decide.
-- Remember that you are in charge.
- Go for it
-- After all your worries are satisfied, pull the trigger.

[/ QUOTE ]
Um, they did every one of these things too. How is copy pasting some random internet advice helpful?

[/ QUOTE ]

No copy pasting here; just the points as they occurred to me, many of which obviously were not followed. Especially the parts about managing the technological process.

Hey Phil, are you the same groundhog that missed seeing his shadow recently, and said that spring would have come by now? Nice track record, rodent boy.
Reply With Quote