Yet Another New Product Development Game?
2015-01-19 19:32:38 GMT
I’ve been trying for over a year to equate Agile and Lean Thinking with other ideas and knowledge areas of product development. From my point of view agile and lean are essentially about product development but it’s been really hard to argue this to people from other areas, specially UX Design and some Product Managers.
Designers (at least the ones I work with) seem to focus much more on the differences between Agile and Design Thinking than on their similarities (which I think are numerous). The aspects that I’m having more trouble with designers relate to: a) being on the same team as developers; b) sharing responsibility for the whole product/process; and c) specialty vs multidisciplinarity
In The New New Product Development Game (1986), Takeuchi and Nonaka talk about how product development was like at big successful multinational companies. It is a great inspiration to me but I haven’t found any recent examples that play the game like they said. I took a few paragraphs from the article to illustrate my points. I would love to know if there is a Yet Another New Product Development Game that I’m unaware of.
a) Begin on the same team as developers
‘Under the rugby approach, the product development process emerges from the constant interaction of a hand-picked, multidisciplinary team whose members work together from start to finish.’ (Takeuchi & Nonaka, 1986)
I’ve heard time and again from designers and non-designers that ‘designers want to work with designers’. At my company we have two design ‘teams’: Web/Graphic Designers and UX Designers. Everyone in both of these ‘teams’ prefer working in a waterfall fashion where their specialized group produces artifacts which are then consumed by a real multidisciplinary Scrum development team responsible for everything from then on (get the features to production).
So my questions to you guys are: have you ever worked with a real multidisciplinary team including every specialty needed to deliver a product on the same team (designers)? How did that work for you? What works and what doesn’t? Is it something worth fighting for? How designers feel about it? How can I get designers to believe in this model?
I won’t address aspects b) and c) for now so we can focus on aspect a)
Any help is very welcome!
To Post a message, send it to: SCRUMDEVELOPMENT <at> eGroups.com
To Unsubscribe, send a blank message to: SCRUMDEVELOPMENT-unsubscribe <at> eGroups.com