Development Style

iWasteNot Systems' preferred model for development resembles the Agile Development style.  We commonly refer to our model as Adaptive, Non-linear, or Evolutionary Development.

We try to closely tie software development to 'Real World' goals or problems to be solved.  Work is broken down into the smallest chunks possible, with the caveat that each chunk must contain at least the minimum functionality required to meet a goal or solve a problem for an end-user.

Each chunk is moved through a similar process to the usual during the all-in-one-go (Waterfall) development style which is more conventional.  Needs assessment, scenario modeling, planning, design, coding, testing and release are all performed for each chunk of function at the time that it is developed and deployed.

It is expected that each chunk of work will take no longer than one month to complete, with some taking at most, a week.

The system thus grows organically from base functionality toward optimal in discrete functional units.

Pre-Planning Stages:

Step 1 - Establish Primary System Goals
Step 2 - Engage in Scenario Modeling to establish the expected use-patterns for the proposed system.
Step 3 - Create a System and Information Architecture which supports the expected use-patterns.

Implementation Stages (broken into small modular units which have all the required elements to support a specific chunk of functionality):

Step 1 - Establish Real World Goal or problem to solve.
Step 2 - Engage in Scenario Modeling to establish the expected use-patterns for the proposed functional unit.
Step 3 - Initial implementation of functional unit.
Step 4 - Refinement based on feedback and assessment of achievement.
Step 5 - Repeat steps 1 through 4 until satisfactory results are achieved.
Step 6 - Repeat Steps 1 through 5 as necessary to achieve a total system to support the Primary System Goals.

Linear vs. Adaptive development style