Project Models


There are many project models for Web site development, which one to use often depends on the implementing partners or the end customer and their preferences. Experience says that it is nearly impossible to predict every problem that may arise in a complex project. Therefore it is wise to use an iterative and flexible approach. The project model you choose is of less importance, as long as it supports incremental step-by-step development.


Project Process

The project process, regardless of size and project methodology, includes a number of steps. Often the project starts with the sales phase, where the solution is visualized, ends with the project close-down and handover to the support and maintenance organization.


The Step-by-Step Approach

To land a large project successfully, taking small steps at a time when creating the deliverables is extremely important. As far as possible, divide the project into smaller functioning deliverables or ”milestones” along the way. Try to ”isolate” functions so that they can be developed separately.Start system integration early. Add one part at the time to the site, then test, and modify and repeat the procedure until ”good enough” satisfaction is reached. At this point, focus on the solution performance, ”beauty flaws” can be repaired later. And – be sure to regularly involve the end-users, the steering group or any third-part of importance in this process to set the right expectations from start.This may sound obvious, but emphasizing a working solution from the beginning helps you avoid unexpected and time consuming surprises at the end, and gives the project a better chance to deliver in time.


Project Methods

Scrum

Scrum is a highly iterative method where small teams work in sprints. Each sprint lasts for a certain time, and contains a specified number of functioning deliverables that are presented at the end of each sprint. Scrum can be seen as an incremental framework for managing complex work commonly used with agile software development.


RUP (Rational Unified Process)

RUP for software design is a product as well as a process. RUP is a framework for object oriented software design, with visual modeling of use cases, class models and object interactions. RUP can also be viewed as a disciplined approach to requirements and change management in complex projects.


GANTT Chart Model

With the GANTT method, the project is divided into smaller sub-projects with deliveries related to checkpoints called milestones. GANTT provides a graphic schedule for the planning and controlling of work, and recording progress towards stages of a project.

Ask a question