Big web projects are like elephants. You need to eat both one bite at a time.

Making the deadline for a large web project can be hard. If the deadline is missed so are expectations. For a large project to be successful, you need an approach that is more flexible and feasible.

Many times the best approach is to break a large project into smaller parts. These smaller parts can be launched in succession as phases. Each phase is its own small project with features and requirements. When phases are launched they are fully functioning. And, since phases are launched over time, you can start to measure results sooner.

The biggest benefit to working in phases is that your project is more likely to be feature complete on time.

As with any project, phased projects must be planned out. The first step is to consider the minimum needs to launch, often called the minimum viable product (MVP). Once the foundation is set, the following phases are mapped out based on what is most important and most urgent. Items that are not both important and urgent can be moved to later phases or left alone.

Phased projects require discipline. You need understand what is most important and what is not. Keep in mind that saying “Yes” to one thing is also saying “No” to something else. Keep priorities in check and remember to keep “ready” “aim” “fire” in order.