Project Scheduling
leaders from other areas of the project to understand when their contributions will be
ready for testing. You then must balance your original schedule against the risks and
resources you identified in order to arrive at the most effective schedule for testing.
Each testing iteration presents an opportunity to validate one or more of your test
cases. Developing a testing schedule based on iterations helps you filter your test
cases so that you can more effectively design, implement, and run your tests for each
stage of software development.
you schedule at least the "must" (high priority) and "should" (medium priority) tests.
If resources become constrained over the course of the project, you can sacrifice tests
of lower priority without compromising the absolute quality objectives expressed by
the "must" tests.
own. You can associate iterations with test cases, then run these test cases based on
iterations.
and tasks on your project schedule. For more information, start RequisitePro as
follows:
RequisitePro opens and the Open Project dialog box appears.
Wizards, Integrations and Components > RequisitePro Wizards >
MS Project Integration Wizard
Microsoft Project.