Deal support Document List 3

You can use a the Concept of Operations document (CONOPs) to describe the purpose of a proposed system, the environment in which it will be operated, how it will be used, roles and responsibilities of users, resources required for its implementation, and other information project stakeholders will need to fund the proposed system.

You can use an Capacity Plan document to capture the IT resources required to support the functionality and performance requirements of your IT systems when operating at full capacity. The Capacity Plan helps gauge the most cost effective way of provisioning resources and services by aligning them to your organization’s demands.

You can use a Needs Statement document to describe a business need or a deficiency in your organization, justify the exploration of an alternative solutions to resolve this need, and then provide estimated costs for these actions.

You can use a Scope Management Plan Document to create Scope of Work documents to help you to start planning your next project. They define all processes and work required to complete your project, including justification, work products, deliverables, objectives, assumptions, and limitations.

You can use a System Boundary Document to establish the boundaries of an information technology (IT) project. The System Boundary Document captures the goals and objectives that the IT project is intended to satisfy. It also captures critical success factors and performance measures that provide the criteria to judge whether the deliverables have satisfied the business’ goals and objectives.

You can use a Statement of Work to describe the deliverables or services required to fulfill a contract.

You can use a Risk Management Plan to identify, evaluate and prioritize risks during the software development lifecycle.

You can use a Feasibility Study document to perform a preliminary study to determine a project’s viability, analyze the problem and then determine if it can be solved effectively. The results determine whether the solution should be implemented or not by helping you write the Problem Statement, Business Environment, Business Problem, Requirements Statement, Business Drivers, Feasibility Assessment, Feasibility Ranking, Ranking Criteria, Ranking Scores, Proposed System, Cost Analysis, and Recommendations. This activity takes place during the Project Initiation phase in the software development lifecycle and is created before significant expenses are engaged.

You can use a Cost Benefit Analysis document to analyze, evaluate, and cost potential solutions to meet your organization’s needs. You can use this to present the costs for the design, development, installation, operation, maintenance, and disposal of the proposed system over its projected lifetime and identify the approach for the development of the system as determined in the Feasibility Study.

You can use a Concept Proposal Document to identify the need or opportunity to improve a business function by highlighting where strategic goals are not being met or performance can be improved. The Concept Proposal should demonstrate that this is a worthwhile investment and identify potential impacts on systems, staff, and operations.

You can use an Change Management Plan document to address changes which may be encountered during the project lifecycle. Typical areas of change occur in the scope, schedule, budget, and resources.

You can use a Business Rule document to define specific aspects of your business. Business rules clarify the appropriate action that needs to be taken and removes any ambiguity regarding the correct course of action that must be followed. Business rules describe how company policies or practices apply to a specific business activity. As you model your business processes, you can capture business rules as separate elements and weave them into your process flows.

You can use a Business Case document to outline the Business Need, Current Process, Services, Expected Benefits, Change Analysis, Cost estimate, Cost/Benefit Analysis, and Project Schedule.