The Benefits and Challenges of Maintaining a QC Work Plan

Member Submitted
The work plan described in this article raises visibility to other teams' tasks that impact the QC schedule, shows other dependencies, documents historical data, and is flexible enough to use for different types and sizes of projects, as well as for different audiences. Since business users and project team members may not understand all that occurs during the testing process, it's wise to use a QC work plan to show all tasks, persons accountable, estimated duration, and actual duration for the software project.

During a directors’ project status meeting, one project manager states “we haven’t met the schedule because the release is still in testing.” The directors think “what are those testers doing and why are they holding up the schedule?” when the data, if it was tracked, would show that the Quality Control (QC) team has received 18 builds and the team cannot complete a test cycle because of severe defects that require fixes.

One tool to track this data is a QC work plan. This work plan shows QC tasks, dependencies and resources, is flexible enough to use for different types and sizes of projects, may be used for various audiences, and documents historical data. Along with the benefits of the work plan, there are challenges and costs associated with it.

Click on the file attachment below to read this paper.

About the Author

Shannon K. Brown has over thirteen years of experience in the quality discipline within a variety of industries including pharmaceutical, engineering, start-ups, and hospitality. Sonya Oetting has over seven years of experience in the quality field including engineering, e-commerce, retail, and hospitality industries.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.