[Sigia-l] How the design process fits into the agile methodology

[Jacqui Olkin]

Oops, I hit "send" too early before.

Ziya said:
>As I always say, framing of the problem is everything. It doesn't matter
whether agile or some other methodology allows folks to solve a problem more
effectively, if the problem solved (strategy) happens to be the wrong one.

I say, that's a pretty safe argument. You always need to start with a good 
idea--whatever methodology you use.

But, with an iterative, tightly integrated methodology such as agile (or 
design-build), you are likely to find out faster where the weaknesses in 
your original strategy are and be able to address those.

Over n' out.

J.


Jacqui Olkin
Olkin Communications Consulting
jacqui at olkincommunications.com
571-643-6020 ph.
703-834-5653 fax
www.olkincommunications.com

web . print . content . strategy





>From: Ziya Oz <listera at earthlink.net>
>To: <sigia-l at mail.asis.org>
>Subject: Re: [Sigia-l] How the design process fits into the agile 
>methodology
>Date: Sun, 18 Feb 2007 21:17:47 -0500
>
>Jacqui Olkin:
>
> > "At regular intervals, the team reflects on how to become more 
>effective,
> > then tunes and adjusts its behavior accordingly."
>
> > Is this not a strategic behavior?
>
>Not to me. "Becoming more effective" is not strategy in the way I'm 
>thinking
>of design as business strategy. This is the reason I earlier cited steps 
>1-3
>of a 30-step agile process. If the framing of the problem is done in step 0
>(that is, before the agile process even is given the go-ahead), the
>direction (and thus the possibility of eventual success) of steps 1-30 have
>already been defined to a large extent. "Becoming more effective" within
>those 30 steps may or may not amount to success because of step 0.
>
>Actual illustrations of these can be seen in many of the iPod-killer
>attempts over the last 4-5 years. Every single one of those development
>processes could have been done via agile methods and effectively, in the 
>end
>it probably would not have made much of a difference, because their overall
>strategy of competing against an end-to-end system like iPod/iTunes/iTMS 
>was
>fundamentally flawed.
>
>As I always say, framing of the problem is everything. It doesn't matter
>whether agile or some other methodology allows folks to solve a problem 
>more
>effectively, if the problem solved (strategy) happens to be the wrong one.
>
>----
>Ziya
>
>When 2+2=4, it's development,
>When 2+2>4, it's design.
>
>
>
>------------
>IA Summit 2007:  Enriching IA
>Rich Information, Rich Interaction, Rich Relationships
>March 22-26, 2007, Las Vegas, NV
>www.iasummit.org
>-----
>When replying, please *trim your post* as much as possible.
>*Plain text, please; NO Attachments
>
>Searchable Archive at http://www.info-arch.org/lists/sigia-l/
>
>
>
>
>________________________________________
>Sigia-l mailing list -- post to: Sigia-l at asis.org
>Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l

_________________________________________________________________
Don’t miss your chance to WIN 10 hours of private jet travel from Microsoft® 
Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/