Chapter #01 | Chapter #02 | Chapter #05
The need for collaborative design
Great technical teams working closely with well-meaning business stakeholders can still deliver software that fails to meet an organization’s needs. We see it every day. Software teams become too focused on finding solutions without fully appreciating the context of the organization. Business stakeholders can be reluctant to voice their concerns in technical sessions. Tensions escalate, and conflicts go unresolved.
Effective software requires effective collaboration, and just like every other aspect of software development and design, collaboration is a skill you have to learn and practice. Collaborative modeling can be a key strategy in doing so since it can clarify assumptions and foster improved collaboration between development teams and stakeholders. Read more in Chapter 1 of our book to understand the need for collaborative software design better.