I have always problems explaining people what our company does. Not because I don’t know what it does, but because other people isn’t knowledgeable enough to understand the concept. If I say “eBusiness” – people don’t know the term. If I say “business process optimisation” – they think we aren’t IT company. If I say “we do web development”, they usually reply “ah, web design”. Wrong! (Of course we do web design too, but it’s not our main business…)

So I met my mentor last week and he told me that people do not care how I call it – websites are still websites. They want their project done and they don’t care how we build it. And he asked question which made me think – “Which comes first design or development?”.  By logic and all the good concepts I and probably most of you would reply “design”. But is it true in agile development?

I searched a bit over the net and found one really good article about it. And now what I think is that in agile development pilot project comes first. Pilot project is proof of concept that developed idea can work. You can argue that it should have some design anyway, but it’s just something to get ideas from for the finalised design.

Agile development is test-driven. You write tests first and only then code and then design. Have I proved my point? Any ideas about this?