"Small Changes for Big Wins"
summary
Team moves from three‑week to two‑week sprints and adds one tester, cutting cycle time while keeping coverage. A modular test matrix in Excel becomes the single source for areas and primaries, later linked to a components field in Jira so trends and exploratory targets are visible. Daily scrums drop to twice a week, and a handful of automated end‑to‑end tests with Testim slowly raise coverage — practical, incremental changes that work.
AI-written summary · about
chapters (5)
related talks
26mHelp! We have a QA problem
31m#testedAF: Test All the Things (Not Just Your Units)
46mTalk about value, not testing – how to bring about rapid change
26mJust doing scrums won’t win the game
49mBaking Boards: Tweak the Recipe for Agile Development
01h 00mHow microteams change the way we collaborate
42mIncredible Agile Teams
32mEnterprise transformation (and you can too)