Planning Extreme Programming book

[SirGilligan]

I just came across the book, "Planning Extreme Programming."

I find it very interesting! It is amazing how it contains comments
very similar to my "Maverick" writings!

http://home.att.net/~geoffrey.slinker/maverick/MaverickDevelopment.htm
l
Often, important dates for a project come from outside the company:
• The date on the contract
• COMDEX
• When the VC money will run out
I have watched the release dates for the product set by the next
occurrence of COMDEX and not by anything that really pertains to the
development of quality software....In Maverick Development there is
no "release date by trade show". How many times have you had a
release date for a product set by product marketing to be for the
next trade show? Where is the basis on that choice? They will tell
you that if you miss that date we will miss our window of
opportunity. The ability to market and display a product at a trade
show is advantageous. However it is not sufficient to require the
release of a product based on date alone. If the original time
estimation for the set of features places the release date beyond the
trade show then the feature set must be changed to correspond with
the shorter development time.

I guess experience teaches us all the same lessons!

Geoff

[Laurent Bossavit]

Geoff,

If the original time estimation for the set of features places the
release date beyond the trade show then the feature set must be
changed to correspond with the shorter development time.

In the case of COMDEX, there's an even more powerful strategy. The
trade show rolls around more or less at the same time of year each
year, quite predictably. So start the project earlier instead of
waiting until it's almost too late.

Cheers,

-[Laurent]-
If a program is useless, it will have to be documented.

[SirGilligan]

That would work great! I wish PM's would consider that in their long
term thinking. I do imagine that good ideas don't always come "one
year" before a trade show. Often they come 2.78 months before a trade
show. If we could just schedule good ideas to appear at certain
intervals! ;-)

Geoff

Post by Laurent Bossavit
Geoff,

If the original time estimation for the set of features places the
release date beyond the trade show then the feature set must be
changed to correspond with the shorter development time.

In the case of COMDEX, there's an even more powerful strategy. The
trade show rolls around more or less at the same time of year each
year, quite predictably. So start the project earlier instead of
waiting until it's almost too late.
Cheers,
-[Laurent]-
If a program is useless, it will have to be documented.

[Laurent Bossavit]

Geoff,

If we could just schedule good ideas to appear at certain intervals!

Or if we could just design programs so that they're always ready to
incorporate good ideas... whenever they appear !

Cheers,

-[Laurent]-
How come wrong numbers are never busy?

[SirGilligan]

Post by Laurent Bossavit
Geoff,

If we could just schedule good ideas to appear at certain intervals!

Or if we could just design programs so that they're always ready to
incorporate good ideas... whenever they appear !

Yep. I find that people get "tired" or something and that is what makes
them not want to incorporate changes into their code.

Code is easy to change and always has been. Coupled code is a pain, but
I am not talking about that kind of mess. I mean, I get tired even with
my good code. It's like, "Here we go again. This is boring work."

It is hard sometimes not to suggest changes to the system just to avoid
boring work.

Just a little honesty from me. No comment necessary, but comments are
welcome!

Geoff