Testing Complex and Time Critical Projects!
summary
Claims managing five complex, time‑critical applications on a roughly six‑month schedule with initial chaos: 30+ stories in the first sprint, teams without access, and a failed production push. Implements practical fixes: peer testing, screen-recorded bug reports, chat groups with client contacts, reverse planning from the deadline, an Excel color‑coded tracker and lock the builds rule. Result is fewer critical UAT bugs, predictable contingency plans, and reclaiming about four to five hours of daily capacity.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:28First day chaos
- 3:57Failed production release
- 5:01Five critical projects
- 7:27ISRO and rail projects
- 9:57Time-critical principles
- 11:01Trust and team coordination
- 12:04Weekly team meetings
- 13:05Planning and goal setting
- 14:09Breaking barriers
- 15:35Peer testing strategies
- 16:40Locking builds
- 17:23Time estimation
- 18:06Prioritization and agile
- 18:46Productivity tools
- 19:52Final advice
related talks
26mHelp! We have a QA problem
36mDevising a Project Test Approach
36mHow programmers & testers can be productive
49mBalancing Release & Sprint Delivery Speed with Thorough Testing
10mBeyond “try harder”: Effective strategies to tackle bugs
36mContext-driven Agile Tester
36mHow to defuse a bomb Wait, I mean a bug
31m#testedAF: Test All the Things (Not Just Your Units)