How many times have you heard “we missed this target, but hopefully we’ll make that up later on.” — likely in the QA phase.

The other issue I have with these charts is that they try to immediately break things down into the task level, which isn’t ideal.

I’d rather coordinate dependencies and priorities with FEATURES — something that the client will care about — and in that regard we can deliver software in many small (yet complete) chunks.

Good write up!

Yes, Iterations are timeboxed, but what can fit in those iterations is the bigger question…

Not to bleed into Friday’s post, but one of the many questions we have to change is not how much something will cost, but having this budget and timeline what do you think can be done and what is the probability?

I will expand more later this week… ;)

1. Iterations can be timeboxed, therefore they can be represented on a bar chart

2. If we can’t produce software in an agreed timeframe with agreed features, how do we set expectations on the ‘cost’ of the project?*

*Without a cost, they don’t know where to invest their money because they don’t know how much of it they will need. TurboTaxOnline.com costs me about $150 a year. I find that to be a great value. However if they told me who knows the cost we’ll just charge you I’d opt out of using the website.

James