Re: user discussion & meeting and more meetings

[Kris Van Hees <kris.van.hees@oracle.com>]

To chime in on this a bit...   One of the difficult points with frysk
development (from my side) right now is that there is very limited
visibility into the progress of frysk aside from the UI.  These is also
not really information I have been able to find on the side of project
management, in terms of what is being worked on, what the milestones
are, where priorities ought to be, etc...  Truly, basic project
management and knowing who is doing what.  It's kind of important to be
able to share that information, and also to be able to participate in
the decisions that lead up to it.

	Kris

On Tue, Feb 20, 2007 at 05:48:45PM -0500, Andrew Cagney wrote:
> 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