Previously if we do not write automated tests on a web application project we felt that it is totally fine, as long as it is completed with zero or minimum amount of bugs and delivered on time. The clients also did not demand automated tests, and even if we offered it they would reject the idea as the cost of the project would increase.
Project Managers have become a very important aspect of our engineering. PM does preliminary analysis of cost and time estimate for new projects. And when the deal is closed, the PM writes a test plan, design database schema, determine day-to-day target until completion, interfacing between our designer and prototyper and the client to build a prototype, etc.
More than three years ago we worked with a US client who besides outsource some part of their work to us, also employ full-time local American developers. I know these developers personally and I know they are superb – not only the code is awesome, but also they are creative, initiative, and have a strong sense of discipline and responsibility.
A fixed-price project almost always come with a deadline. How can Developers estimate and promise in the contract how long a project is gonna take, before the project even starts? And more importantly, how Developers can keep that promise?
Before I was about to write this post I googled ‘how to deal with a difficult client’ and I know there are a lot of good information out there already, so I’d like to keep this post brief, and begin with a story 
If you have a project, it might be important not to outsource the work to more than one vendor. It might be tempting to use more than one vendor. Especially if the vendor doesnt have sufficient human resources to deliver your project within the expected time frame.
Unbeknownst to clients, many freelancers subcontract the work to other freelancers.
Yes, you outsource the work to someone, and that someone re-outsource the work to someone else!
We often feel like John, a hypothetical developer whose story goes like this. John goes to Jane’s (his boss) office everyday, but there is noone in the office, no colleagues, and no Jane. John gets an instruction on what to do once or twice a week on a short email. John works on the to-dos, deliver the results, but he very rarely gets a response to his reports. What’s worse, when he asks questions, the questions left unanswered for days, although it’s blocking him to complete the task.
Dont ever let your outsourcing relationship goes like this! The disadvantages are easy to spot…
As the boss, Jane is wasting her money. Imagine how many hours wasted because a question is unanswered in a timely manner, and how many hours wasted because a task isnt done quite as expected because Jane doesnt have time to check on the deliverables.
As a developer, John’s motivation is down to the drain pretty quickly. Motivation translates to productivity, so it hurts the client as well. As the boss, Jane needs to constantly set expectation, give sufficient pressure to pump up John’s adrenaline. Read the rest of this entry »
Basically outsourcing is the same as hiring more employees.
The difference is just a few zeros in your payroll bill.
If you own a small (or solo) consultancy business, who have been getting regular consultancy works, and you are now looking to grow your consultancy business, outsourcing is a good option.
First however, because you are a programmer yourself, you have to manage your expectation.
You may most likely notice that you can do what you outsource yourself, in a much faster speed.
This actually will be true even if you employ an in-house programmer.
But over time, you will see that you can free yourself off programming and focus more on building your business, getting new clients (or other things, like go fishing and taking a nap) Read the rest of this entry »
As recent as 8 months ago, we dont have the notion of ‘Managers’. Everyone works as Engineers and Developers.
