How to Gather and Document User Requirements
via E-Training
42 Days – Course No. eBA20
Target audience:
◦ Business Analysts who need to update or formalize their implicit
understanding of their role, accountabilities and activities.
◦ Project Managers who incorporate the business analysis role within
their functional activity sets.
◦ Business Managers who work within a project environment, and who
interface with Business Analysts and Project Managers
Recommendation
The material presented in this course provides
the foundation necessary for building additional business analyst skills. You
should take this course before taking any additional courses in the curriculum.
Learn How to:
◦ Explain the critical role of the business analyst with respect to
requirements elicitation and project management.
◦ Develop and validate a solution vision and scope that will enable
the creation of measurable quality standards.
◦ Use appropriate modeling techniques to create the business
architecture baseline.
◦ Plan the requirements elicitation and analysis to maximize
efficiency and estimate the required effort.
◦ Determine the most appropriate technique(s) for eliciting
requirements at different points in the analysis cycle.
◦ Analyze various kinds of requirements into a complete, coherent, and
organized requirements document.
◦ Build consensus in order to validate and finalize the requirements
in the business requirements document.
course synopsis:
Incomplete requirements are often cited as the
number-one reason projects or systems fail. Accurately defining the
requirements and staying on course are 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 familiarizes participants with core knowledge and skills
required to analyze and document user requirements. It also identifies how
these requirements are defined and managed throughout the life cycle.
Recommendation: The material presented in this
course provides the foundation necessary for building additional business
analyst skills. You should take this course before taking any additional
courses in the curriculum.
This online course takes advantage of an engaging new learning methodology and
Macromedia Flash™ delivery platform. Each lesson includes a realistic scenario
and a problem related to project management—similar to those project managers
face every day—along with a "Project Desk" filled with the resources
necessary to solve each problem.
Learning is both independent and interactive.
Lessons and individual assignments are self-paced. In addition, threaded
discussion questions enable participants to apply the lesson content to their
own work situations and interact with other participants. The instructor provides
personalized feedback to both the individual assignments and threaded
discussion answers and is always available to answer participant questions
about course concepts.
course topics:
Introduction to Requirements Elicitation
◦ Position business analysis within the overall discipline of project
management
◦ Describe the business analysis process and its underlying themes
◦ Determine the appropriate levels of detail at which business
analysts should define requirements
◦ Establish the appropriate documentation set necessary to manage
project requirements
Establishing Vision, Scope, and Quality
◦ Capture solution vision at all business and user levels
◦ Find the right boundaries for your business requirements
◦ Create high-level quality targets for a solution
◦ Explain the relationship of vision and scope to quality
Modeling at the Enterprise Level
◦ Describe the function of modeling in business analysis
◦ Explain how business rules constrain processes and drive
requirements
◦ Create basic business models to aid in comprehensive enterprise
analysis
Developing the Requirements Work Plan
◦ Describe the value of creating a work plan for the requirements
elicitation process
◦ Build and execute an action plan for capturing requirements in the
appropriate order
◦ Build a work breakdown structure for the business analysis activity
within the Analysis phase of the project
◦ Explain the importance of defining who the users are as part of the
analysis planning process
◦ Identify risks to the Analysis phase and plan risk responses according
to risk priority
Requirements Elicitation
◦ Describe the value of creating a work plan for the requirements
elicitation process
◦ Build and execute an action plan for capturing requirements in the
appropriate order
◦ Build a work breakdown structure for the business analysis activity
within the Analysis phase of the project
◦ Explain the importance of defining who the users are as part of the
analysis planning process
◦ Identify risks to the Analysis phase and plan risk responses
according to risk priority
Developing the Business Requirements
Document
◦ Write a comprehensive, unambiguous business requirements document
(BRD), communicating the needs of the business to users and the technical team
◦ Describe how the requirements analysis process completes the BRD
sections
◦ Apply standard technical writing principles and techniques to
requirements documentation
◦ Create requirements documentation that can be used as the basis for
customized development, maintenance of existing systems and/or as selection
criteria for off-the-shelf software
◦ Determine whether the business requirements document is complete and
consistent
Validating Requirements
◦ Validate requirements documented in the BRD using an identified
validation technique
◦ Select and apply appropriate consensus building techniques in order
to come to agreement on the finalized set of requirements documented in the BRD
◦ Obtain formal approval to proceed
◦ Understand the project's change control process
Other Information:
Professional Development Units (PDUs): 24