The Myth that is the “Project Timeline”

“Mail me the project timeline”, the client replies and then starts a train of tasks to set one.

When a project is approached, there is always a tentative date that the developer sets as a personal milestone. He then figures an approximate date considering the miscellaneous work to set a date and sketches a project timeline for the client to understand the flow of work with time. Sounds legit and simple, you think? Stick to the plan. Get work done.

Ah! If only it were so.

Although a definite date is set, this date now has to overcome several obstacles. For starters, awaiting the designs from the web designer. Making sure the developer has finally got his hands on what now is termed as the “approved design” by the client. This step takes longer, since sometimes feedback arrival from the client team takes longer than the tentative estimated time.

After coding the website, it still takes another week to test it. No digital agency that believes in quality services skips this one and none should.

At times, the client’s marketing team already announces the website launch date, starts campaigning the release on social media, newspapers and so on without consulting the developers. This leads to greater confusion. To avoid this confusion, it is always better to have the developer in the loop, as to what stage the project is on and ONLY when you get a green signal from the developers’ team, should the marketing strategy prove good for one and all.

So, now you know why project timelines have been so dreaded for years on by both parties alike. We at Jetbro, hence believe in keeping things better organized with regular discussions with clients, reporting them with our progress milestones during a regular interval of time. Saves the mess and avoids confusion.

Got a project that needs immediate attention? Give us a call. We love team challenges.

Originally published at technomugs.tumblr.com.