Peirre Roberge wrote:
>> 2) Engineering-Focused (4 months): Agile programming team develops
>> the product using the prototype as a target, with occasional light
>> input from the design team but mostly focusing on solving and
>> innovating tech solutions. Expose the development product
On Feb 12, 2008, at 3:53 PM, Alan Cooper wrote:
>> I'd love to hear what people think of this approach, especially if
>> you've tried something like it. I'm pretty confident in it, at least
>> for now.
>
>
> Christopher,
>
> Which one do you throw away?
>
> Thanx,
> Alan
I wouldn't throw an
For those of you on the list who missed Alan's keynote, there's a transcript
here: http://ajaxian.com/archives/interaction08-ixds-in-savannah-alan-cooper
-g
Welcome to the Interaction Design Association (IxDA)!
To post to this list .
Then if you're able to educate your colleagues, get them on board as
you say, you're doing the right thing. We heard a lot over the weekend
about relationships between designers and engineering. I feel this is
way more important than what methodology is used. Simply throwing
things over the wall to
Datagrids are the evil demonic spawn of feable minds and people of
small souls!!!
Time to design a data grid. Maybe they will let me alternate row
colours!
will evans
user experience architect
[EMAIL PROTECTED]
617.281.1281
On Feb 12, 2008, at 5:09 PM, Kevin Silver <[EMAIL PROTECTED]> wrote
On Feb 12, 2008, at 5:06 PM, Jeff White wrote:
> On Feb 12, 2008 1:37 PM, Scott McDaniel <[EMAIL PROTECTED]> wrote:
>> In a strict display sense, this is the single most common phrase
>> I've heard from
>> engineers/programmers about design:
>> "Why not just throw it in a data table and be done
On Feb 12, 2008 5:06 PM, Jeff White <[EMAIL PROTECTED]> wrote:
> On Feb 12, 2008 1:37 PM, Scott McDaniel <[EMAIL PROTECTED]> wrote:
> > "Why not just throw it in a data table and be done with it?"
> >
> > Scott
> What's the issue with that? Kidding...
>
> How have you handled the situation?
>
> Jef
exactly!
On Feb 12, 2008, at 3:01 PM, W Evans wrote:
> True Scott - which is why brainstorming and prototyping by IxD
> people should
> be done first!
>
> If everything was thrown in a data table - we would never have the 3-d
> flip-book carousel to page through our CDs on our iPhones. Lotus
Scott,
Too funny and timely. A few unlucky souls over the weekend in Savannah
had to endure my rant against Data-Grids. I just reviewed a flex
application for a client that relies heavily on data-grids, we're
going to be fixing that because it just doesn't work in their
situation. To top
On Feb 12, 2008 1:37 PM, Scott McDaniel <[EMAIL PROTECTED]> wrote:
> In a strict display sense, this is the single most common phrase I've heard
> from
> engineers/programmers about design:
> "Why not just throw it in a data table and be done with it?"
>
> Scott
>
What's the issue with that? Kidd
True Scott - which is why brainstorming and prototyping by IxD people should
be done first!
If everything was thrown in a data table - we would never have the 3-d
flip-book carousel to page through our CDs on our iPhones. Lotus 1-2-3 came
out 25 years ago - we might think about innovating once in
In a strict display sense, this is the single most common phrase I've heard from
engineers/programmers about design:
"Why not just throw it in a data table and be done with it?"
Scott
On Feb 12, 2008 11:40 AM, Christopher Fahey
<[EMAIL PROTECTED]> wrote:
> On the subject of Alan Cooper's keynote,
how they
depend on oily hands and long apprenticeships." -Libby Purves
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christopher Fahey
Sent: Tuesday, February 12, 2008 8:35 AM
To: [EMAIL PROTECTED]
Subject: Re: [IxDA Discuss] Fwd: Thoughts on
]>
Date: Tuesday, February 12, 2008 11:35 am
Subject: Re: [IxDA Discuss] Fwd: Thoughts on Alan Cooper's Keynote
To: [EMAIL PROTECTED]
> On Feb 12, 2008, at 11:04 AM, Cagwin, Virginia wrote:
> > Like David mentioned, interaction design must come first. It's the
>
Dan wrote:
2) Engineering-Focused (4 months): Agile programming team develops the product
using the prototype as a target, with occasional light input from the design
team but mostly focusing on solving and innovating tech solutions. Expose
the development product regularly to a small user
1) Strategy- and Design-Focused (4 months): Thoroughly design a version
1.0 prototype and test it with real users. No tech development. Just
collect requirements and design something that meets a business strategy
and delivers an awesome user experience. Identify the technological
needs, but don't
This reflects my view on it as well. After all, we did have a seminar
called "User Interface Design in an Agile Environment",
which my limited understanding seemed to speak to including engineers
earlier in the process, if only for 'buy in', 'ownership'
and other buzzwords. The designer in questi
On the subject of Alan Cooper's keynote, did he provide any clarity
on his assertion a few months ago that it is the norm for engineers
to start coding without having done even one second of thinking about
design? Not just neglecting to do any interaction or UX design, but
not doing any cod
I spent most of last year at Salesforce.com as the UI Manager trying to
understand Agile, and how UCD fits in to it. There was a lot to like about
the methodology, and a lot to dislike. I think that at it's core, Agile
tries to recreate the best of what we all aspire to at startups or on small
te
On Feb 12, 2008, at 11:04 AM, Cagwin, Virginia wrote:
> Like David mentioned, interaction design must come first. It's the
> only
> way I found a project to work successfully.
Interestingly, I am about to begin Phase 3 of a major project with
the following phases, each of which slightly overl
David and Jared, I agree with you both. I'm rolling onto my second agile
project, after 3 years of learning what worked well, failed and how to
recover quickly to still get the product completed, but not on time. We
are using Feature Driven Development (FDD) method.
Like David mentioned, interact
Not being privvy to the IxDA Summit and Keynote speakers, I think Agile can
work very well with Design embedded in, and I've worked in 4 places that did
it welll and 2 that did it like crap.
The companies that did it well were not "Agile Maniacs", meaning they took
what worked with the process and
-- Forwarded message --
From: mark schraad <[EMAIL PROTECTED]>
Date: Feb 12, 2008 10:00 AM
Subject: Re: [IxDA Discuss] Thoughts on Alan Cooper's Keynote
To: David Malouf <[EMAIL PROTECTED]>
On Feb 12, 2008 9:43 AM, David Malouf <[EMAIL PROTECTED]> wrote:
> Design is cultural t
23 matches
Mail list logo
