In the software develop world, there are plenty of models -- and graphical representations -- to help organizations and individuals understand and analyze the development process. The most familiar, the classic waterfall model, is still used to describe the often linear path that a development process takes.

However, the spiral model became a popular alternative, as it more accurately captured the needed concept of a multi-step, iterative process, in which previous steps impacted future steps, particularly in cases of poor code quality and the mismatch between initial requirements and the current functionality of an app.

Other models, without such iconic representations, have been embraced by various people in the software development field. The most prominent is the agile programming method, which lacks a core graphic to illustrate its features.

The wicket

In the course of working with development organizations, New Rowley felt existing models, while still relevant and foundational to the topic, failed to capture some critical aspects of modern development processes. In response, we created the "wicket" model. The visual representation of the model is designed to convey the impact of development for both IT as well as business executives. Highlights include:

• A multi-phase process that embraces deign, coding, testing, and deployment.
  
  
• Since most development is based on extending, re-factoring, or otherwise modifying existing code, the wicket model emphasizes the increasing code base.
  
  
• The wicket itself lives on top of an established and deployed application, demonstrating how enhancements must be developed and tested while the previous version of the app is running.
  
  
• The wicket varies in width, a representation of how development projects can very in their size and complexity, and thus the time required to design, code, test, and deploy the resulting software.

We don't expect the wicket model to replace the previous, well-established models. For example, it leaves out the iterative nature of a development project that the spiral model emphasizes. However, we do encourage developers and IT managers to utilize the wicket model, particularly when a visual concept of a development effort is needed to help non-technical business managers understand a project's scope. 

Note: Any thoughts or comments on how to improve the value of the wicket model are welcome.