QA story walkthrough with developers helps a lot in agile methodology.

We always dream of making things simple and easy. Yep me too believe in those words. But for a QA this is nightmare when the D-Day of Sprint arrives. QA will always busy in execution day and night, retesting, regression, scripts and a lot...

Now let me suggest something that can make your life more simple in agile methodology as a QA. A walkthrough on the story once the story is assigned to a developer. 

Now whats this? Here you are gonno discuss with the story owner (developer) on the pros and cons and your understanding on the story. Also have some checklists prepared before you meet him as it can be crazy. 

Walkthrough meeting with developers

Before you meet the developer, 

• read the story, analyse it from the QA perspective and understand its risks and impact.
• check the test oracles and available test documents (use cases if any).
• prepare a checklist (simple handwritten one).

Now once you meet your customer (developer) :)

• Ask him/her each and every question and his views on the story.
• Please refrain from asking how he is developing it unless and until you are a technical test analyst or tester (becoz this will drive away the show to a different bucket).
• Please put in your concerns and the end results you will be looking for in a very brief manner.
• Check your checklist and share the same with the developer.

Once you come back for preparing your TC's or TPlans.

Quality Bugs

If possible try to have a softcopy of the checklist in place as this might help you out later. Then start with your test cases (TC's) or Test Plans (TPlans) to drive your show.

This is the one I have applied in my projects and I have found it very impressive and efficient. Atleast you could always rely on the quality of bugs that come up later rather than increasing the quantity.