Ths is my first post here, so I thought I'd toss out a question that addresses an issue I am currently working on. I work on a agile team where the devs use Tracker to account for their velocity. As the UX + UI designer on the team, I also have a separate project for my work. However, the methodologies and deliverables between development and design aren't exactly the same. This makes it a little challenging to use Tracker to the same effect, but I'm hoping to come up with a great solution.
I've recently implemented an approach of writing a story for each deliverable, rather than each feature. For example, (let's say the application has an Admin user interface and an External user interace) if an Admin user should be able to show/hide a piece of content to an external user, I would write stories for:
the userflow and wireframes showing where the Admin finds this feature, how they use it, what it does, and where it surfaces to the External user
the Admin form where there is a check box (or slider button/other) for the show/hide feature
the supporting help text popover screen that explains this feature to the Admin
the External user screen in two states - content shown and hidden.
After the stories are written, I can then assign a point value to determine how much time it will take to complete each piece. My current point value set up is from 1 - 5, where each point is equal to 1 day's worth of time (i.e. 2 pts = 2 days).
This way, I can deliver against the required deliverables to account for design velocity and time put it takes to do the work. So far, this is the best way I can think of to use Tracker for UX. If you're using tracker for your UX/UI/design projects, what are you thoughts? Do you have any methods to share?