InfoQ

News

Adopting Simple Design

Posted by Amr Elssamadisy on May 13, 2008 07:51 AM

Community
Agile
Topics
Object Oriented Design,
Design
Tags
Adoption

Kim Gräsman asked a simple but thought-provoking question to the extremeprogramming Yahoo! group:

Hello all,
It seems incremental design has become a theme (if implicit) on the
list these past weeks -- does anyone have good references to reading
on incremental design?

Good question.  There were some good recommendations made.  Here are some of them:

The question then morphed into a discussion about adopting incremental design:

I'm just thinking about this in the abstract, I don't have an actual
question really, but it seems to me getting a team started with
incremental design can be difficult, and I've talked to people who
have tried without much success. So I think I'm trying to better
understand the practice before misguidedly attempting to use it.

To answer the question about how to adopt incremental design well, the age-old question of what IS good design reared it's head.  This, of course, resulted in advice that was all over the map.  One interesting point of view was presented by Ron Jeffries:

I believe that by most people's lights, a "good design"
automatically turns out to be evolvable. IOW, faced with a design
that is thought to be good, but not evolvable, we can quickly come
up with a design which is similar in essence, "better", and
evolvable. The making it "better" will make it more evolvable
without working directly toward that property.

But, one notable gap in the discussion was that the "how do I adopt incremental design?" was never directly addressed even though that seemed to be the main topic for a large part of the discussion.  The group came at the issue from different angles but never directly.  Is it difficult for us to discuss adoption?  Or is it so obvious that we don't need to address it directly?

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Reply

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.