In both agile and waterfall development, keeping the test plan up to date is essential for ensuring quality and alignment with project goals. In waterfall projects, updates typically happen at key milestones—after requirements are finalized, design is approved, or major changes occur. However, the test plan is generally more static due to the fixed nature of the process.

In agile, the test plan should be treated as a living document. With frequent iterations and evolving requirements, it's common to revisit and adjust the plan at the start of each sprint or when there's a significant shift in user stories or acceptance criteria. This helps the QA team stay aligned with developers and ensures tests remain relevant.

How does your team handle test plan updates when priorities shift mid-sprint or during late-stage development?