[bind10-dev] What to do with new tasks

[Stephen Morris]

Following the discussion today about where to put new tasks, I've
created a "New Tasks" milestone and added unassigned tasks created since
the Prague Meeting to them.

For the moment, this is just a housekeeping exercise, but I would like
to propose a simple workflow: all new tasks - defects or new features -
go into the new tasks milestone.  Periodically we can review these items
and decide what to do with them.  (If we do this weekly on the mailing
list, the number of new tasks should be relatively low and it shouldn't
take too much time.)  At present, I see a number of possibilities:

* The task is so urgent that it has to be added to the current sprint.
(AIUI, in Scrum, once a set of tasks is chosen for a sprint, no further
tasks are added except in unusual conditions.  So this should be a rare
occurrence.)

* The task is something that fits our year 3 goals, so is moved to the
year 3 task backlog for inclusion in a future sprint this year.

* The task is low priority, so is moved to the "general" task pool (i.e.
is not associated with any milestone) and will be a candidate for
inclusion at some time in the future.

* The task is rejected.

In this way, instead of creating tasks and just losing them into the
"general" pool, we at least get the chance to review new pieces of work
and are able to make a timely decision as to what we do with them.

Thoughts?

Stephen