Testing in one week sprints, hierarchy backlog items and test coverage.
One week sprints are great and bring big benefits to you team and product.
The artifacts that are in your system will be; 
the backlog with nice small backlog. That small that they can be realized in the one week sprint. your sprint will contain a 
test plan for the sprint, with related product backlog items. Probably there also will be some 
additional test plans for other concerns/ risks. The 
regression test plan finally will contain a collection of test cases gathered from the sprint test plans and the additional test plans. And the customer will use a 
acceptance test plan for there work.
This works great. And, because the PBI’s 
with their corresponding test cases 
are that small the team will have the continuous discussion if the needed validation should be implemented with unit test technology/ automated test or, if it would be easier/ faster/ better/ higher ROI to specify and execute the test as a manual test. Work around testing in this way makes it a real team effort which makes it easier to get testing done in the sprint.
How should we test this PBI?
The test cases during a sprint are that small that also the 
regression set will become a collection of very small validations of the system. After several ‘one week’ sprints the bigger scenario / end to end test cases are missing. A collection of small validations made the team uncomfortable about the quality of the regression and unit test case set.
For example: when making several settings the system behaves in a different way. In our situation is was the backend connection with either SharePoint 2007, 2010, 2013 or O365. Making this setting and saving this setting was one PBI. The different behavior according to this setting where other multiple PBI’s. And the overall collection of settings (all different PBI’s) made the system behaves different. We needed an Activity Diagram to explain its behavior.
The decision to make use of Parent PBI’s is easy made (we called them Features and prefixed them with this name).
Related to these ‘feature’ PBI’s a feature test plan can be created, which will cover the full scenario and all path coverage's. in this way giving the team the comfort that all paths and scenarios are covered.
Finally ending up with a bit more complex organization, but with a better test coverage.
Feature PBI’s broken down in child PBI’s, which are partly implemented in a sprint. A nice additional benefit is that the team focuses on Feature PBI after Feature PBI, implementing them one after another. 
Activity diagrams support the scenario, and when needed use case or other UML diagrams. The overall scenario (activity diagram) is related to the Feature PBI and the different actions can be related to the child PBI’s. 
Testers can use their Test Design Techniques when analyzing the UML diagram for test coverage and test cases. And the 
regression set will be a mix of Sprint Test plan test cases and Feature Test plan test case.
Everything perfect. But the bit more complex organization of the backlog has its challenges. Not all PBI’s relate to a Feature PBI and often a PBI’s influences / relates to multiple Feature PBI’s. The one activity diagram per feature is fake and a theoretically example, the real world is more challenging. See also Martin’s post You can’t stack rank hierarchical work items?.
Although it will give you some extra backlog grooming activities, still Features PBI’s can bring benefit to the system. Don’t try to make it too perfect and definitely have testing knowledge in place for the coverage then it is a good thing to give it a your bigger systems.
6 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2: Test Planning
3: Test Specification and Execution
4: Test Controlling and Reporting
5: Test Infrastructure and Virtualization
6: Operations Integration
Feel free to ping me if you want to have these sessions delivered at your company.
5 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2: Test Planning
3: Test Specification and Execution
4: Test Controlling and Reporting
5: Test Infrastructure and Virtualization
6:
Operations Integration Feel free to ping me if you want to have these sessions delivered at your company.
4 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2: Test Planning
3: Test Specification and Execution
4: Test Controlling and Reporting
5:
Test Infrastructure and Virtualization 6:
Operations Integration Feel free to ping me if you want to have these sessions delivered at your company.
3 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2: Test Planning
3: Test Specification and Execution
4:
Test Controlling and Reporting 5:
Test Infrastructure and Virtualization 6:
Operations Integration Feel free to ping me if you want to have these sessions delivered at your company.
2 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2: Test Planning
3:
Test Specification and Execution 4:
Test Controlling and Reporting 5:
Test Infrastructure and Virtualization 6:
Operations Integration Feel free to ping me if you want to have these sessions delivered at your company.
1 Testing with Visual Studio 2012 Agile TMap _ The QUALITY A-Z Roadshow
The QUALITY A-Z Roadshow:
A full day overview, with demo’s and real world experiences of all the testing capabilities of Microsoft Visual Studio and needed testing practices.
1: Keynote: The Value of Quality
2:
Test Planning 3:
Test Specification and Execution 4:
Test Controlling and Reporting 5:
Test Infrastructure and Virtualization 6:
Operations Integration Feel free to ping me if you want to have these sessions delivered at your company.
Hands-on Visual Studio 2012 Workshops - What to do with your free Azure MSDN subscription.
I run workshops.
Instead of boring lectures, I give the attendees the opportunity to get real hands-on experience and feel the scenario instead of listing only.
Specially the Visual Studio 2012 ALM scenario’s are really nice, the attendees work together on a scenario like: code review, feedback, agile planning and testing.
I run these workshops with Azure Virtual Machines, every attendee has it’s own environment on Azure prepared and configured by me for that specific workshop. After I created an image (see: How to Capture an Image of a Virtual Machine) one day ahead of the workshop, I start creating Azure VM’s just before the workshop starts (see: Create a Virtual Machine). After the workshop I kill everything again. so, I only use it for a minimal amount of time, a perfect cloud benefit scenario.
A small calculation on the Azure costs will give you insight in how many time you can run such a workshop a month. Indeed this costs so less money that you can run these kind of workshops for 20 people multiple times a month without getting over the free boundaries of your MSDN Azure account. Probably this will change while, the in beta, Azure VM’s are still free. You ‘re only charged for bandwidth and blob storage, which is cheap.
All attendees are connected with my Team Foundation Service. They provide a MicrosoftID (aka LiveID / Hotmail account) which they use to connect to TFS, within five minutes after the workshop starts everybody works together in teams on the same code base and backlog.
A really nice scenario on how Team Foundation Service enables ad-hoc teams to start working together. I few weeks ago I did a test workshops and after five minutes 40 testers where testing, specifying test cases, run tests cases and automated test cases for just one specific application for three hours. Not only interesting for workshops.
So, what to do with your un-used Azure power which comes with the MSDN Subscriptions benefits, run workshops! It is really interesting for the attendees, easy to setup and free.
One thing to pay attention to: look if the software you're installing on the image is valid for Azure. I use trial versions of software, sometimes you’re not aloud to run it. But, my workshops only take three hours. I kill everything afterwards and make the attendees experienced in the installed software, explain it to the software company they will probably love it and almost for sure they didn’t cover this three hour scenario in their licensing and allows it to use it.
Continuous Quality with Visual Studio 2012 (deck)
A deck covering software quality related topics supported by Visual Studio 2012.
and the PowerPoint web app viewer…