Re: Interviewing/getting info from SMEs

[Glenda Jeffrey <jeffrey -at- HKS -dot- COM>]

Patty Ewy (pewy -at- sun1 -dot- anza -dot- com) wrote:
: One of the things that has really been a challenge is getting a system that
: makes sure that we get all the information we need from the development
: staff....

: How do you do this?

Here's an idea I intend to try:

1. Get an understanding of how the code is modularized.

2. Write a little program which goes out every night
(or every week, or whatever) and finds out what parts (modules) of the
code changed, and who changed them. This should be do-able
if your company is using any sort of automated source code control system
to track code changes. Since you've already done step 1, you'll
be able to sort out changes that affect the documentation (e.g.
GUI changes) from changes that don't (e.g. infrastructure changes).

3. The next morning, take your list and track down the programmers
responsible for the changes. Interrogate them (using bright lights
and hot candle wax if necessary) until they tell you what the
changes were.

My guess is that, after a few go-rounds with each programmer, they'll
have the bright idea that it would have been easier to tell you
what the changes were before they implemented them.

Has anybody tried this sort of technique?
--
Glenda Jeffrey                                     Email: jeffrey -at- hks -dot- com
Hibbitt, Karlsson & Sorensen, Inc                  Phone: 401-727-4200
1080 Main St.                                      Fax:   401-727-4208
Pawtucket, RI 02860