Beyond Requirements: Whose Job Is It Anyway?

Session Overview and Relevance

As a Business Analyst consultant, you are given a clear statement of work with set deliverables; however, when the Project Sponsor wants to know why no one is using the new system, who’s job is it to resolve the resistance? While the Project Manager (PM) focuses on technical delivery and the Change Manager (CM) focuses on training/communications, the Business Analyst (BA) holds a critical position in the middle, translating requirements into actual, usable business processes.  Drawing on experience working in integrated project teams, we will move beyond the textbook to explore the messy reality of the BA consultant’s role. In this interactive session, you’ll join in a high-stakes game of "Whose Role Is It?" to uncover the accountabilities of the BA, PM, and Change Manager.  Come prepared to dive into the ambiguity, challenge the silos, and learn why the BA is a key player in the success of a project.

Learning Objectives

By the end of this session, participants will be able to:

• Differentiate between scope delivery (PM), user adoption (CM), and process alignment (BA) to identify where accountabilities overlap.

• Analyze common "grey area" scenarios to determine how a Business Analyst can proactively address user resistance through process design and requirement validation.

• Develop strategies for breaking down project silos to ensure the "Business Requirements" translates into a solution that is actually adopted by the business.

Target Audience

• Business Analysts (Mid- Senior): Business Service Consultants who find themselves caught between a rigid Statement of Work and the reality of the project team.

• Project Managers (PMs): Those responsible for technical delivery who often feel confused on the grey areas of the project team members roles.

• Change Managers (CMs): Professionals focused on the "people side" who need to work with the BA

Expected Outcomes / Takeaways