| 1 |
Donnie Berkholz wrote: |
| 2 |
> Chris Gianelloni wrote: |
| 3 |
>> Now, perhaps what everyone would like, instead, would be status reports |
| 4 |
>> *where necessary* from certain projects? |
| 5 |
>> |
| 6 |
>> In fact, the council has been discussing asking a few projects about the |
| 7 |
>> status on some of their tasks. The main reason for this is for |
| 8 |
>> communications purposes. Basically, we'd just get a "Hey, where are you |
| 9 |
>> at on $x?" response from the teams. |
| 10 |
>> |
| 11 |
>> I don't *want* to drown projects in bureaucracy and paperwork. I want |
| 12 |
>> them to *accomplish* things, instead. |
| 13 |
> |
| 14 |
> I really like the concept of answering questions rather than giving |
| 15 |
> arbitrary reports. The problem is, sometimes nobody outside your project |
| 16 |
> knows the right questions to ask. |
| 17 |
|
| 18 |
I was thinking more about this. What if, instead of these periodic |
| 19 |
status reports, you just send out a note when something interesting |
| 20 |
happens? There's no point in holding it back till your monthly required |
| 21 |
report, and it saves the trouble of the report when nothing's happening. |
| 22 |
|
| 23 |
Thanks, |
| 24 |
Donnie |
Archives