Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Re: A Cautionary Rant

by Fastolfe (Vicar)
on Apr 09, 2001 at 21:42 UTC ( #71092=note: print w/replies, xml ) Need Help??

in reply to A Cautionary Rant

Sounds like bad organization. You need a Project Manager. Someone that gathers business requirements and coordinates between developers, administrators, security and the client. All changes and enhancements go through the project manager. The developers are approached from and communicate with, chiefly, the Project Manager. Naturally there will be details that require some direct contact between the various parties, but things like change requests, deadlines and all of the coordination would be handled by the PM. Regular meetings are good too, and those that chronically fail to attend should be disciplined if the project suffers as a result.

Replies are listed 'Best First'.
Re: Re: A Cautionary Rant
by petethered (Pilgrim) on Apr 10, 2001 at 01:10 UTC
    I personally work for a small startup ( VERY SMALL ), and even in small companies this type of thing happens.

    A perfect example is the project we are currently working on. Even with 2 programmers, there are a number of steps that we have to go through to code up and running.

    Get the project description.

    Write some code

    Have the results rviewed for changes ( and for some reason, 90% of the time major "oh, can you add this" additions occur )

    Write more code, and rewrite/change 50% of code

    Get reviewed again

    write more code... and rewrite more code

    Get reviewed again

    HTML guy takes over ( all code we produce is templated , other then table internals ect )

    Make a ton of changes for HTML guy

    Reviewed again, now with the HTML

    write more code...

    It goes on and on...

    It seems to me , no matter how big or small the company, an inordinate amount of time is spent developing the project compared to actually developing the code.


      That can be very true, the problem is I think.. most times ppl. don't understand or thoroughly understand the whole project until at least half the prottype is ready to be shown to the upper management to gain approval/critisims/suggestions. Sometimes developing the project can be half the battle of a project.. Fastolfe is right about a Project Manager - it does help. It leaves the project leads and other developers free to do their job and allow the administrative tasks to be handled by someone else who is outside of the project development(coding that is..), but who understands what the project must do.. they sometimes can also coordinate with the clients to gain feedback or be the main person of contact via the developers. But, knowing the project and developing it to specs(no matter how many versions down the road) takes quite a bit of time - and communication is really key.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://71092]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (4)
As of 2017-11-18 01:57 GMT
Find Nodes?
    Voting Booth?
    In order to be able to say "I know Perl", you must have:

    Results (277 votes). Check out past polls.