Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements and Data Gathering batch 5 - Coggle Diagram
Requirements and Data Gathering
batch 5
Requirements
Presentation of Requirements
MotM as confirmation of understanding or requirements
Traceability Matrix
User Story
from ACR (SNoW) > Epic
not yet using feature flag
People
Product Owners
understanding business team structure
sometimes, creation of product roadmap is delegate to someone else (e.g., BAs)
visual: likes seeing the UI/system to provide feedback / requirements
important to be present, to help bridge Business and Product team
needs to be onboarded on Agile practices, including their roles and responsibilities
Product Manager
Your Product Team
BAs
business language > tech language
Devs
QAs
Other Product Teams
(dependencies)
Vendors
vendor BAs, devs, and QAs
complete documentation is important to record ADB's requirements
Tools and Templates
ADO Work Item Templates
bulleted / short descriptions
given-when-then (helpful for QAs)
SDLC Documents
Trainings
team KTs / brownbag sessions
for other teams, there are account leads
BA hub
onboarding
no standard BA onboarding
self-learning
technical knowledge / skillset
stakeholder management
vendor management
BAs are reliant on engagements or documentations
over-all BA training
user story essentials (July-Nov)
Process and Technique
Elicitation and Collaboration
ACR request and approval
if no ARC yet, meeting with stakeholders (understand requirements, flowcharts, etc)
ideally, should come from product roadmap
email, chat, call with BU
for mature products, where to get the enhancements? esp. if delivery is part of vendors' contracts
if approval is delayed, but request is anticipated, user stories are created ahead of time
workshops: most effective to get complete requirements, including dependencies and risks
projects
understanding as-is process (via documentation, interviews, survey, workshops, etc.), led by BA
Analysis
updates to the backlog
getting updated backlog from UAT issues or other future enhancements
some work items are not yet placed in ADO since most of the time, prioritization / requirements get changed (maintained internally)
prioritization
negotiates with POs for non-critical/non-prio enhancements
projects: understanding to-be process (re-engineering the process, addressing painpoints, etc)
sizing
Design
Visio
PowerPoint
Digivision
config in lower environments
Figma
high-fidelity design, high learning curve, question on licenses
Paint
paper / post-its (during workshops)
Excel
Review and Approval
delays from the business' side due to multiple reviewers, and requirements are constantly changing
biweekly meetings with BUs (to discuss requirements, timelines, updates, impediments, etc)