41631 lecture 3 pt1 tech entrepreneurship methods
TRANSCRIPT
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
1
Agenda 19-02-2013
08:30 – 09:00 Technology Entrepreneurship Methodology
09:00 – 09:10 Lean Startup – a quick introduction
09:10 – 09:25 Break
09:25 – 10:05 Lean Startup – Description of central concepts
10:05 – 10:20 Break
10:20 – 11:00 SCRUM – Part 1
09:10 – 09:25 Break
11:15 – 11:55 SCRUM – Part 2
Building a business
Technology entrepreneurship methodologyJakob Bejbro [email protected]
Unless otherwise stated, this material is under a Creative Commons 3.0 Attribution–Share-Alike licence and can be freely modified, used and redistributed but only under the same licence and if including the following statement:
“Original material by Thomas J. Howard and Jakob Bejbro Andersen for course 41631 – Innovation and Product Development Department of Mechanical Engineering, The Technical University of Denmark”
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
3
The special case of ”Technology Entrepreneurship”• Entrepreneurship in general can be characterised as:
The identification, development and exploitation of opportunities by single persons (entrepreneurs).
• Technology entrepreneurship is a subset characterised by being highly dependant on technology for creating value.
• The development of technology into commercially attractive products/services is described well in literature (innovation).
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
4
Prerequisites for Innovation methods
Knowledge
Organisation
Responsibilities
Development
environment
Customer
proximity
Level of
repetition
High levels of knowledge founded in staff and data management systems
Well established organisation with departments aligned to company functions.
The business development task is divided into sub-tasks placed in departments.
The relations between the development’s stakeholders are well known.
Customer dialogue is handled by the sales department
Similarity between development projects is likely to be of a high degree.
Incufficient knowledge, perhaps specific to certain fields (the advantage?).
Restricted to roles. No hierarchy.
Ad-hoc or vaguely defined.
Cross-disciplinary. Teams often lack necessary knowledge and competencies.
Customer is (or should be) closely coupled to the development
Most tasks are solved for the first time. Importance of tasks changes over time.
ESTABLISHED STARTUP
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
5
IPD: In an established company
$
Market
Product
Production
Need(situation)
Well-known relations
Well-known relations
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
6
IPD: In a startup
Market
Product
Production
Need
(situation)
???
?
?
??
??
??
What now?
What now?
What now?
- Increase ROI - Improve Value prop. - Mitigate risk - …
$
… So, why do we need the development log?
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
7
A tool to match the task at hand• The tools deployed need to reflect the nature of the task.
Contextual setting
Established company Startup
Prerequi-sites
Tools available(in Engineering Design)
• Stage Gate Model• Lean• SCRUM• Total Quality
Management• Gantt Charts• Product Architectures &
Platforms.• … and many more!
• Lean Startup (to follow)• … and a few
derivatives.
• High degree of certainty.• Good knowledge
coverage.• Focus on product costs.• Plannable progress.• Sufficient resources.
• Low degree of certainty.• Large gaps in knowledge. • Focus on effectuation.• Ad-hoc / bricolage
oriented process.• Few resources (time, $).
?
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
8
A closer look: The Stage Gate Model*
• What is required to execute the stage gate model?
• How well does the model handle changes in the surroundings?
• Does it operate well when there are gaps in team’s knowledge?
Spend 5 minutes discussing the questions
* Robert Cooper, A process model for industrial new product developement, IEEE: Transactions on Engineering Management, Vol. EM-30, No. 1, February 1983
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
9
ED and Tech Entrepreneurship
Good matchPoor match
Stage gate
model
Lean Startup
Gantt Charts
SCRUM
Product architectures & Platforms
Product/Service-Systems
Model developments / tweaks
Stage gate
modelGantt Charts
Product architectures & Platforms
Product/Service-SystemsSCRUMLean
Startup
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
10
The Development Log
The DL is a tool for: • Navigating and managing complexity.• Prioritising tasks.• Handling team resources.• Specifically designed for the entrepreneurial process.
The DL is not:• A tool prescribing approaches and solutions.• Specific to engineering design.
2013Original material by Thomas J. Howard & Jakob Bejbro for 41631: Innovation in Product Development Department of Mechanical Engineering, Technical University of Denmark
11
Questions?