My team is in the process of writing user stories. UxD team member is part of the team and is going to interact with PO to come with Wireframes. TheMessage 1 of 53 , Sep 6, 2009View SourceMy team is in the process of writing user stories. UxD team member is part of the team and is going to interact with PO to come with Wireframes. The application is desktop based interactive application.Can anyone point the best practices followed in coming with wireframes with minimal re-work during the sprint.Other point which I want to bring up is after the User story is written and wireframes done then only we are planning to do the story point sizing. Any other suggestion would be helpful to refine the approach.My role is Scrummaster in the team.
Date: Sun, 6 Sep 2009 00:41:09 -0700
Subject: Re: [agile-usability] Valuing stories
On Sun, Sep 6, 2009 at 12:35 AM, Adrian Howard<adrianh@quietstars. com> wrote:
> On 6 Sep 2009, at 01:06, George Dinwiddie wrote:
>> Improving the user experience can be a story. But for it to be a
>> it has to drive all the way through to functional software. Doing
>> prototypes is just a task. It don't mean a thing until it gets
>> in the code.
> Personally I find user stories that just focus on UX improvements a
> little bit of a personal red flag. Like refactoring cards they're a
> sign that we've gone down a bad route for long enough that we can't
> fix something in-story.
> When I start looking at the underlying reason we're having UX-only
> stories I often find that we've not been paying enough attention to
> the UX when it comes to the definition of done-done.
I think the UX element has two sides just like everything else. There
is the customer feedback/market research aspect, which is primarily a
business concern. Then, there are the technical concerns: What happens
if I click this button? Does that make sense? consistency,
look-and-feel, etc. Those are responsibilities of the technical team,
with vision and direction provided by business. Regardless of which of
the two we are talking about they are both elements of each and every
story and not stories into themselves.
One blink is all it takes for the world to change. One click and MSN India helps you catch up Try it!
... I think that they re probably an orthogonal dimensions myself. I ve met people who make very good decisions about the design of the code/ ux - but are notMessage 53 of 53 , Sep 11, 2009View SourceOn 6 Sep 2009, at 21:27, Hassan Schroeder wrote:
> On Sat, Sep 5, 2009 at 8:31 PM, William Pietri<william@...>I think that they're probably an orthogonal dimensions myself. I've
>> .... In fact, teams are doing design all the time. The choice
>> isn't between designing and not designing; it's between designing
>> and designing poorly.
> Or between designing consciously and designing unconsciously,
> the latter being fairly close to "not designing" :-)
met people who make very good decisions about the design of the code/
ux - but are not really able to articulate the reasoning behind them
This can be problematical since their decisions can sound arbitrary to
others - even when they're really good decisions.
http://quietstars.com - twitter.com/adrianh - delicious.com/adrianh