Introduction

(draft version)

External Developers (Independents) can be used to fulfill tasks. This can be

• HTML/CSS design
• Solving a problem within the code
• Implementing Code based on a provided skeleton/specification
• Complex analytical / rework tasks

A few guidelines should simplify the process of hiring an independent developer.

Basics

From the point where you agree to a contract, you should do everything to keep the independent running. Of course this is the same if the independet has 'knocked your door' to offer his services. If you use his services, provide the conditions he need thus he brings results and likes you as an cooperation partner.

Don't forget that many times you have a responsibility against the human that you hire. This is especially true if the individual is in a weak position. Never abuse the position to make better negotiations for your side or to cover your own weaknesses. On a long term, this will not pay out. Loyality is something that you will achieve through total fair-play.

There are situation where something (e.g. your actions or sayings) can be missinterpreted. This is especially true, if the independent has entered a deep teach-in or analytical phase.

Higher Grade Tasks

People with high amounts of experience work normally autonomously. This is something that companies require.

It is important to await the results, instead of trying to follow the process and to loose worthfull time.

You should relax and say:

• I have choosen this independent
• I am drinking my coffee and the work get's done.

Rework

Tasks like Redesing, Refactoring, Reengineering, Analysis etc. depend on several phases:

• task-definition / teach-in-phase,
• teach-in / analysis-phase,
• analysis / brain-ripening-phase
• final result-phase.

It is very important to not interupt this process, e.g. whilst passing new requirements in the middle of the brain-ripening-phase. This can collapse the whole creation-process, which reduces results and brings frustration to both, customer and independent.

Used Resources (e.g. Project Resources) should be barrier free, especially for the final-result-phase.

Duration

• An compact overall review can be done simply within one week.
• A Product Evaluation (e.g. change of documentation) can be limited to a week.
• A Code Abstraction can possibly be done in one-week chunks.

But an independend needs to have some time-budget available, to extend the phases, especially when going into overall code-refactoring / code-abstraction / code-extension.

If a task needs e.g. 4 weeks to be solved, it is impossible to split this into 4 single weeks which are negotiated separately. There would be no verfyable results until the last 2 weeks, in some cases until the last week.

Paying Money and Stay Happy

To avoid mental stress, this external work must be treated like any other product in real life.

Sometimes one buys something, but the product is finally not good. Nothing special, especialy for low priced goods.

If you buy a car, things are different of course.

Monetary Budget and Rates

Define a monetary budget. Say:

• ok, I will invest $1.000 to go to the direction of Goal A/B/C.
• If I achieve the goal, I'll save $800 anually.

Define and accept a rate. Say:

• ok, the daily rate of $200 is fair for this independent.

Time Budget

Decouple after this the thoughts from the "money"

Tasks are rated (whenever possible) by time budget. Say:

• ok, this task must be done.
• ok, the amount of 8 hours is ok for this task.
• I have still a time budget of 32 hours.

Do not say:

• I have to pay $100 for this task.