Re: Tech meetings

I've found both as a manager in Oracle and in Miracle that if you schedule regular meetings with the guys (and girls), then they start not showing up after a while, or the meetings become boring. If you don't hold regular meetings they'll complain and wish for regular meetings.

So I've come up with this model:

1st meeting
2nd meeting after a week
3rd meeting after two weeks
4th meeting after four weeks
5th meeting after eight weeks (around here or at next iteration they start complaining...)
6th meeting after a week...
7th meeting after two weeks...

Mvh Mogens

Babette Turner-Underwood wrote:
<blockquote type="cite"
 cite="">
  Message             

  <font face="Arial"
 color="#0000ff" size="2">From time to time, we go through a series of "show and tell" where people do about an hour long presentation, question and answer on some usually technical topic. Occasionally these presentations are business related (eg explaining how the Canada Pension Plan international agreements affects the programs we are doing).  

  <font face="Arial"
 color="#0000ff" size="2">They die off, then the director resurrects them by asking for volunteers. Occasionally, people are told to do a presentation on a specific work -related topic.  

  <font face="Arial"
 color="#0000ff" size="2">-  

  <font face="Arial"
 color="#0000ff" size="2">Babette        

<font

 face="Tahoma" size="2">-----Original Message-----

    From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rudy Zung

    Sent: Tuesday, July 01, 2003 3:05 PM     To: Multiple recipients of list ORACLE-L     Subject: RE: Tech meetings              

<span

 class="666435417-01072003">Don't know if what we do in our shop here qualifies    for your question or not, but our dev groups do "stand-up meetings."  Relatively quick meetings (that can be done standing up; no meeting rooms    required) that are usually finished in about 20 minutes. In the stand-ups, we get heads-up for things and specifications that might be coming down the pipeline from the product management and design side. We get a quick update on the state of deployment (what version has rolled into production, what version is in the QA pipeline) and what the next impending set of changes are about to get pushed onto the dev servers. If there's any potential "gotcha"s that have been experienced (especially on the coding front) they get publicized in the stand-ups as well.    

<span

 class="666435417-01072003">     

<span

 class="666435417-01072003">The main point of our stand-ups are to make sure that all the developers are relatively aware of the scheduling and direction of the product, and to highlight any programming difficulties and workarounds that might arise so that when different developers hit those gotchas, they'll already know that a solution might already.    

<span

 class="666435417-01072003">     

<span

 class="666435417-01072003">These stand-up meetings are basically within a development team/group. Project leads have their own meetings with the product management group. So essentially, the product manager has his own meetings; then the product manager has meetings with the dev project leads to convey what they want in the next iteration of the product; the project leads then present these to the dev group in a stand-up meeting.    

              
      <div class="OutlookMessageHeader" lang="en-us" dir="ltr"
 align="left">-----Original Message-----
      From: M.Godlewski      [mailto:[EMAIL PROTECTED]] 
      Sent: Tuesday, July 01, 2003 12:30      PM
      To: Multiple recipients of list ORACLE-L
      Subject:      Tech meetings
      
      
     
      List,
     
       
     
      Just wondering if your organization has tech meetings, and what
is      discussed and what the goals of the meetings are?
     
       
     
      I've been asked about this, and was wondering if there is a quick
list      out there any where.
     
       
     
      TIA<font face="Arial"
 color="#0000ff" size="2">