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