I started my new contract just after a guy had been newly promoted into a "team lead" position.
He interviewed me too, and is a decent enough guy.
Unfortunately a week or so after I started he implemented a new bi-weekly status report that all the devs have to email him detailing everything you have been doing in the preceding 2 weeks.
This afternoon, we have a 2 hour meeting to go through it all, discuss etc
sigh!
-
I know, I know, it's stupid, unproductive and infuriating. I've tried to master the art of sleeping with my eyes open but just can't get the knack of it. Just invoice, man, invoice.Originally posted by Ignis Fatuus View PostLeave a comment:
-
Managed properly they help stop wasted effort and maintain the teams focus and drive.Originally posted by Ignis Fatuus View Post
I've found that an issue log followed by - is there anything else which needs to be raised meeting is best. No round table status updates, attendance is compulsary and anything which needs more than 2 minutes discussion is left for those involved to sort out afterwardsLeave a comment:
-
I used to work on a failing account that had daily status meetings that lasted 2-3 hours and bascially went over the same old ground. I canned most of them on the grounds that I could usefully spend the time fixing the problems instead of being dragged around in circles. I changed the reporting so that it showed good news.
Funny how the bloke that took over from me couldn't keep the same level up....Leave a comment:
-
Status Meetings
Why is it that when there is loads of work, management think that the best way to handle it is to have everyone in a status meeting every day?
Leave a comment: