Elements of my team and myself are experiencing some difficulty performing design meetings. The symptoms are:
- We get off track easily, a combination of low understanding of the content of the system and want for the solution to be your solution drives the conversation often.
- We are unable to come to an acceptable conclusion. Often the developers and the system architect have issues due to the involvement of the architect in the low level design.
- In-ability to stick to a top-down approach, often going into depth of components before the high level design is completed. I believe this is due to a significant difference of design thinking by the members of the meeting.
I believe the solution to these problems is in better understanding of a design approach. What i am interested in is:
- Suggestions for improvements, but more so
- A good way to conduct software design meetings between the implementers and the software architect, from literature that can be read by all.
- A technique or guide how to best approach design (not architecture, but the steps between High level design and class diagrams), so that the developers and architect can take a common approach to design. Ideally a quote from readable distributable reputable literature is ideal, again so it can be read and agreed by all.