Determining Business Requirements requires eliciting, analyzing, specifying, prioritizing, verifying and negotiating business functions that the product must deliver and support. The results are captured in a Requirements Analysis deliverable; a Requirements Analysis template is available on the EPM website. During this process it is important to have all of the Stakeholders involved. Since this is the process in which all business and processing requirements are determined and agreed to, it is critical that all parties understand the ramifications of including or excluding requirements from scope. This is an opportunity to work out business process issues as a group, in order to reach optimal performance and efficiency within an organization or even across organizations or functional areas. Decisions made will impact the project and/or its product, so all parties involved should be heard, and all areas of concern or question should be 1
Project Manager Project Sponsor Business Analyst Facilitator Subject Matter Experts Data/Process Modeler Technical Lead/Architect Technical Services Information Security Officer Technical Support Customer Decision-Maker Customer Representative Stakeholders
Roles for this Step
thoroughly addressed. Reaching consensus and agreement on the final requirements will help to ensure that everyone gets the product to which they agreed. TIP: Don’t hesitate to use one of the commercially available tools to assist the Project Team in their documentation efforts. Through use of these tools, changes made to a process are automatically carried through to all other associated processes or business rules. Requirements fall into multiple categories that, while related, are themselves separate and distinct. These categories are: Figure 1 Category Functional Requirements Technical Requirements Operational Requirements Transitional Requirements Description Requirements that define those features of the product that will specifically...