Agile Hokkaido

Agile Hokkaido adheres to a conceptual framework for software and system engineering that promotes development iterations throughout the life-cycle of a project. We consider ongoing changes to requirements as a natural, inescapable, and desirable aspect of systems development projects. In other words, adaptability to changing requirements at any point during the project life is a more realistic approach than attempting to define all requirements at the beginning of a project and then expending effort to control changes to the requirements.

At the conclusion of each iteration the Agile Hokkaido team lead who is managing the system's development visits the client to report on the progress made during the previous month, to familiarize the client's staff and management with the newest release of their software, and to review and gather requirements in order to prioritize the work for the next month.

Iteration

The length of an iteration at Agile Hokkaido is one month. Each iteration is one complete software development cycle including gathering of requirements, coding, testing, and implementation. A new release of fully functional software is provided at the end of each iteration.

Project Velocity

Velocity is a measure of how much progress has been made over previous iterations and is used to predict how much can be accomplished over the next iteration. It is possible to increase the velocity at anytime by increasing the resources committed to the project.