[kplato] Scope and Change Control (was Planning and Analysis 101)

[Chris Clarke]

I wasn't going to reply to any message tonight, but I know tomorrow when I 
wake up there're going to be too many waiting, so...

On Thursday 14 June 2001 19:52, Chris Herrnberger wrote:
> On Thursday 14 June 2001 19:25, Chris Clarke wrote:

> > [Configuration Mangagement]
>
> Hmm me thinks we are soon gonna need a glossary of terms. Config 
> Managemnet usually referrs to systems configuration management and
> associated documentation and the control there of. ( then again it may be
> my background) 
> I completely understand your point however and you are quite
> correct but perhaps we need to start a glossary so that the terms can be

Probably a good idea.  I'm very happy to have non computer 
engineers/scientists involved -- the computer industry doesn't exactly have 
the best track record for project managment :-)

> learning Python SiG meeting...well more beer than python. I really like
> learning python this way.....:)

Best way to learn.  Perl works even better after several beer.  _Several_ 
beer.  Eventually it almost makes sense (although you cannot drive home by 
that point).

By my calculation if you're in Ottawa it's about 11:00 now.  That's a pretty 
late "meeting".

[Snip]

> In terms of the proposed app, standard integration with the Gant diag
> section and auto updateing of all associated dependacies (resources
> schedules costs) If say a doc browser were included, tracking of doc
> revisions would be really sweet.

Okay. 

[Snip my thoughts on the revision management process]

> agreed but there are also associated impacts on resources, schedules and
> all other interdependant events, (thats where you either loose or make
> money on tracking the dependancies. ie: What effect will change order No1
> have on event No.12: Depending if your the owner or contractor....it means
> revenue or loss if not tracked and assessed in terms of the overal time
> line and all other measured parameters.)

Yup.  This is one of the areas where I see a huge shortcoming in any of the 
tools that I've used.  It sounds like you're the one who's going to help us 
get this right :-)

[More snippage]

Okay the documentation stuff I'm going to have to read through some other 
time.  It sounds like we're actually coming from the same direction just with 
slightly different terms.

One big difference between running a large software project and running a 
large civil project is I believe the scope of change is much higher in the 
computer project, since we don't have the body of knowledge dating back as 
far as you do.  I'm going to be really interested in how you manage change 
impact, I think there can be some lessons to be learnt there.

All this talk of beer makes me realize that there's a nice cold Okanagan 
waiting at the bar...

Chris C.
-- 
Chris Clarke
security@cfourconsulting.com
http://cfourconsulting.com