Hacker News new | past | comments | ask | show | jobs | submit login

Setting expectations is important. You should let them know what your observation is about the amount of time that you expect the work to take, and give them the opportunity to explain to you why it's taking longer.

Agile/Scrum are good for this, because they give people the responsibility to commit to which work they'll be completing on a given day, and explain why they're blocked or moving more slowly.

Perhaps you should have a daily 15-minute scrum meeting to get a sense of exactly where they are and how things are going? More communication always makes things more transparent.

If you can't do that, set a deadline. Work will always expand to fit the allotted time, so make sure you're keeping the timeframe short enough to make sure the team knows that the project completion date is not open-ended.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: