Business Analysis Documenting & Managing Course

Course Description

Translating the needs of stakeholders into a compelling story or narrative is the next step in your analysis journey. Once you’ve elicited and modeled, there’s a good chance you need to create some type of documentation to ensure that requirements are well understood. Whether you are working in a traditional, plan-driven environment or in an agile-like situation, this course will help you write well-formed requirements. We’ll also work through where the business analyst fits in to the project process after the requirements are documented. How are requirements prioritized? When is traceability used? What is traceability anyway? When and how should a BA be involved in testing? All this and a more as we dive further into documenting and managing requirements.

Take this course alone, or as Course 5 of The Business Analysis Certificate program. 

Length: 2-Days

CDU/PDU: Earn 14 CDU/PDU for both IIBA and PMI certification

Prerequisites: Introduction to Business Analysis course or experience in the business analyst role.

Intended Audience: Anyone who works on projects, especially those who are is interested in a career in Business Analysis, want to understand what Business Analysis is, want to help promote the profession of Business Analysis in their organization.

What We Cover:

  • Approaches for documenting narrative requirements

    • The Business Analysis Body of Knowledge requirement classification, as well as the Uncommon League’s new approach to understanding requirements

    • Where Progressive Elaboration fits in to requirements documentation

    • The quality criteria for well written requirements 

    • How to present different components of requirements

    • Different constructs for writing narrative requirements

    • Practice writing well-formed requirements for both Agile and Traditional approaches

    • How to correct requirements for clarity and quality

    • Techniques to check your work 

    • Components of a business requirements document

    • Components of a system requirements specification or functional requirements document

  • The next steps for requirements and analysis deliverables

    • Effective methods for prioritizing requirements in Waterfall, Incremental or Agile approaches

    • Packaging requirements effectively based on stakeholder preferences

    • Understand the fundamentals of requirements traceability

    • How to trace requirements to business goals and objectives, scope, design and testing

    • How to create a traceability matrix

    • Methods for approving analysis deliverables

    • How to manage changes to requirements and deliverables after sign-off has occurred

  • What happens after requirements are approved?

    • The Business Analyst role in design

    • The Business Analyst role in quality assurance (QA) or system testing

    • The Business Analyst role in user acceptance testing

    • The Business Analyst role during the implementation of the solution

    • The Business Analyst role after the solution has been implemented

Registration