Creating a test plan can be a daunting task, especially when under time pressure. "We need you to test this application and, oh, we go live next Monday." How do you create a plan to test that is accountable, transparent, and structured, yet lightweight enough that can quickly be understood by developers, project managers, other stakeholders, and new testers that may be brought on to help out? And not only that, but be created quickly?
