When its ideal time to close any stories if Dev and QA sprints are separate ?

[shre at]

We want to keep Dev and QA sprint separate.

• Can someone help with best practices to be followed ?
• Also when we should close any story in this case?

We are planning to mark story Dev complete once it is Ready to move to QA. Once all stories of Dev_sprint 1 is Ready to deploy to QA, dev can close sprint. And when it will be Ready to move to production that should be the done stage for QA sprint. And at this point QA_sprint 1 closes.

• So for UAT the story should be in backlog? As per workflow we don't want to close story until it is deployed to production successfully.
• Please suggest what is the ideal way to manage. 

[Deleted user]

Hi @shre at

I have a few questions around your current model;

1. Do you currently have 2 issue types (one for a Dev Story, and another for QA Story)?
2. How are you setting up your sprints currently?
3. What are your devs doing during the QA sprint?
4. What are your testers doing during the Dev sprint?
5. How much time do you allow for your sprints currently?
6. What does the workflow look like?

I could explain some best practice but until I properly understand your sprint set up I would then be able to tailor my message to yourself and your organisation.

Thanks

[Tom Lister]

Hi @shre at 

I echo @[deleted]  comments

This is a matter of modelling your process coupled with good practice.

even though dev is regarded as complete by a developers definition of done, this may be queried during QA and pushed back to Dev.

Hard to define without knowing your process or Definition of Done.