While we adhere to the DSDM approach, we were developing systems long before DSDM was thought of, so we have our own compliant methodology, which we call Modular Prototyping.

This evolved from the frustrations of trying to use approaches such as SSADM and Method One within a RAD environment. We adopted some elements of the waterfall methods, learned a lot from James Martin’s RAD techniques, the Prism Methodologies (particularly the Enhancement and Maintenance method) and delved into texts such as Avison’s and Fitzgerald’s. We have taken elements from all these sources and new methods, such as Extreme Programming.

Why do we maintain our own methods when there are recognized alternatives in circulation? Put simply, we don’t believe that any one methodology has all the answers. We provide a more comprehensive explanation of our reasoning on the Modular Prototyping page.

You can find out more about some of the methodologies, but following the links to the right, or looking at our introductions to DSDM, eXtreme Programming and the Agile Alliance.

[Agile Approach]
[Agile Methods]
[DSDM]
[eXtreme Programming]
[Agile Alliance]
[Why Modular Prototyping?]
[Modular Protyping in Practice]
[Contact Us]
[About Us]
[Legal]