The rationale for the application board

The application board is the green-marked area

Based on the business domain rationale, we understand that the pillar contains all the necessary information to create the correct product. However, the business domain may seem disorganized and chaotic to a software development team. That’s where the application board comes into play. It functions as a “translation” of the business domain, representing the product in logical blocks. It goes by different names depending on the methodology used, such as the vision board in Agile or Product Breakdown Structure in Waterfall, V-Model, and others.

But, the business domain may also look a bit unstructured and unorganized in the eyes of a software development team.

The application board is the ‘translation’ of the business domain into a representation of the product in logical blocks. It is referred to as a vision board (Agile), or PBS, Product breakdown structure (waterfall, V-model, etc.)

Although it is the representation of the complete product, it also indicates the growth path (see Roadmap – Rationale) of the product and also will be used as a test basis to determine the scope of testing (see Testing Board – Rationale).

The application board not only visualizes the product under construction but also is the glue between all pillars in Bona Iqiniso, showing dependencies between functionality, when they are delivered, and what their quality is.