software innovation – principles and tools

Post on 22-Feb-2016

27 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

Software innovation – principles and tools. Daniel Lux. Who am I?. German citizen Computer scientist from Groningen University Co-Founder of Seluxit Seluxit specializes in Smart Grid Smart Home Wireless technologies. Case: A new wireless protocol. Before the project. - PowerPoint PPT Presentation

TRANSCRIPT

Software innovation – principles and toolsDaniel Lux

• German citizen• Computer scientist from

Groningen University• Co-Founder of Seluxit• Seluxit specializes in

• Smart Grid• Smart Home• Wireless technologies

Who am I?

Case: A new wireless protocol

Develop a next generationwireless protocol

• Secure• Robust• Future proof• Generic• State of the art

Customer can only describe how it should

not be

Customer knows it should be better than

the current solution

Before the project

Define:• State of the art• Minimal success

feature set• Desired complete

feature setIterate:• Communicate all

results, good and bad

• Set ambitious targets

Case: A new wireless protocolIteration 0

SurveyWhat is state

of the art now?

ImproveSet high

targets in order to innovate

Planshort

timeline for sense of urgency

OfferFixed budget,

fixed time, flexible scope

Develop:• HW & SW in parallel• Simulate & test• Integrate• ReleaseIterate:• Time boxed• Working prototype• Avoid

interdependencies

Case: A new wireless protocolIteration X

HW Plan Develop Test Integrate

SW Plan Develop Test Integrate

Case: A new wireless protocolResult

From 1st idea about project with 2 pages of features

4800 Man hours of work where the specification and the Hardware were developed over the period of 18 Month

• 3 international patents filed

• Working software stack

• Working hardware

• Protocol is now ready for market

• Speed is critically important

• Divide and conquer• Focus on high-value tasks• Create real customer value• Build effective teams• Lead from the back

Strategiesthat work for us

• Customers using stringent development models

• Big projects with multiple developing parties slow the process down

PitfallsWhere this approach reaches its limits

Questions?

top related