Re: user discussion & meeting and more meetings

[Andrew Cagney <cagney@redhat.com>]

Can you be more specific as to why you consider weekly planning meetings 
to be necessary, or more necessary than giving developers an opportunity 
to get direct feed back on their work.

The discussion has really focused so far more on UI with:

- making requested changes in response to a meeting is >1 week work; 
weekly review of a specific component isn't reasonable
- people max out of a topics discussion (including UI review) at about 
30-60 minutes; so limit the amount of material handled is important
- UI review has very positive effects - developers get to experience 
first hand users succeeding or struggling with what they have implemented

To me this suggests, w.r.t. UI, short sharp weekly reviews focued on a 
single topic may work better:

- possible to run two or more items in parallel - one updated each week
- avoids any delays in getting something onto the agenda
- again gives developers that direct positive feedback that leads to 
better code

Perhaps the time can be split evenly?

Andrew


Elena Zannoni wrote:
> Stan Cox wrote:
>> On Wed, 2007-02-14 at 12:05 -0500, Andrew Cagney wrote:
>>  
>>> -> Cycle the Wednesday meeting so that it alternates between user / 
>>> technical / co-op focused     
>>
>> I vote for cycling the meetings, with week 1 for
>> planning/administration/idea exchange and week 2 for technical
>> discussion.
>>
>>
>>
>>   
>
> A project management meeting every 2 weeks is not going to cut it 
> unfortunately,
> given the scope and the size of the project it needs to be done every 
> week.
> Doing UI every 2 weeks is reasonable.
>