• Home
• Courses
• Training Options
• Certification
• Contact Us
• Employment

• Business Analysis Courses
• Introduction to Business Analysis
• How to Gather and Document User Requirements
• Use Case Modelling
• Introduction to Testing for Business Analysts
• Facilitation Techniques for Requirements Development
• Logical Data Modelling
• Process Modelling Management

How to Gather and Document User Requirements

Course Duration: 4 Days (8:30am-5:00pm)

Professional Development Units (PDU): 28

Continuous Professional Development Points (CPD): 10

You'll Learn How To:

• Define the roles of the business analyst in the requirements process
• Structure a Business Requirements Document
• Effectively document a project's vision and scope Identify user classes and define their environment
• Develop a Requirements Analysis Work Plan
• Define, elicit, structure, validate and document business requirements
• Link the Business Requirements Document to a Software Requirements Specification

PMBOK® Knowledge Areas:

Project Integration Management Project Quality Management Project Scope Management Project Communications Management

Program Objectives:

Incomplete requirements are often cited as the number-one reason projects or systems fail. Accurately identifying the requirements and staying on course from the beginning is key to success in today's business world.

This "how-to" course introduces the roles of the business analyst as they relate to the analysis and documentation of requirements. It familiarises participants with core knowledge and skills required to identify and document user requirements. It also addresses how these requirements are identified and managed throughout the life cycle.

Course Outline:

1. Positioning Business Analysis The context of business analysis processes within a project life cycle PM control triangles (triple constraint) The BA role, the liaison between non-technical solution developers BA value triangle: visibility, traceability, and accountability The Business Analysis Process The themes of the BA process: Elicit, Structure, Document and Validate
2. Positioning Requirements The relationship of projects, deliverables and requirements The nature of requirements and constraints Requirements vs Specifications Types of requirements:- Regulatory requirements- Business requirements (strategic, tactical and operational)- User requirements- Functional requirements- Non-functional requirements Building a business case
3. The Key Requirements Documents The Key Documents- Project Vision & Scope Report- Requirements Work Plan (RWP)- Business Requirements Document (BRD) Other supporting documentation that should be available- Project Charter- Vendor Request Documents- Business Case- Business Contract Documents
4. Establishing Vision, Scope and Quality Vision defined at various business levels; enterprise, strategic, tactical, operational, and user Project and product scope Quality vs Grade Quality, excellence and perfection defined Cost of Quality
5. Modelling Requirements at the Business Level A Primer on Business Rules The importance of capturing the AS IS model Popular Business Level Models- Business Interaction Model- Goal Model- Business Level Workflow Model- Business Level Process Model- Organisational Model- Location Model- Event Model- System Model
6. Developing the Requirements Work Plan Requirements work plan (RWP) characteristics Requirements work plan sections Objectives and overview Deliverables Scope clarification Project stakeholders RWP resource plan User profiles Analysis phase team structure Assumptions, dependencies and constraints Risk management plans WBS: analysis phase Approvals section
7. Requirements Elicitation and Validation Techniques Diagnostic modelling fundamentals: Investigation, Diagnosis, Treatment, Prognosis Question types and user knowledge level Elicitation and Validation techniques Research the past Observation Verbal protocols Interview and questionnaire question types Focus groups Brainstorming JAD Questionnaires Structured walkthroughs Prototyping Product evaluation trials Existing models Countering the various types of bias Knowing when to stop
8. Developing the Business Requirements Document The Business Requirements Document Glossary, background, historical and prior project information Audience, user profiles, user level requirements Business-level, user-level requirements and functional and non-functional requirements Overall approach and decision making processes
9. Technical Writing Do's and Don'ts The English Language and technical writing Documentation techniques Writing guidelines Principles in documenting requirements 
10.  Modelling Business Processes The power of using graphic and text representations The value of process models Use Case diagrams Activity/swim lane workflow diagrams
11. Introduction to Managing Conflict for Business Analysts Conflict definition and sources Conflict responses and tactics Managing expectations The BA contribution to managing expectations

Course Schedule and Fees

Prices below are indicative of Public Courses Only. Discounts apply for groups and on site training. Please call ESI to discuss.