Wednesday, June 22, 2016

On X-Projects

On X-projects:

"The typical X project focused on a needed technology. Although the technique is applicable to many areas of technology, I'll stay with aerospace for the moment. One designs the best ship possible given existing technology. There are to be few to no stretches or reaches: we are not looking for new technology, we are looking to see what the best we have can do – and thereby identify what's needed next.

"The ship is built. Typically there will be three vehicles (tail numbers in the jargon). The first is flown to find out its capabilities. Then those limits are tested, and tested again. Frequently tail number One is destroyed in the test process, although that's not inevitable. Using what was learned from One, Two is modified and flown to its limits, and kept flying until there is no more to learn. Number Three makes a few token flights and goes to the Smithsonian."

It works in software too. "Build one to throw away." This is why the planning phase between sprints is important.


If I esteem mankind to be in error, shall I bear them down? No. I will lift them up, and in their own way too, if I cannot persuade them my way is better; and I will not seek to compel any man to believe as I do, only by the force of reasoning, for truth will cut its own way.

I could not love thee, dear, so much,
Loved I not Honor more.

No comments: