How to Gather and Document User Requirements
Master analysing and documenting requirements, to fulfil the vision and scope of any project.
Incomplete requirements are often cited as the number-one reason projects or systems fail, and accurately defining the requirements and staying on course from the beginning is critical to success in our current environment. This practical course introduces the ‘Business Analysis Success Model’ and how it relates to the role of the business analyst in the analysis and documentation of requirements and the documentation of the solution’s vision and scope. It familiarises participants with core knowledge and skills required to analyse and document user requirements and identifies how these requirements are defined and managed throughout the project life-cycle.
What topics will be covered in the course?
- Roles, Definitions and Key Principles
- Critical role of the business analyst
- Creating and adopting a formal documentation strategy
- Key requirements documents
- Roles and mutual expectations among team members
- Types of Requirements
- Attributed and other 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
- Managing change
- Introduction to Modelling
- Documenting and tracking business rules
- Why use models?
- Modelling techniques
- 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
- Elicitation Techniques
- Dealing with barriers to elicitation
- Elicitation strategy
- Elicitation techniques
- Advantages and challenges of elicitation techniques
- Documenting Requirements
- The purpose of documenting requirements
- Elements of a business requirements document
- Technical writing guidelines
- Requirements analysis
- The role of modelling in requirements documentation
- Use case and activity diagrams
- Presenting requirements
- Managing Consensus
- Communicating effectively
- Effective consensus building
- Validating Requirements
- Validation techniques
- Decision making and approvals
- Managing change and risk post-validation
- What happens next?
What will I learn?
- Define the role of the business analyst in the requirements process
- Effectively document a solution's vision and scope
- Develop a requirements analysis work plan
- Elicit, structure, analyse, validate and document business requirements
- Structure a business requirements document
Is this course for me?
This course is for Business Analysts who need to update or formalise their roles, authorities, accountabilities, and activities; Project Managers who incorporate the Business Analysis role into their functional activity sets; Business Managers and users who interface with Business Analysts; and systems analysts, technical leads, database analysts, and software developers who must use requirements as the basis for solution specification, development, and implementation.
What is included in the price?
Individual training consultation before and after the course
Does this course help me towards certification/accreditation?
At the end of the course you will get the chance to verify your level of knowledge in a test. You will receive a certificate upon successful participation. This course is also eligible if you aim to achieve an Associate’s or Master’s Certificate from George Washington University. Learn more.