Please enable JavaScript.
Coggle requires JavaScript to display documents.
BA Process (Improvements / Pain points (Communication (Ensuring all reqs…
BA Process
Improvements / Pain points
Communication
Ensuring all reqs captured
Leading relationship as POC with business & WG
Included or leading all requirement gathering sessions
Working Group
Detailed requirements - time needed
Scheduling availibilty
Correct users given access to
Requirement sign off
at Working Group or Exec sponsor level?
For every req?
Just high level req?
Definition of Done
Ongoing discovery during dev cycles
put timelines at risk
Need for single source of record for doc/req
Solutioning
UX/UI requirements
Epics/stories
Definition of Ready
Process flows
Tech solution
managing backlog
Working Gruop
Additional reqs discovered
Prototype reviews
Detailed requirement gathering sessions
Discovery and Planning
Business sign off of features
Working Group sessions
Working Group defined
Scoping & prioritization
backlog creation
JIRA
Epics & user story creation
google docs
smart sheets
JIRA
Dependencies determined (process/ref data)
Estimation & scope management (support & verify)
Shadowing / SME knowledge transfer
Initial notes / requirements drafts
Confluence
Process flows (current state)
process flows (future state)
Testing
UAT
E2E
Test cases
Roll Out
Support
Training
Defining roll out strategy with stakeholders
Development
Working Group
Clarification on cards/req
UI reviews
Additional info for cards