Web Development Firm - Common Problems - Looking for Solutions!

Hello,

We are running a Web Development Firm and we decided to re-look into the systems to enhance it for betterment.

Below are some details of quick analysis:

Problems Ordered in Priority

Out of Scope
Unclear Requirements
Deadline Miss
Dislikes Design
Delay form client side
Changes after Phase Approval
Clients deny Rules

What are the Solutions you Suggest to these problems. Detailed solution or ideas would help.

eyashwant - AIM, Skype, Gmail
eyashwant_1000 - Yahoo
- MSN

Thanks in advance.

 

We have run into several of the same issues.

Some things we have begin implementing to try to minimize these issues are:

Spend more time on gathering requirements
Use Change Control forms when changes or out of scope work is requested

 

Hello,

Yes, After our analysis we found the same.

We can give this a try, but not always easy as our clients are always busy ones.

We looked at this too. Not yet implemented, BUT, we sent updates by email and then client give feedback by email. So in this case, you copy that and paste it in this form and send to client for review and sign?
Do you actually get a signature? Won't this be annoying to sign tons of time? Or you just use the form with no signature?

Btw, Can you email your form sample if possible to
Then I can understand a little more.

May be we can have a chat on this a bit?

 

Change control in a client/ supplier relationship is slightly different and probably wouldn't go as far as demanding a form. Your basically asking them what the new functionality/ feature they want is. You reply with either your new estimate or quote including price and time impacts depending on if your doing fixed price or T&M. The client then decides if they want to go ahead with the change or not.

Unclear requirements is simply your own fault for not gathering them properly. You should document them on behalf of the client and have them sign it off. Your plan should have this as a milestone and you have pre explained that you cannot go on until milestones are completed.

Deadline missed means bad planning. You need to work out if your underestimating the time something will take or over estimating how much time someone can dedicate to the project.

Design is simply a requirements gathering issue again.

Client side is never a "delay", you state your plan based on lapsed time not fixed dates.... it will be 2 weeks from your sign off not it will be on 14 November. If you run concurrent projects you'll have to put a block of time in for sign offs to maximise utilisation but you can adjust as you learn your clients speed (likewise, remind before that something will be ready on X date and sign off is needed before going on etc etc - don't just tell them on the day)

After phase changes is just change control

Dont know what your meaning by the "rules" and so not surprising the clients don't either

 

If you have unclear requirements then there always be a difference in what the client wants. This is the most important thing that any designer or in your case the company has to look into.

Just like my case, a Portuguese guy wanted me to design his website, but there was a huge language gap between both of us! That's why I had to delay his project and when i completed the design.. he rejected it :'(

 

No, We get clear requirements from clients. BUT, Some of our long term clients who needs 50 sites and 100 sites in a year, asks us to make one ourself and that is a problem. Some times in development, they may give a big site as reference and we will add in proposal some features. They ignore proposal details and ask for out of scope works. Long term client, some times cannot resist.

This makes it clear. So you reply the way client communicates like email, etc,. Not going to make a form and make him sign and stuff.

Yes, We do document. Asking client sign off is a trouble as he has to print, sign, scan and email. Another task for him and it will make them feel bad.

If a project runs and client takes 3 days to reply for a feedback or disappears for a week, that's what I can deadline miss. Another is additional tasks out of project scope increases time. Etc,. Not a problem with estimate.

Right, But not all clients have idea initially. They wanted us to try.

Right. This is good way. BUT, If in middle of project 2 days client is off and we are to wait for feedback, we have to push deadline and explain client. Is that the process?

Right, After Phase approval, it's change control form and additional cost and time. That's what we planned.

Rules can contain all that is discussed above, late payment avoiding rules, etc,. Some don't like to go with it, but they are long term clients. Good Ones, but don't like to follow these.

Thanks for all your suggestions so far. I appreciate it!