Model Storming

Correct Answer: When the team reaches diminishing returns in generating new insights

Model Storming is meant to be a lightweight, informal modeling activity that helps teams explore and understand specific aspects of their work. The key indicator for concluding the session is when the team starts experiencing diminishing returns in generating new insights. This is the optimal stopping point because: - It indicates the session has served its primary purpose - The team has extracted the main value from the exercise - Continuing beyond this point would be inefficient The other options are incorrect because: - Documenting every possible scenario is too exhaustive and goes against the lightweight nature of Model Storming - Using the full allocated time slot is not a meaningful indicator - sessions can be shorter if objectives are met - Achieving complete consensus on all aspects is unrealistic and unnecessary for Model Storming, which is meant to be a quick, collaborative exploration exercise rather than a comprehensive modeling session

Correct Answer: Through Model Storming, the team can brainstorm and sketch different database designs, discussing pros and cons until a consensus is reached.

In the given question, the best approach to assisting the dev team in their database design for the complex project would be through Model Storming. This answer correctly states that the team can brainstorm during Model Storming sessions to sketch varied database designs, evaluating the pros and cons of each, until they reach a consensus on the most effective design. This practice is widely adopted as it allows not only for a team-wide understanding and agreement, but also allows room for creative and different solutions to be brought forward. The other answers are incorrect for the following reasons: Hiring a separate database team or letting the scrum master choose the design contradicts the principle of self-organizing and cross-functional teams in agile. They're responsible for organising work and coming up with a solution, not depending on an external team or a single individual. Lastly, stating that the database doesn't matter because it can be changed anytime is also incorrect. It neglects the fact that changes in design after implementation can be costly and time-consuming. Therefore, it is crucial to get the design as correct as possible in the beginning to avoid redundant effort.

Correct Answer: Create parallel sketches exploring both aspects and merge common beneficial elements

Creating parallel sketches that explore both performance and user experience aspects is the most effective approach because: 1. It acknowledges all stakeholder concerns equally and maintains collaborative spirit 2. It allows for visual representation of trade-offs and dependencies 3. It enables the team to identify synergies and common ground 4. It keeps all stakeholders engaged in the process 5. It promotes creative problem-solving through visual thinking The other approaches are less effective because: Scheduling separate sessions fragments the discussion and delays resolution, potentially creating silos. Applying weighted scoring prematurely reduces complex trade-offs to numbers and may overlook important nuances. Focusing primarily on system architecture diagrams emphasizes technical aspects too heavily and may not adequately address user experience concerns in an integrated way.