ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Web Dev Projects from Hell?

April 06, 2011 3:22am

Subscribe [2]
  • #1 / Apr 06, 2011 3:22am

    Bransin

    157 posts

    Any stories you would like to share around the campfire?

    Currently getting tired of a never ending project and a scope that is so vague where the sky is the limit.

  • #2 / Apr 06, 2011 5:26pm

    grrramps

    2219 posts

    Currently getting tired of a never ending project and a scope that is so vague where the sky is the limit.

    It’s so important to get the basic details down up front. Define the scope. I do ‘this’ and I get paid ‘this much.’ Anything else I do costs ‘this much’ more.

    A never-ending project isn’t so bad if you’re able to bill for what hasn’t ended yet.

    I love billable hours.

  • #3 / Apr 06, 2011 10:11pm

    Bransin

    157 posts

    A never-ending project isn’t so bad if you’re able to bill for what hasn’t ended yet.

    So true. When working freelance I feel I have these bases covered. Where it becomes a problem is when working for a web agency and a scope that was developed by the partners/sales where research is limited and specificity lacks in the final scope.

    I’m paid for my work on salary, but where it becomes an issue for me is when the client has expectations of deadlines, and the produced timeline is always too short and never accurate.

    For a web development agency, should a project manager have a web technical background?

  • #4 / Apr 06, 2011 10:35pm

    grrramps

    2219 posts

    For a web development agency, do you think a project manager should have a web technical background?

    Not necessarily, but those who do tend to have just enough knowledge to be dangerous. When taking on a new project it’s still best to define the scope on your terms. In other words, their scope is general, your response is specific. Always work to your specifics. Anything beyond that becomes billable hour material (with appropriate change order requests).

    However, that doesn’t address a current situation where you’ve already agreed to a wide scope and the client keeps piling more on top (often details that were overlooked). At this point, you add up all your hours to date, itemize all you’ve done so far, and politely and honestly let them know you cannot continue under those circumstances. Reason #1 - not enough detail in scope and specifications to provide an accurate or reasonable bid for the project. Reason #2 - continually adding more detail, or more requirements, alters the original scope. Both situations are untenable going forward. If they’re a worthy client, they’ll back up and approach the project on terms that are beneficial to both. If they’re an unworthy client, they’ll be pissed, probably fire you (legal action might be a threat, but always difficult to squeeze blood from a turnip), and bring in someone else. In that case, count your blessings, and move on.

  • #5 / Apr 07, 2011 6:49pm

    Rob Allen

    3114 posts

    So true. When working freelance I feel I have these bases covered. Where it becomes a problem is when working for a web agency and a scope that was developed by the partners/sales where research is limited and specificity lacks in the final scope.

    I’m paid for my work on salary, but where it becomes an issue for me is when the client has expectations of deadlines, and the produced timeline is always too short and never accurate.

    It’s always hard when you’re at the mercy of someone elses specs. When working for agencies and I get a new project to look at I tend to question everything before work starts - often the sales person has to go back to the client to answer my questions and it’s then that things start creeping out the woodwork, and making the impossible deadline obvious!

    One project I looked at last year appeared straightforward on paper, but once I’d grilled the sales rep and got the answers I wanted they suddenly realised the job was 5x as big as first thought. I passed that one on 😊

    For a web development agency, should a project manager have a web technical background?

    I’d say that depends on the person. A good project manager should be able to manage any project in any industry because they will take time to learn about the ins and outs of the medium they’re working in. A poor project manager will probaby balls things up.

    I have always been of the opinion that any manager should have some background in the industry in which they’re working, the best ones I’ve ever know have all started at the bottom and learnt their trade.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases