Don’t be too hard for agile; How to go lean with hardware

I am Moriya Kassis

Hello!

Product Management Consultant and Senior Venture Associate @

Why is this ME standing on this stage and talking about this subject?

“

We are at the beginning of the re-rise of Consumer Electronics, when the problem of

unifying development lifecycles is fast becoming

the biggest impediment of innovation.

Agile = Decision Model

Are you doing the right product?

Are you doing the right product?Are you doing the product right?

Agile methodology makes it possible to improve upon an original HW design

without significantly increasing spending and time required.

The Don’ts:

Don’t talk SW with your mouth full of

HW: 1

Get ready to learn some new techniques and try to enjoy leaving your agile SW experience aside

Don’t have MacGyvers in your

team:2

Developers should work in pairs to reduce the time needed for training and documentation. Mix the firmware and the hardware geniuses to work together

Don’t forget the certifications:3

Make sure to get started on necessary certifications early, and skip the nice-to-haves

But it’s easier to tell you what not to do, than...

The Dos:

Finite Iteration:1

Break down the elements of your separate prototypes further, and iterate on the most discrete units of functionality that you can.

Do a majority of the people you ask to play with your prototype tell you that the button is awkward? Getting buttons with the right click-feel is one discrete element to iterate on.

A digital

A digital

or a physical component?

What shape of a button?

What shape of a button?

Do a majority of the people you ask to play with your prototype tell you that the button is awkward? Getting buttons with the right click-feel is one discrete element to iterate on.

Button placement is another one.

Button placement is another one.

Button placement is another one.

Button placement is another one.

Separate Prototypes:2

Make 2 different objects -

Separate Prototypes:2

Make 2 different objects –an ugly black box ‘works like’ prototype,

Separate Prototypes:2

Make 2 different objects –an ugly black box ‘works like’ prototype,and an entirely non-functiona‘l looks like’.

Re-define the term demo-able component. Every single time:3

An iteration is a product version somewhere between a “virtual product” through to a “ready-to-trial prototype”

Similarity to the final

component

actual subsystem

Ease of development

Spectrum of options for a subsystem

Similarity to the final

component

actual subsystem

Ease of development

Spectrum of options for a subsystem

Spectrum of options for a subsystem

Similarity to the final

component

actual subsystem

Ease of development

Similarity to the final

component

actual subsystem

Ease of development

Spectrum of options for a subsystem

Fast Over Fancy:3

There will always be newer-faster-better tinkering toys, and you can spend forever researching them. Instead, find things that work and use them to build a functioning prototype.

“

People care about whether you’ve made something that

they want

Make tradeoff:4To be able to plan after you demo’d the previous one, make tradeoffs in terms of: Frequency of Integration Depth of integration Fidelity of feedback

Any questions ? Moriya Kassis

Now go and break things.