We create software by working inwards from the user experience. Maintaining focus on the users’ perception of the system, we do just enough to satisfy the needs of the user rather than what we think is necessary or cool. On a regular basis, we come up for air to check context and avoid getting lost in the weeds. We decide which direction to go next based on where our client sees value and consider how we’re going to demonstrate what we’ve created so far. We don’t jump into unit land because trying to connect all the pieces at the end doesn’t produce a good solution.
AGILE IN ACTION
Search Posts
-
This work is licensed under a Creative Commons Licence
Recent Posts
- Organization complexity is a waste farm
- Managing costs provides a false sense of security
- State of Agile survey for 2011 tells a familiar story
- (I can't get no) satisfaction, let alone customer delight
- Positive emotions and purpose
- People don't buy what you do, they buy why you do it
- Too busy chopping wood to sharpen the axe
- So you want a fresh apple
- Systems are seductive
- Crack cocaine problem-solving and complexity
Archives
- ► 2012 (5)
- ► 2011 (24)
- ► 2010 (31)
- ▼ 2009 (41)
- ► 2008 (69)
- ► 2007 (152)
- ► 2006 (128)
- ► 2005 (63)
- ► 2004 (2)

1 Comment
I've recently been doing what I hope is a successful project inception (that's going to lead to a bid for the project) by trying to keep an eagle-eyed focus on the user experience.
I feel it worked very well, and certainly the prospective client was happy (it also helped that he was willing to put in the time and effort needed).
How do you feel such an approach tallies with domain driven design? I ask because I've heard some comments on teh interwebz saying that UCD and DDD are at odds, and was interested in your opinion.
Cheers,
Simon