Open activedecay opened 11 years ago
Your question is a deep philosophical one, so let's break it down.
WHAT IS AN ISSUE? Issues should either
OK I CREATED WHAT I THINK IS AN ISSUE After creating an issue, we should talk about it to make sure that it covers one and only one feature that the customer will see. For instance: "Add a page that lets the user change their password and email". Sounds deceptively like one issue, but is actually two: change password, and change email. That would be two issues.
OK ITS REALLY ONE ISSUE THIS TIME Once we agree that the issue is one thing, and the details of the issue are clear, then I can start implementing the feature described in the issue.
WHAT DO YOU DO NEXT? I work on the issue until it's coded, however the issue is not done.
WHAT IS DONE? https://startpage.com/do/metasearch.pl?query=definition+of+done Definition of done is crucial to an effective team.
ARE YOU AN EFFECTIVE TEAM? ... see Oblivion, the 2013 movie.
ARE WE DONE YET When the issue is done, "meets our definition of done", then we can close it.
So when you open an issue....what do you do next?