The Methods & Tools newsletter has just released in its html archive
section the article "Project Failure Prevention: 10 Principles for
Project Control". It is now well-known and well-documented that far
too many projects fail totally or partially, both in engineering
generally and software engineering. Everybody has some opinions about
this. This paper offers some of Tom Gilb's opinions and originality to
the discussion. The basic premises in this paper are as follows:
* We specify our requirements unclearly;
* We do not focus enough on ensuring that the system design meets the
requirements.

http://www.methodsandtools.com/archive/archive.php?id=56

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete

On Tue, 05 Jun 2007 04:35:14 -0700, editormt wrote:
> The Methods & Tools newsletter has just released in its html archive
> section the article "Project Failure Prevention: 10 Principles for
> Project Control". It is now well-known and well-documented that far
> too many projects fail totally or partially, both in engineering
> generally and software engineering. Everybody has some opinions about
> this. This paper offers some of Tom Gilb's opinions and originality to
> the discussion. The basic premises in this paper are as follows:
> * We specify our requirements unclearly;
> * We do not focus enough on ensuring that the system design meets the
> requirements.
>
> http://www.methodsandtools.com/archive/archive.php?id=56
>
How about the most basic principle of all:
P0: GOOD PEOPLE: Find, reward, develop and retain people who succeed in
their tasks, produce good work and do what they say they will.

Pete