From babette@rogers.com Tue, 08 Jul 2003 17:15:55 -0700
From: "Babette Turner-Underwood" <babette@rogers.com>
Date: Tue, 08 Jul 2003 17:15:55 -0700
Subject: RE: Tech meetings
Message-ID: <F001.005C3EAB.20030708170925@fatcity.com>
MIME-Version: 1.0
Content-Type: text/plain
Title: Message



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 ZungSent: 
  Tuesday, July 01, 2003 3:05 PMTo: Multiple recipients of list 
  ORACLE-LSubject: 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> 
  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.
  
    
    <FONT 
    face=Tahoma size=2>-----Original Message-----From: M.Godlewski 
    [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 12:30 
    PMTo: Multiple recipients of list ORACLE-LSubject: 
    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> 
    <SPAN 
class=666435417-01072003> 



