Module 9 (30 points) - Chapter 10 1. (Whitman & Mattord, 2016, p. 543) What is a project plan? Why is a security related project plan often far more complicated than other plans? It is a formal document that identifies, priorities, assigns task, and guides the project. It's a document that lays out all the company's goals, deadlines, items needed, to accomplish your goal. It is a lot more detailed and is normally handed off or delegated to cross-functional teams. This needs to be more detailed as to what is needed to be done and what time frame, especially with multiple departments having their hand in the cookie jar. 2. (Whitman & Mattord, 2016, p. 543) What categories of constraints to project plan implementation are noted in the chapter? Give an example. Why does the scope of a security project need to be maintained? 3. (Whitman & Mattord, 2016, p. 543) List and describe the three major steps in executing the project plan. Name an organization that has helpful security project planning information. 4. (Whitman & Mattord, 2016, p. 543) Why is it a good practice to name specific individuals as resources early in the planning process? Why is it a good practice to assign start and end dates in the early stages of project planning? 6. (Whitman & Mattord, 2016, p. 543) List and describe the four basic conversion strategies (as described in the chapter) that are used when converting to a new system. Under which circumstances is each of these the best approach? What are possible