Ken Orr wrote ( in Cutter IT Journal Vol.3, No. 7 ):

Agile . since Jun 23 . Index . DOCs TOP TOC

Metaphor


Every project should have a single, overarching concept or metaphor. Metaphor is intended to replace the term architecture within a project and provide it coherence. According to Beck, "As development proceeds, and the metaphor matures, the whole team will find new inspiration from examining the metaphor" [1].

Of all the components, the metaphor is perhaps the most difficult one to grasp. At some level, it is supposed to be the essence or the irreducible core of whatever it is your project is building. When done right, it makes it possible for team members to keep focused. We'll discuss more about metaphors later in this report.

Agile . since Jun 23 . Index . DOCs TOP TOC

Simple Design


From Beck's standpoint, "The right design for software at any given time is one that:

§      Runs all the tests.

§      Has no duplicated logic. Be wary of hidden duplication like parallel class hierarchies.

§      States every intention important to the programmers.

§      Has the fewest possible classes and methods." [1]

As you might imagine, "simple" has lots of meanings to lots of people, and I can imagine a number of scenarios where Beck's definition of simple might not turn out to be so simple after all.

Agile . Index . DOCs . TOC