3 ms·
> Regarding nudging: Ask when something will be done (with units of work that are small enough to make this viable), and get them to commit to it. If they repea
by firingtest 16y ago
> Regarding nudging: Ask when something will be done (with units of work that are small enough to make this viable), and get them to commit to it. If they repeatedly don't deliver, and fail to communicate the problems, then you know you have a problem.
That's what we've been doing almost for a year now and many failed repeatedly. Secondly when you give them strict deadlines and this kind of tracking I noticed that they might not deliver the best but they'll just fix/do something quickly and in a dirty way. Stuff like programming and Q/A testing is not easy confirm. Generally this sort of stuff bit us in the ass after months and ended up clients to be unhappy.
- auxbuss 16y agoThen, on the face of it, you have poor quality workers, or folk that are the wrong type to work remotely. For cross-checking, CI (with code coverage), tdd, and pairing helps a lot, I find. And they're cheap to do.
- wariola 16y agoThere are many automated ways to do this too. Check out Parasoft Concerto. This system does it by managing by exception. Meaning that if an artifact is not where is should be the worker gets notified. http://www.parasoft.com/concerto http://www.parasoft.com/concerto