Collaboration joins stakeholders and software teams in performing design work together. It creates shared understanding of user needs and architecture, replacing isolated hand-offs that encourage assumptions, incomplete requirements, and quick fixes. section 1.2
BigScreen’s hand-off problem
At BigScreen, the product owner alone gathered requirements, translated them into implementation-focused user stories, and handed them to developers. Direct collaboration was missing, so features were often incomplete or incorrectly implemented. The situation also exposed why collaboration matters more in software than in construction: users reveal new insights only after interacting with an unfamiliar solution. section 1.2 section 1.2.4
Use collaboration as an intentional facilitation practice:
- Discuss how power rankings may affect participation and outcomes before a session. section 6.4
- If completeness matters, invite lower-ranked participants to speak before highly ranked participants. section 6.4
- Open discussion with a continuum question such as whether ranking affects the team, from “not at all” to “absolutely.” section 6.4
Figure 1.4 Detailed diagram of the Waterfall process
Use the process diagram to contrast sequential requirement hand-offs with collaborative software design. section 1.2.4
