Anyone using a tool that organizes UE issues by task, product or theme?

10 May 2010 - 1:19pm
4 years ago
5 replies
690 reads
cgoebel
2010

I'm collecting UE defects, concerns, ideas and need to organize them so that they can be addressed by a designer. Think backlog (details, priority etc) but organized so it works for a designer, not just a developer. I'd love to be able to tag issues so they can be sorted by theme, areas of the site, specific tasks etc. I'd like visibility into trends across a user type, tool or interaction, so we are solving real issues not just firefighting. Excel just isn't cutting it.

What are tool(s) are you using? What's working, what isn't working?

Thanks in advance!

Christina

 

 

 

 

Comments

10 May 2010 - 2:16pm
makabde
2009

Hi Christina,

For collecting, sorting and tagging ideas, images, screenshots; I personnaly use Evernote wich is available on Mac and PC.

A useful feature is the ability to synchronise different computers and even my iPhone with all my notes.

http://www.evernote.com/

Makram

10 May 2010 - 6:00pm
Michael Moore
2008

I haven’t used this, but some clients are, and it looks like a pretty nice system: http://www.pivotaltracker.com/
Plus the price is right. (free)

Michael Moore

On Mon, May 10, 2010 at 12:58 PM, cgoebel <cgoebel@gmail.com> wrote:

I'm collecting UE defects, concerns, ideas and need to organize them so that they can be addressed by a designer. Think backlog (details, priority etc) but organized so it works for a
designer, not just a developer. I'd love to be able to tag issues so they can be sorted by theme, areas
of the site, specific tasks etc. I'd like visibility into trends across a user type, tool or interaction, so we are solving real issues not just firefighting. Excel just isn't cutting it.

What are tool(s) are you using? What's working, what isn't working?

Thanks in advance!

Christina

 

 

 

 

(((Plea
11 May 2010 - 6:50am
community at la...
2006

> I'm working on a Web2/Gov2 project at the moment where I'm using Jira studio from Atlassian, configured with some custom issuetypes that match pretty closely to what you're describing. The costs aren't too bad, depends on how many you intend to have using the instance. See http://www.atlassian.com/hosted/studio/pricing.jsp

Regards,

Brian Hill (Disclosure: I'm an Atlassian consulting partner, but there is no commercial return to me on the use of Studio. I just like the way it's packaged for fast startup and quick cycle times to delivering results with maximum transparency).

>> I'm collecting UE defects, concerns, ideas and need to organize them so that they can be addressed by a designer. Think backlog (details, priority etc) but organized so it works for a >> designer, not just a developer. I'd love to be able to tag issues so they can be sorted by theme, areas >> of the site, specific tasks etc. I'd like visibility into trends across a user type, tool or interaction, so we are solving real issues not just firefighting. Excel just isn't cutting it. >> >> What are tool(s) are you using? What's working, what isn't working? >> >> Thanks in advance! >> >> Christina >> >

11 May 2010 - 8:01am
joelmoney
2010

Version One is what we use at Aol. Takes some getting used to but
overall great for an agile work flow and tracking sprints and stories.

Sent from my iPhone

On May 10, 2010, at 8:16 PM, "Michael Moore" wrote:

> I haven’t used this, but some clients are, and it looks like a
> pretty nice system:Â http://www.pivotaltracker.com/ [1] > > Plus the price is right. (free) Michael Moore On Mon, May 10, 2010
> at 12:58 PM, cgoebel wrote: >> I'm collecting UE defects, concerns, ideas and need to organize
>> them so that they can be addressed by a designer. Think backlog
>> (details, priority etc) but organized so it works for a >> designer, not just a developer. I'd love to be able to tag issues
>> so they can be sorted by theme, areas >> of the site, specific tasks etc. I'd like visibility into trends
>> across a user type, tool or interaction, so we are solving real
>> issues not just firefighting. Excel just isn't cutting it. >> >> What are tool(s) are you using? What's working, what isn't working? >> >> Thanks in advance! >> >> Christina >> >> Â >> >> Â >> >> Â >> >> Â >> >> (((Plea >> > (((Please

10 May 2010 - 6:47pm
bminihan
2007

PivotalTracker is pretty good, in that it lets you tag stories by UI area, role, etc.  It exports to CSV, which lets you re-sort, filter, etc.  It lets you get started quick, and you can get moving even quicker.  Unfortunately, though, it doesn't provide many "alternate working views" beyond "icebox, backlog, current, and finished".  For that reason, I had a tough time using it for "product management" and feature prioritization.

We used a tool called Mingle (http://www.thoughtworks-studios.com/mingle-agile-project-management) at another company.  It's a more full-featured work/feature tracking system than the above, but provides some REALLY nice visualization tools for rearranging and sorting priorities.  I believe it's free for up to five users, but I also think you have to install it yourself (it takes a Gig of memory and needs its own box, practically).  Other than that, I absolutely loved it for everything from high level planning down to bug-tracking.

Lacking the above, my favorite method for roadmaps is still a stack of 3x5 cards.  I keep a stack on my desk, and whenever a feature idea comes up, I jot it down and add it to the pile.  About once a month, I spread them all out on a giant boardroom table, order them if they have an order, then ask sponsors to re-sort the list, and insert new cards into the stack where they feel they're important.  It's an intensely visual and interactive way to plan, yet requires some effort to "get it back online".

Whatever you do, I've learned that the less you write down (or immortalize) on paper or excel, the more you'll be able to rearrange your thoughts, throw away features, prioritize, sort, and plan.  Guess my advice is: whichever tool you use, keep your features simple and flexible, and only write full documentation when you're getting close to execute a story/card/feature.

Good luck.  You're right, that's a tough job, for which few tools are really applicable.

Syndicate content Get the feed