1. What are the one or two most challenging issues in identifying and documenting IT acquisition requirements (i.e., the requirements for solving the problem that was defined)? Explain your reason(s) and how the issue(s) can be successfully addressed.

2. Should it be permitted to add, delete, and change requirements after they have been approved up to the time a contract has been signed with a service provider? Should it even be possible to add, delete, and change requirements during the subsequent project?

3. The development of a work breakdown structure can be challenging. It requires a good understanding of the problem and a good understanding of the proposed solution. The proposed solution must be "broken down" into its major parts, each of which may be further broken down. Comment on your experience in developing a work breakdown structure for your individual project. What was easy? What was difficult? What problems did you encounter and how did you solve them?