OO Software Project Entropy Question.
From: AndyW (foo__at_bar_no_email.com)
Date: 08/08/04
- Previous message: Hamilcar Barca: "Re: misconceptions on computer science"
- Next in thread: H. S. Lahman: "Re: OO Software Project Entropy Question."
- Reply: H. S. Lahman: "Re: OO Software Project Entropy Question."
- Reply: Phlip: "Re: OO Software Project Entropy Question."
- Reply: JXStern: "Re: OO Software Project Entropy Question."
- Reply: Phlip: "Re: OO Software Project Entropy Question."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 08 Aug 2004 18:22:41 +1200
Hi folks - I'm just doing some research on the subject of Software
Project Entropy (in OO development) and have some questions.
This is part of the subject area of Chaos Theory in Software Project
Management that I was doing some work on many years ago - so holds
some level of interest for me.
Background [context]
Software Project Entropy often occurs when the rate of 'work' is high
but nothing is being produced. When this occurs at the extreme level -
the software project stalls - often resulting in a failed project.
One of the reasons [the one I want to focus on here] is that software
projects may focus on fixing defects rather than producing new code.
This can occur when process and/or requirements are ill defined and
bad code is produced.
Alternatively the software development method being used on the
project may have a focus on mini-cycles where development is followed
by brief periods of bug-fixing. This is performed usually in short
incremental cycles.
If the code being produced has a low level of quality in that the
number of defects being found during the micro test phases is high -
the project may tend to spend more and more time fixing bugs. As this
time being spent gets longer and longer, the time available to
procuding new code gets shorter. Thus entropy is occuring on the
project with the result being an eventual development stall.
Questions
I have 3 basic questions that i'd like to ask, but welcome any
disussion on any other ideas/experiences people may have related to
this topic.
1). As entropy occurs on the project, so the cost of the project
rises. If the entropy level increases, then the percentage of the cost
of the project that is incurred due to wasted effort also rises.
Do people monitor this - either using metrics or some other technique
- if so how (comment ?].
2. The introduction of the newer more modern techniques for software
development (i'm thinking of Agile/Extreme etc] means that the
mini-cycles as mentioned above are more likely to occur.
What effect do these methods have on the levels of entropy in the
software project - is it reduced or increased or is there no focus
given to it - why ?
3. Following on to question two - given the older techniques/methods
that were in use before these methods came about [became mainstream] -
is there a comparison that can be made.
I do not want to create a debate on the methodologies mentioned above
- I just want to use them since many people are familiar with those
that i have mentioned.
Also, my background is in large software development (millions of
dollars, thousands of people) - so if anyone else is familiar with
that environment would like to comment that would be great. I
suspect that it would be more relevant to looking at small and medium
sized projects as I feel that most people come from that invironment.
So for the purposes of this discussion - i shall choose the smaller
scale projects.
Cheers
Andy.
- Previous message: Hamilcar Barca: "Re: misconceptions on computer science"
- Next in thread: H. S. Lahman: "Re: OO Software Project Entropy Question."
- Reply: H. S. Lahman: "Re: OO Software Project Entropy Question."
- Reply: Phlip: "Re: OO Software Project Entropy Question."
- Reply: JXStern: "Re: OO Software Project Entropy Question."
- Reply: Phlip: "Re: OO Software Project Entropy Question."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|