DEVELOPMENT SERVER
Rules to Successful Projects

With the convenience and cost-effectiveness of e-mail, it is tempting to resort to emails for too much client contact. Don't forget that clients are people too, and they need human interaction to ensure everything is OK. So it is essential that you maintain verbal contact before, during and after a project. What are examples of ongoing project contact?

1. Set the expectations early. Let the client know what to expect in terms of communication. For example:

   "Hi Bill,
   We will run your project in an agile manner. Expect emails and phone calls that we need responses to. These are examples:

   • The first step - we will send you a release plan to approve. Once approved we can begin work
   • Every morning - expect a 'Stand up meeting' call or 'Morning Goals' email with a list of tasks the developers will be working on that day
   • Every time a task is done - you will get an email with information about what was done, often with screen shots and code snippets"
   • If you need to change the priority of a task - email us and we will consider it for inclusion either the next release, or a subsequent one, depending on its importance"

   Avoid going more than 3 days without a phone call to your client.

2. New Resources - If you are put onto an existing project, it is good practice to call the client and introduce yourself. For example:

   "Hi, I'm Andrew. I'll be taking over from Mark on your project. Mark has filled me in on the specifics and I'm keen to get involved."

If you use the phone instead of email when it is appropriate, you maintain an open channel of verbal communication with your client. This helps to break down communication barriers, lets the client know that you are friendly and involved, and makes them feel confident in your ability to deliver the project.