Customer Discovery - business analyst roles and responsibilities Flashcards
what do business analysts do
facilitate collaboration between the business and technology teams of an organization
participate in all phases of the project to ensure successful delivery, ending with presenting and monitoring final deliverables
skills business analysts need
soft skills
analysis of business needs - define business needs
eliciting requirements - gather input from stakeholders
writing business cases - what, why, how, who of project
reviewing requirements - document
creating flows, diagrams
wireframing (visually depict processes)
data analytics
problem solving
what tasks do BAs do related to elicitation, documentation, and analysis of project requirements?
requirements gathering
document findings
analysis of requirements
how do business analysts manage pain points?
Find solutions
facilitate testing in UAT phase, design use cases, obtain sign-off
how do business analysts participate in project delivery?
handle communication with stakeholders
ensure on track with timeline, fulfill acceptance criteria
Business Analyst Role in Analyze phase
Lead the analyze phase
Gather Requirements
Obtain Sign-off
Business Analyst Role in Build Phase
clarify business requirements - user stories are clear
aiding in UAT - ensure bugs are fixed
Business Analyst Role in Delivery Phase
solving issues related to user stories, facilitate meetings, keep teams aligned
manage project scope - keep it accurate and modifications won’t impact timeline
Business Analyst Role in Operate Phase
review final deliverables with stakeholders
train users and gather feedback
business analyst vs admin roles
BA more project management, admin more platform set up
What are the technical skills a BA has to have a basic understanding of?
AppExchange
Automation
Collaboration
Data management
Reports and dashboards
CRM
Platform
Sales and Marketing
key activities of BA
Communication
Elicitation
Document Requirements
analyze Information
Facilitate solutions
Implement solutions
Test
4 misconceptions of BA
need to be super technical
shouldn’t configure on the platform
only needed after project kickoff
only focused on requirements
BA Skill - Analysis of business needs
define business needs, have technical understanding to translate to tasks
BA Skill - Business Case Definition
write business cases to provide reasoning for project
what, why , how and who of project
BA Skill - Elicit Requirements
gather requirements from internal and external project stakeholders
Workshops, interviews, observation, brainstorming
BA Skill - Requirements Review
After requirements gathered, document and review project requests to design work plan
BA Skills - Flows and Diagrams
visual representations of processes
BA skills - Wireframing
break down the processes to depict how processes fit into the business flow
BA Skills - problem solving
variety of tools to solve problems identified in the requirements elicitation phase
BA Best Practices when running a meeting
always have a presentation prepared
BA - what to do when a stakeholder comes to the meeting already with a solution?
If you’re faced with a preemptive solution, encourage the stakeholders to think of what they want to accomplish in generic terms, not in the context of a specific product. Always guide them to think about why they need to do something differently, instead of how to do it differently.
what are attention traps?
BA - when getting requirements, one person talks the loudest and is super responsive. You should make a effort to hear everyone out, so you can be sure to be prioritizing the most important item, not just the item the responsive person is saying.
In requirements gathering, what should you do to measure success?
Establish benchmarkings! See current state, get measures you can see and compare at end of project
