Quality Assurance Presentation II
The point of this presentation is to communicate the status of your project with one iteration to go to complete it. The status should be reported in terms of a quality assurance report that details how effectively requirements are being met. Your first quality assurance presentation detailed how you PLANNED to ensure the quality of the system you are building. This presentation should quickly review your process, environment and mechanisms for assuring quality but the focus should be on reporting what verifiable progress has been measured with a view to defining what is left to do in your final iteration.
Quickly recap the purpose of the project and illustrate the current status of your running system with a few screen shots relevant to the key requirements and critical scenarios for your system. If there have been any significant changes in requirements or unexpected issues that required special attention, highlight them.
Quality Assurance Strategy and Test Framework
Quickly recap the strategy and processes you have in place for assuring quality and performing tests. Be sure to explain how the strategy and tests relate to your key requirements and critical scenarios in order to verify that they have been implemented properly.
Quality Assurance Report
Summarize the results of your testing so far, and if possible correlate them to the requirements and objectives for the project. You should have at least two test runs done a different times (say at the start and then at the end of iteration 5), so you can show how quality is improving. If you have not yet achieved the level of quality you would like, the previous test run can be helpful in estimating how much more effort is required. You should also summarize the stability of the product in terms of how many bugs have been found so far, their severity and how many remain to be fixed. You should give full details of one or two critical tests (data used, framework, results) in order to illustrate concretely what you are doing in your testing. However, the full details of the tests run, results, bugs etc. should be left for your final report.
Outline your plans for deployment to your customer and the current status. Has the system been deployed to the customer yet as a demo, pilot, or full install? What issues will you face or have you faced in deploying to your customer? What acceptance testing have you done or plan to do with your customer either in your development environment or in their production environment?
Highlight the key tasks still remaining that need to be accomplished for your final iteration, especially those that are required to address any quality assurance or deployment issues that have arisen in your testing.