Incomplete requirements are often cited as the number one reason projects or systems fail. Accurately identifying requirements and staying on course from the beginning is therefore key to success in today’s business world.
This “how-to” course introduces the role of the business analyst as it relates to the elicitation, analysis and documentation of requirements. It familiarises participants with the core knowledge and skills required to identify and document user requirements. It also addresses how these requirements are managed throughout the lifecycle.
Recommendation: The material presented in this course provides the detail needed to begin eliciting and documenting requirements. Those wishing to take additional courses in the Business Analysis Professional Development Programme will need this foundation.
This course is aligned with version 2.0 of A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)™.
- Explain the critical role of the business analyst with respect to requirements elicitation and project management
- Develop and validate a solution vision and scope
- Use appropriate modelling techniques
- Planning the requirements elicitation and analysis to maximise efficiency and estimate the required effort
- Determine the most appropriate technique for eliciting requirements at different points in the analysis cycle
- Analyse various kinds of requirements into a complete, coherent and organised requirements document
- Build consensus to validate and finalise the requirements in the business requirements document
Creating a Requirements Work Plan
The value of planning
Elements of a requirements work plan
Planning the analysis Identifying business analysis tasks
Stakeholder identification and prioritisation
User identification and profiling
The purpose of documenting requirements
Elements of a Business Requirements Document
Technical writing guidelines
The role of modelling in requirements documentation
Use case and activity diagrams
Dealing with barrier to elicitation
Advantages and challenges of elicitation techniques
Introduction to Modeling
Documenting and tracking business rules
Why use models?
Effective consensus building
Decision making and approvals
Managing change and risk post-validation
What happens next?
Roles, Definitions and Key Principles
Critical role of business analyst
Creating and adopting a formal documentation strategy
Key requirements documents
Roles and mutual expectations among team members
Types of Requirements
Attributed and types of effective requirements
What is an effective requirement?
Vision Scope and Quality
Defining problem, vision, and scope
Importance of a solution’s scope statement
Documenting project vision and scope Including quality measures