Test Management

Bug Modeling

Charting and highlighting bug trends to improve Schedule Predictability.

Schedule/Milestone Management

Milestones indicate significant events or phases in a product lifecycle and provide clear goals for the software QA test effort. Excessive missed milestones may indicate that a project is beginning to slip.

Project Metrics

These provide a snapshot of the project bug status and test progress. Metrics give you an "at-a-glance" view highlighting trends in your effort.

Quality Reports

Regular statuses keep you informed of progress and red flag open issues for early resolution. Quarterly reports give you a wider view of project progress and aid planning for future phases. Final Quality reports are a wrap-up of all software QA testing performed and provide a "postmortem" view of the whole effort.

QA Project Plans and Test Plans

These documents define terms and strategies and serve as a charter for your test effort.

Risk Assessments

This involves analyzing risk criteria associated with your project to determine the current level of risk to your project. Solutions can then be applied to mitigate critical areas before they become project-threatening problems.

Issue Management

Bug lifecycle planning will set up a process for finding, fixing, and verifying bugs. Bug fix prioritization will determine what issues need immediate attention.

Test Environment Planning

Shasta QA can help you determine what tools and techniques you need for a more effective test effort.

Component Prioritization

Your development schedule may not permit testing all components completely. Being able to identify components where failure is most critical can ensure appropriate software QA testing for those areas.

Staffing Estimates

Experience has shown that knowing how many software QA test engineers to assign to a project, and the ratio of testers to development, can be critical to the success of a development project.