In an agile team, pre-planning all your tests is not always the most efficient use of time for testers. PBIs can change direction, scope, and priority, and pre-planned tests are likely to change.
Exploratory testing provides the best way to create repeatable tests from the acceptance criteria - as you need them.
There are two ways to run an exploratory test in Microsoft Test Manager.
Figure: Bad Example - go to the Test tab, choose Do Exploratory Testing, choose a PBI, then click Explore. Too many steps.
Figure: Good Example - Right-click on a requirement in your test suite and choose Explore requirement
Note: You should always run an exploratory test against a PBI. This will automatically relate any bugs and test cases to that PBI (not to mention the exploratory test run).
When you start an Exploratory test, you don't see any test steps, but you can click on the title of the requirement to see its Acceptance Criteria.
Figure: Clicking on the title will show you the Acceptance Criteria
If you find a bug while testing, click the Create bug button to add a bug related to the PBI.
Figure: Creating a bug from an exploratory test links to the PBI
By default, the reproduction steps will be populated with the last 10 actions you took (you can change this and other defaults with configuration). You can cut this down to just the relevant actions by clicking Change steps.Figure: You can change the repro steps captured in the bug very easily
Now you have a bug, you should create a matching test case so you can verify when the bug is fixed. This also gives you a handy regression test to help ensure the problem isn't reproduced later.
Figure: Click Save and create test to create a matching test case
Again, the steps are prepopulated from your bug steps.
Figure: The test steps are prepopulated from the action recording