Is there any proof that iterative development is worthwhile, or better in some qualities than the waterfall?
For example, will an agile or iterative method make my team more productive?
How do you plan an iterative project?
My customer expects a week-by-week schedule and detailed PERT chart. What should I do?
How to handle fixed-price contracts when applying an IID method?
Can IID be applied on projects or contracts (usually fixed-price) in which we are forced to do major up-front requirements analysis?
What are typical risks and mistakes when adopting an iterative process?
How to adopt an iterative, agile process within an existing waterfall process culture?
How to control costs if adaptive planning?
How do we measure quality in an iterative process?
How to coordinate subteams or subcontractors on a large IID project?
How to estimate overall effort or duration for an IID project?
How to estimate the duration of an IID project without having a plan of what will happen week by week?
If we have use cases, how to schedule them with respect to iterations?
How do we track use case requirements across iterations?
How to persuade our customers (or management) to adopt IID?
We want to apply XP, but don't have an onsite customer. What do we do?
We think we are applying XP, but use fairly detailed written specifications for the iteration rather than an onsite customer. Is that OK?
What's going to happen with our existing test and QA department if we adopt an IID method?
Can a project fail with an IID method?
What new skills are needed for managers and developers?
How to deal with change management in an IID method?
Is IID useful for commercial products?
We have to tell the customer what they will get and what it costs before starting to build it. Therefore we can't work iteratively, true?
We can't make a solid architecture if we do not know all the requirements up front, true?
Rework (or refactoring) each iteration sounds expensive. Isn't it cheaper to design it correctly up front?
What use are iterations for short projects of, say, three months duration?
How can we get our management to realize they don't need a final, detailed plan on "day one"?
Our test environment is very complex and run by another organization. How can we iterate and test?
What do we do when time, budget, and scope are all frozen but we still want to apply an iterative or agile method?
Doesn't iterative development mean that we don't know when we're finished?
Should I plan the work for all the future iterations to ensure the scope and resources (e.g., people) fit the desired end date?
How do I get feedback when there is little or no user interface?
Should iteration activities overlap? For example, requirements for the next while testing for the previous?
How long should iterations be?
How to handle the design of a database with an iterative process?
Should the customer always be in charge of what gets built each iteration?
How to plan an iteration?
Do I give the results of every iteration to my customer?
How to do documentation for maintenance, when we want to be agile?
How can I create a work breakdown structure (WBS) without a weekly schedule, or an iteration-by-iteration schedule?