| 1 |
On Wed, 04 Oct 2006 10:27:17 -0400 |
| 2 |
Chris Gianelloni <wolf31o2@g.o> wrote: |
| 3 |
|
| 4 |
> > > - Project status reports once a month for every project |
| 5 |
> > |
| 6 |
> > Totally agree on this one! |
| 7 |
> |
| 8 |
> OK. |
| 9 |
> |
| 10 |
> I'll give you Release Engineering's "status reports" for September, |
| 11 |
> October, and November: |
| 12 |
> |
| 13 |
> September: taking a well-deserved break |
| 14 |
> October: taking a well-deserved break |
| 15 |
> November: taking a well-deserved break |
| 16 |
|
| 17 |
Well, in the past, I've found that even getting brief reports like that |
| 18 |
is very helpful when I've been running meetings. It's just generally |
| 19 |
good to know that folks are alive and such, and a brief "Hi, we're |
| 20 |
still here" kinda report every month is nice for that. Just a quick |
| 21 |
email before the meeting works fine. Also, it gets everyone in the |
| 22 |
habit of giving reports, so that they remember to report when something |
| 23 |
new happens. |
| 24 |
|
| 25 |
> I don't *want* to drown projects in bureaucracy and paperwork. I want |
| 26 |
> them to *accomplish* things, instead. |
| 27 |
|
| 28 |
Sending a brief "All's well with releng" email isn't exactly what I |
| 29 |
would call "drowning in bureaucracy". |
| 30 |
|
| 31 |
-- |
| 32 |
Mike Kelly |
Archives