That (sleep) being said, I would caution you to not repeat the mistake I've seen many people make: using a sleep that works most of the time, but fails when things get busy.
Here's the scenario: you've got a process you want to wait for and it takes a couple seconds. You put the sleep in and everything's fine till one day the process takes ten seconds for some reason. Your assumptions go to heck and your system fails.
If this is your possible scenario, try to look for ways to know for sure if the thing you're waiting for is done. Waiting for a return code. Or maybe a wrapper that runs process A, waits on it and then runs process B only when A is really done.