Episode 132: Top 10 Architecture Mistakes with Eoin Woods

Scoping

Scoping in software architecture is a delicate balance between being too broad or too narrow, often influenced by various stakeholders. Eoin Woods highlights that understanding who the decision-makers are and involving them early is crucial to avoid scope issues. He explains, "Scope is just tough to get right. But the key thing really is making sure that you understand who the decision makers and the important people are who have a say in scope and who will be affected by scope and get them on board early" 1. This involvement helps in managing expectations and making informed decisions about what to include or exclude in a project 2.

   

Stakeholders

Engaging stakeholders early, especially those from compliance and audit groups, is essential to avoid last-minute surprises. Woods notes that these groups often remain passive until it's too late, emphasizing the need for proactive communication 3. He suggests using architectural views tailored to different stakeholders to ensure clarity and understanding. On non-functional requirements, Woods advises learning from past systems and using scenario-based approaches to clarify these needs:

You can do a similar thing much less formally with a few sentences to kind of illustrate to somebody what a particular quality requirement is going to imply for them.

--- Eoin Woods

This method helps stakeholders grasp the implications of their requirements, ensuring they are realistic and achievable 4.

   

Non-Functional

Non-functional requirements often pose challenges due to their abstract nature and the difficulty in quantifying them. Woods explains that stakeholders may sign off on precise requirements without fully understanding their implications, leading to issues later on 5. He shares that using scenario-based discussions can uncover hidden quality requirements and provoke necessary stakeholder reactions.

Right. We've uncovered a quality requirement. Thank you.

--- Eoin Woods

This approach not only clarifies expectations but also highlights potential areas of concern, such as security and system evolution, which are often overlooked 5.