I seriously spent a whopping 5 minutes trying to filter the issue list to get a good idea of what was being worked on, what was outstanding, and what was planned and basically can't see the right combo to do this (open just doesn't work).
In any case, there are 39 active work items from what I can tell (52 total, 11 fixed, 2 closed). We're not going to get them all done for release and CodePlex doesn't have a way to prioritize features. So the question is what's the list in order that
we should knock off?
If you guys have worked in an Agile fashion before, having the list prioritized by the product owner (I'm assuming Phil here) is key. It basically means here's our items in the order the PO wants them, grab one and take ownership, finish it, and move on.
Do we have such a list or can one be put together (or is there a magical combination of clicks to get the issue tracker to display this).
Sep 16, 2010 at 3:40 PM
Edited Sep 16, 2010 at 3:41 PM
We’re still working out all the details of the development process. There’s a lot going on right now with the impending launch so I beg your patience.
So far, we’ve defined a rough triage process we’ll use until we get a more detailed process in place:
When we hold triage, we assign items either to the next release, or to a holding “triage” release. The filter you should be looking at for new work items is:
Release: Triaged (if none are triaged, then
All or unassigned)
Assigned To: Unassigned
As I mentioned above, if there are no work items in the “Triaged” release, that means we have items that haven’t been triaged. We’ll be holding regular
triage meetings to try to keep that under control.
For example, I see 7 work items that are not yet triaged.
However, if there’s something that’s not yet triaged that you want to work on, start a discussion and we can triage over email.
There are two items that strike me as good starting points for you Bil.
http://nupack.codeplex.com/workitem/22 which I just now assigned to you.
http://nupack.codeplex.com/workitem/51 might be a good one as well since I believe you expressed interest in these two.
I’ll try to write up a more detailed proposal soon for how I think we should run our agile/lean style process.