The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Delivery Schedule

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Delivery Schedule Posted: Apr 24, 2005 10:46 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Delivery Schedule
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Frank Patrick talks about scheduling a delivery, and relates it to a scene in an HBO movie about the Apollo program:

"Schedule Chicken" is one of my favorites. If you've ever seen the HBO Series "From the Earth to the Moon," about the Apollo program, you might remember what was my favorite episode -- the one about the Grumman engineers building the lunar lander. There's a great scene in which everyone goes around the table saying "Sure, my group's on track." until one admits the reality of needing some more time, at which point everyone then backtracks, saying, "Well, since Joe will need more time, we could use it to..." There's other PM wisdom and reality spread out in that episode. Check it out if you get a chance.

I see this every release schedule here. Towards the end, we have release meetings where we go over the high and critical bugs. The idea is, engineers who have a bug that needs fixing prior to release have to get dispensation from the rest of the team - either by explaining that there won't be a regression, or that the bug is so bad that we have no choice - you get the idea.

Towards the very end of that exercise, we start doing candidate builds. When there's something wrong in a candidate build, I see the same reaction Frank mentions: "well, so long as we are cracking the build, can we sneak this in..." - comes up every release cycle.

Sounds to me like this sort of thing is endemic to all engineering work - both hardware and software.

Read: Delivery Schedule

Topic: Smalltalk Solutions 2005 Daily Update: April 19, 2005 Previous Topic   Next Topic Topic: The supposed good old days

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use