Does your organization have difficulty defining 'done?'  Do you find that the various stakeholders each have a different understanding of what 'done' means?  Do you ever feel as though the completion criteria are an ever moving target? Does the team ever declare code 'done' only to have the product manager, product owner, customer, or testers reject it?

If so, you are not alone. The good news is that you have the power to improve your situation.

Bring your frustrations, challenges, and problems with defining "Done" to this working session. We'll work together to find practical solutions that fit your context. Specifically, we'll use proven techniques and frameworks to:

• Understand what gets in the way of defining Done in your context.
• Discover how to gain agreement about what Done means.
• Define what Done means in concrete, testable terms.
• Tap into the wisdom of the group. Anyone who has struggled with a problem has valuable insights; bringing these insights together often yields effective solutions.

There are several things this workshop will not provide you with. You will not receive The One True Way to Define Requirements. If there is a Magic Wand of Instant, Perfect, Unambiguous Completion Criteria, no one has shared it with us. You will not walk out of the session with the Only Requirements Elicitation, Analysis, or Management Tool You'll Ever Need (unless you count the one between your ears).

Instead, this session will give you techniques for discovering possibilities and a renewed appreciation for your own innate ability to work through the every day challenges of defining what Done means in your context.