Cut features

At this point, we usually have a large list of features for the application. Neither time nor money are infinite, so choices get made.

Prioritize

Typically we score our features on a matrix of business necessity on one axis and difficulty on another. A task with a difficulty of 5 and a business necessity of 1 is ripe for cutting. A task with a difficulty of 1 and a business necessity of 3 isn't important, but it is so easy that we might as well do it.

Together we determine which features should be included in the initial release of the application, and which should be included in phase two or beyond. These decisions can be based on time restrictions, budget limitations, and the need for user feedback. Now we have a schedule and a plan for development.

Architecture

Here we determine the broad architectural choices. Is this a website? Is it a website with a desktop app for administration? Where does the data live? How do we authenticate users? etc.

Next: Development