What methodologies have you used in your work?
sobes.tech AI
Answer from AI
Worked with agile methodologies, primarily with Scrum and Kanban.
Scrum:
- Teamwork: Daily Scrums, Sprint Planning, Sprint Review, Sprint Retrospective.
- Iterative development: Sprints (usually 2-week long).
- Roles: Scrum Master, Product Owner, Development Team.
- Artifacts: Product Backlog, Sprint Backlog, Increment.
In Scrum, the focus is on incremental product delivery and adaptability to changing requirements. QA actively participates in all meetings, assists with task estimation (Story Points), performs testing in each sprint, and participates in Demos and Retrospectives.
Kanban:
- Visualization of work: Kanban board with columns reflecting stages of the workflow (e.g., To Do, In Progress, Testing, Done).
- Work in Progress (WIP) limits: Limits the number of tasks at each stage simultaneously.
- Continuous flow: No fixed iterations; tasks move through the board as they are ready.
- Metrics: Lead Time, Cycle Time, Throughput.
In Kanban, the focus is on optimizing flow and minimizing task passage time. QA actively manages tasks on their board, works on reducing Cycle Time for testing stages, and uses WIP limits to balance workload.
Additionally, experience was gained working in environments with Waterfall elements, especially when interacting with large clients, where formal documentation and planning at the initial project stages were required. In such cases, the V-model or modified approaches combining Waterfall stages (requirements, design) with iterative testing within these stages were used.
Important aspects of QA work in these methodologies:
- Scrum: Testing in each sprint, participation in backlog grooming, writing and updating test cases/checklists based on user stories, automation of tests as part of the Definition of Done.
- Kanban: Focus on speed and quality in flow, minimizing defects at the testing stage to prevent blockers, prioritizing testing considering WIP limits, monitoring quality metrics.
In both cases, cross-functionality and close interaction with developers and the Product Owner are important.