1. You are managing a project that was postponed twice because its funding was diverted to higher-priority projects. The system owners do not want that to happen again, so they are very anxious to get the new system started and built as quickly as possible. They are putting a great deal of pressure on you to spend no more than a couple of days on requirements discovery. If anything is missed, they tell you, it can be fixed later on. You really want to make them happy, but a little voice of caution is going off. What are the potential consequences and costs of rushing through the requirements discovery process?

2. System developers use fact-finding techniques in every project phase. Is fact-finding more important during the requirements analysis phase than for other phases? Why or why not?

3. What is the deliverable that is created once requirements analysis is completed? Why is this deliverable needed, and what does it include? Who are the audience and/or users of this deliverable, and for what reasons?