Re: [agile-usability] Re: where do your UX team-members sit?
That's a good point, Nick. Given that I'm a consultant, we usually get called in to help with new projects. We haven't had to help out with existing products (and their pre-existing constraints) that much. And when we do, our approach tends to find new and better directions to take the product, so they kinda start from scratch and reinvent their product.
From what little work we've done to dress up existing products, our approach seems to mirror yours.
--- On Sun, 12/5/10, Nick Gassman <netwiznick@...> wrote:
From: Nick Gassman <netwiznick@...>
Subject: [agile-usability] Re: where do your UX team-members sit?
Date: Sunday, December 5, 2010, 4:24 PMWhat Larry descrubes is actually quite similar to our approach, although the amount of up front design required depends on the nature of the project. If it's an entirely new application, or a significant development of an existing one, we'll spend some time on it prior to the Agile team being fully constitued.If the project is an incremental development, then we might engage with the development team right away. Our deliverables are hi-res designs which leave no ambiguity or room for interpretation on design. The are though always questions and suggestions from the developers which benefit from the embedded UX person once they are working on the project.Nick
I work at a medium sized company. We have three designers and five developers, all who sit in close confines. From reading the posts lately I wonder if we handle design and development differently.
It seems (and I may be horribly wrong) that the arguments are mainly against big, up front design. I absolutely agree. However, I don't think that having designers do designs prior to development is a bad thing, if done well and there's plenty of communication.
We have one month release cycles, which means we're getting real, working software into our clients hands very quickly, and get feedback quickly as well. We do paired design, so two designers will sit down and shake out most of the design. This can take anywhere from a day to a week and a half depending on the size of the story. During this time we meet with developers several times so they know where the design is going, point out technical road blocks, and yes, give design input. Then we hand it over to get coded, and during this time the designers work closely with the developer who's handling the story to answer questions and work out real time design questions.
So the designers do a bulk of the design (I'd say 95%), but there's no huge outlay of up front design. We do it all 'just in time'. Designs get input from developers, product owners, and other stakeholders. The mock up's may go through three or four iterations before they reach development, all within a few days time.
I'm not saying that developers cannot design, I think many can to varying degrees. We've just found that paired design done just prior to development, and working in close proximity to each other has allowed us to create great designs quickly.
On 12/4/10 4:33 PM, Tref Gare wrote:
Our environment is the opposite – we huddle our ux folk together which does give us the cross pollination thing, but means we miss out on the embedded engagement with the developers. I’d love to find some form of middle ground where I get to regularly mind meld with my design colleagues, but also am in there with the devs when the design hits the metal.