Update the iteration plan. Next, start with the use cases in the revised first iteration and list out the scenarios in the first use case. Explain what a use case and scenario is for those who may be new or vaguely familiar with them. Go over each scenario one by one. As you go through the scenarios, you ll notice the project team coming alive as the visually intuitive nature of sequence diagrams starts to slowly warm the team members brains with ideas about the business processes behind the use cases and scenarios.
Adrenaline starts pumping.
Remember to keep them from speaking MouseClick-ese. Suddenly, team members feel productive. With each additional meeting, morale picks up. Keep a journal of the use cases and scenarios that cause the most heated and passionate debates. These are typically going to be the riskiest, most complex areas of your domain and code.