Does this happen on projects? Why draft Collins were exempted? "Contractor or Scapegoat? The key success Contracting
By Georgina Laidlaw
February 17, 2005
Reader Rating: 9.2
It seemed like a great opportunity at the time. A business relationship that you contact the offer of some contract work. It seemed perfect: you get to work on a project you want to always dreamed about without the worry of a customer management that freelancers are often confronted. You want to deal only with the project manager, do a great job, getting paid, and everything would be sweet.
But now, you work all hours to do the work for the client on time, despite the fact that the work bears little resemblance to the first project you discussed. The scope continues creeping bug alerts come in bursts, you're three months since the initial period, customers get antsy even if they do not provide you with various information needed ... and when (if!) never finished, you are only going to pay what you originally planned before the start of work (and things got out of hand).
If you already have for someone else, you know how it can be difficult to keep a grip on the project. When you find your own independent customers, if you must bear the burden of managing customers, you can also enjoy the benefits of controlling the relationship. But often, when the freelance contract for someone else, it becomes difficult to maintain this level of control. They are in the position of "contact" rather than "respected professional, and things spiral out of control from there.
At the same time, in the unpredictable world of web design or development, things can - and do - go wrong. And too often, the project manager under the normal is pointing to his staff under contract, shouting: "the contractor did!" Too often, the entrepreneur is equal scapegoat.
The good news is: it does not have to be this hard! independent designers and developers can protect themselves against the dangers of contracting ... Once they understand why these problems arise and seize the strategies needed to combat them.
This article aims to explain some of the common pitfalls and identify the tactics you can take to protect yourself the next time you are in the dubious position of project resources.
First, we see the types of situations in which the contractor can be trusted unwittingly put themselves up to be exploited. We will discuss solutions, showing exactly how each tactic can help you answer difficult questions from your project manager or the clients themselves.
Problem
Often, entrepreneurs feel like they have little or no on a project - as we have discussed above, they feel as if they were "just a resource." This feeling may increase in a number of circumstances - circumstances that entrepreneurs should strive to avoid! Let's take a look at them now.
Specifications inaccurate or non-existent Briefings
Often, the client and the project manager wants to start working as soon as possible. So you have a meeting, the project scope in a very rough, and then someone asks you how long it may take you "get something for us."
In other cases, the project manager will go away, write a spec - a specification that may or may not be as precise as you would ideally like - and have signed by the client even before you had the chance to questions. Or maybe you just do not like the process of scoping, and itching to start before starting the project has been specified in detail.
Obviously, this is a recipe for disaster. Projects must clearly and framing, though it may appear dull now, Naili.
Posted on April 21, 2010.
