Change Control for ASP

[Larry Bud]

Well, my company has gone into super micro-management mode, and
started a change control process for everything IT. I've been happily
coding away and now they want a change control approval for EVERY
change on our intranet that is ASP related. Does anyone else have to
deal with this? Seems WAY overblown to me, and I asked if a change
control can be approved in 10 minutes, because sometimes, that's how
quick a change needs to go into effect. They of course, said no. The
problem is, they really don't understand the web or ASP.

Any suggestions?

 

[Mark Schupp]

You're going to have to enlist the help of the client (internal or external)
who has to have changes made in 10 minutes in order to make sure that there
is a change-control procedure for emergencies.

 

[Phill. W]

Well, my company has gone into super micro-management mode, and
started a change control process for everything IT. I've been happily
coding away and now they want a change control approval for EVERY
change on our intranet that is ASP related. Does anyone else have to
deal with this? Seems WAY overblown to me, and I asked if a change
control can be approved in 10 minutes, because sometimes, that's how
quick a change needs to go into effect. They of course, said no.

So long as "they" are trying to manage [all] this at a level that "they"
can get to grips with, you'll just have to put up with it. However, all
too frequently this is /not/ the case and "they" will very rapidly find
themselves out of their depth, floundering in vast amounts of unrelated
detail and building themselves into a corner with their so-called Change
"Control" system.

If you get to this point and you're /lucky/, the "system" will collapse and
you can go back to what you were doing before. If not, you'll be
saddled with an inappropriate and inflexible "system" that nobody likes,
and everybody tries their best to work around.

The problem is, they really don't understand the web or ASP.

$ set role "Devils-Advocate"

Or perhaps - much as I was about ten years ago - you are too
used to just "hacking" your programs (web pages or whatever)
together and putting code into Production that is, us being human,
improperly and/or incompletely tested. Such code, of course, breaks
and then requires the Urgent and Immediate fixing you describe.

In more "mature" settings, changes are planned, [costed] and prioritised
before being allocated, coded, tested, [re-tested] and finally released
(and, quite probably, tested again). It is rare that bugs can slip through
such a "system" and "Emergency" fixes are few and far between - but,
as you quite rightly say, it *does* happen and any Change Control
system *must* allow for them.

Regards,
Phill W.

 

[Steven Burn]

Strangely........ I agree with Curt.

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Personal favourites

WebGrid - www.webgrid.co.uk
Freeware Arena - www.freewarearena.com
Freeware Home - www.freewarehome.com
Pricelessware - http://www.pricelessware.org
Practically Nerded - http://mvps.org/PracticallyNerded/
Bugs, Glitches n stuff - http://mvps.org/inetexplorer/Darnit.htm
Calendar of Updates - http://www.dozleng.com/updates/index.php?&act=calendar

 

[Roland Hall]

in message
: Well, my company has gone into super micro-management mode, and
: started a change control process for everything IT. I've been happily
: coding away and now they want a change control approval for EVERY
: change on our intranet that is ASP related. Does anyone else have to
: deal with this? Seems WAY overblown to me, and I asked if a change
: control can be approved in 10 minutes, because sometimes, that's how
: quick a change needs to go into effect. They of course, said no. The
: problem is, they really don't understand the web or ASP.
:
: Any suggestions?

Just one.

Your first response is to complain and try to explain to them why this is
not a good idea. They already don't understand and are making unreasonable
decisions so why would they listen to reason?

I have found that the best way to deal with micromoronmanagers is to just
give them what they ask for. Document that you think the approach they have
switched to is not a good fit for the company but you are willing to comply.
Now, send them so many change requests that their eyeballs bleed. The best
way to prove to someone who has control over your task schedule, who really
has no clue as to how anything works, is through demonstration while they
are taking responsibility. Your job is to do what is asked. When they are
willing to take on the responsibility of technical decisions, they will have
to provide answers for the delays and lack of productivity.

Ok, one more.

DO NOT EVER work around the process for anyone, including your boss, unless
of course s/he is the owner. When the s**t hits the fan, it will be
everyone for themselves. Your boss will most likely deny any culpability.
However, if your boss threatens you with grief over not following orders
when it violates company policy, that's pretty easy to work through with HR.
If HR agrees with your boss, then a good attorney can help you achieve those
two golden words, residual income. (O:=

Your job is supposed to be fun and rewarding. When it ceases to be either,
it's time to start looking. I'm always looking and I am my own boss!

In the end, you will have to make the decision that is best for you and your
situation.

HTH...

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp

 

[Larry Bud]

Or perhaps - much as I was about ten years ago - you are too

used to just "hacking" your programs (web pages or whatever)
together and putting code into Production that is, us being human,
improperly and/or incompletely tested. Such code, of course, breaks
and then requires the Urgent and Immediate fixing you describe.

In more "mature" settings, changes are planned, [costed] and prioritised
before being allocated, coded, tested, [re-tested] and finally released
(and, quite probably, tested again). It is rare that bugs can slip through
such a "system" and "Emergency" fixes are few and far between - but,
as you quite rightly say, it *does* happen and any Change Control
system *must* allow for them.

Well, to compound the problem, we have NO testers. We USED to have
testers, when the auto industry was rocking and rolling in 99 & 2000.
But we're not an IT shop, we're a Tier 1 supplier. But we have
internal legacy client/server business apps that need to be rewritten.
Right now, I am the ONLY coder. I give a time estimate for
writing/testing, but of course they want it quicker, so the testing
suffers....

I agree that developers are poor testers. I know how the app is
suppose to work, so I don't work nearly as hard (accidentally or
purposely) to break it.

 

[Larry Bud]

I have found that the best way to deal with micromoronmanagers is to just

give them what they ask for. Document that you think the approach they have
switched to is not a good fit for the company but you are willing to comply.
Now, send them so many change requests that their eyeballs bleed. The best
way to prove to someone who has control over your task schedule, who really
has no clue as to how anything works, is through demonstration while they
are taking responsibility. Your job is to do what is asked. When they are
willing to take on the responsibility of technical decisions, they will have
to provide answers for the delays and lack of productivity.

All excellent advice. Thanks!