Digital Oxygen recognizes that project requirements change over time.  Older software development methodologies start out with a complete design of the system, and then proceed to build the software to match that design.  This may often lead to the customer getting the software they originally asked for, but not getting the software they really want.

We start out with an overall idea of what the software is for, and a list of high-level requirements that must be met in order to declare the project complete.

As the software is developed, our clients are sent preview versions of the software, so they can see how the project is progressing, and so they can offer feedback to help guide the development of the software.  We feel that this feedback and two-way communication is essential to guide the development toward a successful conclusion.

As they arise, new requirements are evaluated against the scope of the original project, and added to the requirements list if they fall within that scope.  In order to meet delivery deadlines and avoid "feature creep", requirements that fall outside the original scope are either logged for a future upgrade project, or the project contract is adjusted to account for the new requirements.

Internally, Digital Oxygen uses a lightweight software development methodology called "Scrum", which belongs to the Agile family of development methodologies.  We have found over time that the Scrum methodology allows us to produce high quality software while remaining adaptive to requirement changes.