# Way of working
Work flow for user story and US-related working items (task, bug, test suites)
BA: BA receives requirements from PO/stakeholders and creates an user story. BA analyzes the requirement and creates the task name: Analyze the business logic. BA updates the US under description, AC, screenshot, then get confirmation from PO/stakeholders. Confirmation of a User Story will be added in comment section as "Confirmed".
Team Lead: After user story is assigned to TL in cross planning meeting section, TL creates a new task: investigate and starts investigating the solution and technical then updates directly in the US, under comment section. TL gets confirmation/review from technical team for technical solution.
Team Lead: In sub-team refinement meeting, TL assigns the user story to developer, briefs description and technical proposal. For user story need BE tasks, BE will incharge the user story.
QC Lead: QC Lead investigates the user story after Team lead refinement meeting, assigns to QC Engineer, transfers requirements to QC for creating the test scenario.
BE Developer: BE Developer pickups the US, reads all spec + technical approach and double confirms with TL if any. Breaking detail task include BE and FE ( assign to FE). All fields in task shall be updated each two working days. From now, BE in-charge of timeline, development. TL need to monitor the state closely.
QC Engineer: QC Engineer reads the spec , creates test suite for the US, fills the effort estimation, defines the test config and creates test scenarios. All suites need to be link to the US by using requirement-based test suite type and updated it's remaining effort each two working days.
Developers: Developer checkouts the code from repository, then creates a new branch for their's work. BE developers collaborate with FE developer to implement the task. BE developers create PR and record the video attach to the PR (FE and BE PR). Then submit PR to their TL for review.