Forgot your password?
typodupeerror

Comment Communication and Releases (Score 1) 167

I'm project manager of outsource company and lead a team of 6 perl developers. We have completed bunch of projects - different size and duration. We have failed project - and sometime it was our fault. But now I have some simple rules that allow me to avoid that:
- Communication: I wrote every day update letter to my customer and optionally have chat twice a day - early morning and tonight (we're on GMT-6). If customer didn't answered me I suspend activity and ask sales person to call by phone or call by phone self. Anyone in a team have a way to get emergency messages: SMS, pagers etc - so we can react on such situation.
- Releases: we're trying to release anything ASAP - everyday to have a feedback from customer. It helped much when we have both fixed-price or custom site.
- Legal: we'll not work if there are no agreement about cost, payments schedule and timline is accpetable. Sometime we declined offers to not get project failed. We have lawyer department and set of different contracts for different types of services.
- Payments: CFO worked in US that allow to solve problems ASAP, so our wires and checks never lost in space.

BTW I can provide anyone with list of 10-20 references from lead countries of the world (most from US) that are *COMPLETELY* satisfied with our service. Company currently have 300 techies and about 50 managers employed. We grow twice a year - so I sure someday we can handle VERY BIG PROJECT.

Slashdot Top Deals

"Take that, you hostile sons-of-bitches!" -- James Coburn, in the finale of _The_President's_Analyst_

Working...