Determining Business Requirements

At the right time, in the right way, from the right people

We all do projects as team members, managers, users, support groups, or project managers. Most of these projects are cross-functional and/or cross-business, spanning multiple departments, groups, and borders within an organization. 

This program is for anyone who participates in or leads teams that develop and write business requirements. Participants learn how to create the new wave of business requirements documents. The latest thinking is to get to market ASAP, so there has been another revolution in requirements creation.  For many projects, it is no longer acceptable to have extensive requirements documentation. The major trends are to reduce text documentation and use models targeted at specific stakeholders, as the saying goes, “a picture is worth a thousand words.” Communication should be efficient and effective for each stakeholder. These deliverables identify what the project will do (and for whom) and what it will not do (i.e., in-scope and out-of-scope). The business sponsors also need this information to decide whether or not the project should proceed to the next step, Functional Specifications.

The workshop is endorsed by PMI® (Project Management Institute) to help participants become better Business Analysts and, if they choose, prepare for the PMI-PBA Professional in Business Analysis credential. Upon completion, attendees involved with PMI’s Project Management Professional – PMP and/or PBA programs are awarded 8 PDUs or “Contact hours”. Our Global REP code is 1270. The workshop also complies with the IIBA® and its BABOK® (Business Analysis Body of Knowledge).  

 

Who should attend?

This program is designed for individuals who are currently or will soon be the development of requirements for projects. 

• Business analysts
• Project managers
• Developers and technical professionals
• Subject matter experts

 

What you will learn.

After completing this course, you will be able to:

• Understand the concepts of Business Case, Enterprise Analysis, and Business Requirements, and place them within the Project Life Cycle (AGILE and Waterfall)
• Use the PMI-PBASM Handbook as a job aide when fulfilling the business analysis role
• Apply a framework and toolkit for producing Business Requirements for new and/or improved products, services, and processes;
• Identify the potential stakeholders and roles needed within the business project environment 
• Work with sponsors to develop the Project’s Mission, Scope, and Charter;
• Understand and apply several tools for creating Business Requirements, e.g., Elicitation Methods, Cross-functional Process Mapping, Fish-bone (Ishikawa, Cause and Effect Diagrams), MuSCoW Analysis, Cost Benefit Analysis, Pareto Analysis, ROI, etc.;
• Use tools to capture and analyze the “current-state” (as-is), identify potential problem and opportunity areas, identify disconnects, and perform gap analysis to develop the business requirements of potential “end-states” (“to-be” states);
• Write Business Requirement Statements that are meaningful, effective, and reflect the needs.
• Understand and address the impact of change on the people, and how this affects the business requirements process.