Best-Practice Quality Assurance for Small Teams
summary
Starts from the claim that small teams can adopt enterprise QA practices without big budgets and gives concrete steps: set up issue tracking early (recommendation: use JIRA with custom forms but Trello/Asana OK), appoint a QA champion, document a source of truth and write test skeletons rather than exhaustive cases, schedule everyone for testing, verify fixes by original reporters, and expect QA to cost real money. Examples include building QA at Live Tiles and running The Machine QA consultancy. prioritize defects by severity and priority
AI-written summary · about
chapters (20)
- 0:00Introduction
- 8:02What is QA
- 9:53QA Fundamentals
- 16:57Issues and Tasks
- 19:43Cheap QA
- 21:15QA Process
- 24:29Source of Truth
- 26:37Test Skeleton
- 28:38Schedule Testing Time
- 30:10Bug Reports
- 32:34Priority and Severity
- 34:24Verification
- 35:52Community Testers
- 37:24Internal Testers
- 38:46QA Questions
- 43:47QA Recommendations
- 46:13Coview Reviewers
- 47:02NDAs
- 48:38Cover Letters
- 50:47Who are you looking for
related talks
21mEstablishing Quality Assurance in Startup environment
08m"How to Start a QA Department"
56mNo QA resources? You can still deliver a quality website
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
53m20 QA Best Practices to take back to your workplace
41mLife Without QA
28mInstilling the built-in quality mindset into a dev team
36mWhy a Growing Company Needs a Growing QA Team