This has been on my mind a lot lately. I feel like our process is
very fast and accomplishes the right things, but I don't have much
to compare it to. It'd really mean a lot to me to know your
company's design process and to gather any feedback you have on the
process I outline below. I'm looking for ways to improve what we
So here's how we do design at onegreatfamily.com:
We are a small company, we have 8 developers. We consider ourselves
an "Agile/Scrum" shop. We have 2 designers, one assigned to the
windows app and one assigned to the website.
While looking interaction design in an agile context, I'm constantly
coming across a certain very landmark public discussion from 2004
between Alan Cooper and Kent Beck (of Extreme Programming) mentioned
across the web. It seems this was a very insightful discussion and I
am very curious to read it.
What are your experiences in an agile environment? What has worked for
you and what hasn't?
My organization is considering employing agile, and I tend to be of the
opinion that UXD needs to be at the forefront of the process thinking
about things holistically - then breaking the project into chunks that
will eventually result in a complete user experience.
I would like to know if anyone out there has any experience working with the Scrum Project Management and how it ties in with the whole design process (starting from site maps and wireframes to visual comps).
Scrum (for those of you are not aware of it) is a more start up like management style where there is more of emphasis on collective responsibility (as opposed to responsibility of the proj manager). Also, in Scrum the work requirements, development and QA happen side by side (as opposed to one after another). So basically, you work on smaller pieces of the puzzle.
What are your thoughts on Interaction Design and the Agile Environment?
Here’s my experience of how extreme programming and design mix:
1) Product requirements are one thing today, another tomorrow, based
mainly on strategic (not user) feedback
2) Weekly iteration cycles allow 4-5 days for research, prototyping
and documentation of design
3) Little time is left for contextual inquiries - the product becomes
the "company’s" vision rather than the consumer’s asked-for solution
4) “Featuritis” is a full-blown epidemic
5) Redesign of the entire syste
We are in the discovery phase of the project, where we have absolutely no
idea what the user needs are. There is limited time and resources this we
cant conduct ethnographic studies. What would be the best set of "agile"
methodologies that can be used to start the process?
What are the opinions here about what comes first, the Design or the
I am currently designing a web application from an existing windows
application. No decision had been made at the time as far as the technology
to be used, only that it would be a web application. So I designed like I
normally do, I composite/mock up designs in Fireworks, and then build the
our prototypes to users and have received a lot of great feedback and
Development has now decided to use Adobe Flex for the front end.