469,903 Members | 1,612 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,903 developers. It's quick & easy.

FDLC issue

On a VB/ASP project, how do you convince a manger who
doesn't believe that a development methodology in the FDLC
is necessary in today's IT market, is REALLY necessary?
This manager believes this process slows the development
process down significantly, especially with ASP
development. This manager believes this process probably
works better for software companies than normal industries
like insurance, banking, manufacturing, etc. This manager
would rather see poorly written ADHOC code that works and
was produced quickly, than analysis that was thought out
and good code was written in the process. This manager
also believes that documentation should come after your
done programming than during the FDLC.

Has anyone every dealt with this situation before, and
succeed in changing the manager view of IT development?

Jul 19 '05 #1
3 2538
I've heard of the Systems Development Life Cycle, but cannot figure out what
the F stands for.
"BadManager" <an*******@discussions.microsoft.com> wrote in message
news:03****************************@phx.gbl...
On a VB/ASP project, how do you convince a manger who
doesn't believe that a development methodology in the FDLC
is necessary in today's IT market, is REALLY necessary?
This manager believes this process slows the development
process down significantly, especially with ASP
development. This manager believes this process probably
works better for software companies than normal industries
like insurance, banking, manufacturing, etc. This manager
would rather see poorly written ADHOC code that works and
was produced quickly, than analysis that was thought out
and good code was written in the process. This manager
also believes that documentation should come after your
done programming than during the FDLC.

Has anyone every dealt with this situation before, and
succeed in changing the manager view of IT development?

Jul 19 '05 #2
Full Development Life Cycle
-----Original Message-----
I've heard of the Systems Development Life Cycle, but cannot figure out whatthe F stands for.
"BadManager" <an*******@discussions.microsoft.com> wrote in messagenews:03****************************@phx.gbl...
On a VB/ASP project, how do you convince a manger who
doesn't believe that a development methodology in the FDLC is necessary in today's IT market, is REALLY necessary?
This manager believes this process slows the development
process down significantly, especially with ASP
development. This manager believes this process probably works better for software companies than normal industries like insurance, banking, manufacturing, etc. This manager would rather see poorly written ADHOC code that works and was produced quickly, than analysis that was thought out
and good code was written in the process. This manager
also believes that documentation should come after your
done programming than during the FDLC.

Has anyone every dealt with this situation before, and
succeed in changing the manager view of IT development?

.

Jul 19 '05 #3
On Tue, 23 Dec 2003 14:58:24 -0800, "BadManager"
<an*******@discussions.microsoft.com> wrote:
On a VB/ASP project, how do you convince a manger who
doesn't believe that a development methodology in the FDLC
is necessary in today's IT market, is REALLY necessary?
This manager believes this process slows the development
process down significantly, especially with ASP
development. This manager believes this process probably
works better for software companies than normal industries
like insurance, banking, manufacturing, etc. This manager
would rather see poorly written ADHOC code that works and
was produced quickly, than analysis that was thought out
and good code was written in the process. This manager
also believes that documentation should come after your
done programming than during the FDLC.

Has anyone every dealt with this situation before, and
succeed in changing the manager view of IT development?


Basically, you have three options. Accept his requests, quit and find
a new job or kill him and assume his position. Note that the third
one may sound acceptable but most organizations will frown upon it...

Jeff
Jul 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by George Hester | last post: by
2 posts views Thread by Anthony Cuttitta Jr. | last post: by
reply views Thread by Kevin Spencer | last post: by
reply views Thread by Charles Leonard | last post: by
4 posts views Thread by Paul | last post: by
13 posts views Thread by SAL | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.