Define the project manager as the project’s driver responsible for budget, deadline, scope, and quality, and show how business analysts support them by managing risks and keeping projects on track.

Explore waterfall and iterative SDLCs, compare their phases and testing approaches, and learn how V-model mapping highlights testing at each development stage and the benefits and challenges of iteration.

Identify and apply six key requirement attributes: clear, complete, applicable, prioritized, implementable, and testable, to prevent miscommunication and guide peer reviews and walkthroughs.

Identify requirement sources, including stakeholders and documentary sources like existing documents and standards. Ensure reliability, consult experts, and document sources with named individuals to guide effective requirement gathering.

Explore the art and science of gathering requirements through one-on-one stakeholder interviews, emphasizing preparation, open-ended questions, confirming understanding, and follow-up notes.

Collaborate to define agile requirements through user stories and acceptance criteria, manage product and sprint backlogs, and decompose epics into actionable tasks.

Explore the business analysts toolbox, focusing on analysis and modeling to transform stakeholder requirements into effective solutions by examining needs both individually and holistically.

Learn to use swimlane flowcharts, organizing steps by actor lanes to show who does what and when, highlighting handoffs and bottlenecks with real-world examples.

Explore entity-relationship modeling with diagrams that map entities, relationships, and attributes, using cardinality to show how many instances participate.

Explore data flow modeling with Yourdon DeMarco notation, illustrating how data moves through processes, data stores, and inputs/outputs, driven by labeled arrows and simple rules.

Learn to model user–system interactions with use cases and diagrams, covering components, flows, preconditions, postconditions, and basic versus alternate paths.

Baseline the requirements and apply a formal change control process to review and approve changes via change requests and a change control board.

Apply analysis and modeling techniques to gathered requirements, note that 20–30% of analysis occurs during gathering, perform stakeholder needs analysis, decompose inputs, and document current process with a swimlane flowchart.

Learn decomposition analysis by breaking the product sales report into title, top table, and bottom table, iterating to finer pieces, and mapping the report collation with a swimlane flow chart.