Research Hypotheses

In our effort to implement XP on this large project, we proceeded on the following assumptions.

1. The story cards and the resulting code that developed as part of the iterative, XP process would be a sufficient guide for everyone on the team to understand the whole application.

2. Dividing application functionality into story cards that would fit into our iterative plan could be learned once and then reapplied for all subsequent iterations.

3. We would be able to identify easily the single customer who would drive the planning game for this XP process.

4. The customer we identified would be able to drive the planning game and be the primary author of all functional tests developed to verify completion of new functionality.

Each of these assumptions or hypotheses is grounded in one or more of the core XP practices, so we felt confident that we could make these assumptions as part of our switch to this new methodology.