[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Hewlett Packard DST Project

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
on.)

Mr. William Woo, DST project manager, gave a presentation on June 24, 1994 which we attended. He was kind enough to share his slides with us.

Team has six developers.

Instead of a heavy emphasis on documents as deliverables, brief (e. g., 1-2 page product data sheet) documents are written.

Within a development cycle, each engineer is assigned "bite size" functionality to implement. An example of a checkpoint within the cycle is a design review, per engineer. In design review the code of a working prototype is examined. Another per engineer checkpoint is "functions complete."

Code reviews are done whenever the engineers want them.

"Key thing in this for managers is measuring the ability of your engineers."

"Do everything as small as possible for meaningful releases."

The team has an ad-hoc source code management scheme.

Because Mr. Woo has experience managing QA, we found his process had emphasis on testing. Engineers write their own unit test code, and they also use an in house tool that generates test code. Testing is performed on several component levels.

Our feeling about this process: although it seemed somewhat informal, it works because of the skills of the team members, and Mr. Woo's knowledge of his team's abilities. The emphasis on testing is better than most Smalltalk projects we have encountered.

[ prev | top | next ]