Defining an IT project's requirements is one of the most important steps in developing the project scope. A major consequence of not defining requirements well is rework, which can consume up to half of project costs, especially for software development projects. Everyone can cite examples in all types of industries of how important it is to understand requirements as early as possible. For example, if the project team is designing a house, it is much cheaper to decide where windows and walls will be on paper or a computer screen than after the entire house is framed. New processes and technologies are making it easier to define and implement requirements, but it is still one of the most challenging aspects of developing the project scope. Within your team, continue to define the IT project by adding to your project proposal. This portion of the project proposal must be 750-1,000 words, defining the scope and schedule of the chosen IT project and addressing the following components: Use 2-3 research techniques to describe how the collection and documentation of stakeholder requirements leads to the content of the IT project scope. Cite your sources. Explain how the IT project schedule is derived from