> May I ask what could possibly take 12 weeks worth of work before having anything useful? 12 person weeks is a tiny amount of effort. > but in the first spri

> May I ask what could possibly take 12 weeks worth of work before having anything useful? 12 person weeks is a tiny amount of effort. > but in the first sprint you can release the component to tokenize strings, for example. Ah I see - You just have to redefine what useful means :P. If your customer needs a search engine then having a string tokenizer is not useful at all. You don't run a project this way to improve individual developer productivity. You run it this way to reduce infrastructure and project risk. Often using Scrum practices is a good tradeoff - the problem is the messaging. The truth is we are trading off developer productivity and growth in order to lower overall risk and make the software process more predictable.