These are the slides from Nir Klein's workshop at Product of Things Conference in Tel Aviv on July 2018: Who this workshop is for: This workshop is for those who have little to non-background in hardware technologies and want to get a better grasp on the interface between the Product and the R&D roles during the development of IoT products, with emphasis on startups and small companies After this workshop you will be able to: - Understand the R&D applications of IoT must-features - Plan a PRD for a theoretical product - Guide your product and R&D teams on how to better work together, leading them to build better software and hardware product components What is covered: - Product and R&D roles - Limitations of a startup and how it affects the product’s definitions - The Required technological disciplines to develop an IoT hardware product - Guidelines for planning your MVP and PRD - What should PRD for IoT hardware product look like - Case studies and common mistakes In this workshop, Nir brings first-hand experience on successfully leading product and R&D teams, overcoming their differences (both technical and not), and bringing them together with the aim to make better IoT products

1. Workshop by Moriya Kassis
Build your first IoT device
The tricky interface of Product and R&D
Workshop by Nir Klein,
Tech Consultant

2. About me
2
linkedin.com/in/nirklein
Nir Klein, IoT Tech Consultant
nir@iotchefs.com

3. Why should we discuss it?
3

4. GOALS
▰ Product <-> R&D
▰ Better Products
4

5. What’s the plan?
1. PRD Guidelines
2. MUST requirements
3. How do IoT developers think?
4. Hardware “vs” Software
5. Create our own PRD
5

6. PRD Guidelines
Building our Product Requirements
Document
6
1
PRD Guidelines
MUST requirements
How do IoT developers think?
Hardware vs Software
Create our own PRD

7. Main PRD Categories
● Story
● How it works
● Hidden expectations
● “Boring” but important
7
● Future Extensions
● Markets and Financial
● Environmental

8. What’s your story?
8
Product
Description
Stakeholders
Usage
Scenarios
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

9. How it works? How the user interacts with it?
9
Modes
of
Operation
UI / UX
+
OnBoarding
External
Interfaces
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

10. Expectations that won’t be mentioned
10
Wireless
Comm
Energy
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

11. “Boring” (not really) but important
11
DFM Mechanical Serviceability
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

12. Future Extensions
12
Connectivity
and
Security
External
Sensors
And
Devices
UI
Extensions
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

13. Markets and Financial
13
Target
Markets
Target
Cost
Target
Price
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

14. Environmental and Regulations
14
Env.
Storage /
Operation
FCC / CE / UL
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
PRD Categories

15. Mitigate risks in advance
15
If things goes smooth,
it means you missed something…
BE PREPARED!
Story
How it works
Hidden expectations
“Boring” but important
Future Extensions
Markets and Financial
Environmental
*Mitigate Risks
K
I
S
S
eep
t
imple,
tupid!
PRD Categories

16. MUST Requirements
MUST-have requirements that you better
not miss for your launch
16
2
PRD Guidelines
MUST requirements
How do IoT developers think?
Hardware vs Software
Create our own PRD

17. OTA
Known as
OTA => Over The Air (Update)
FOTA => Firmware OTA
DFU => Device Firmware Update
17
Let’s say we develop “smart” bicycle...
MUST Requirements

18. On-Boarding
18
Connect / Pair
“Teach”
Customize
MUST Requirements

19. Security
Device ⇔ Cloud API
Cipher Suites
Secured FW
Authorized Access
19
MUST Requirements

20. Safety &
Materials
Battery
20
MUST Requirements
Materials (Bio-Compatibility)

21. Comm &
Battery life
Rates / Range
Time between replacement or charge
21
MUST Requirements

22. Testability
22
Current
Measurement
RF
Performance
Testing
MUST Requirements

23. How do IoT Developers think?
And what does our requirements mean in
their point-of-view?
23
3
PRD Guidelines
MUST requirements
How do IoT developers think?
Hardware vs Software
Create our own PRD

24. 24
Typical Requirement -
Industrial Design
● Layers
● RF Interference
● “Real Estate”
Z cm
X cm
Y cm
How do IoT Developers think?

25. 25
Typical Requirement - OnBoarding
OS version?
Sub-1Ghz
Enter / leave mode?
How do IoT Developers think?
Don’t start with Android and
say we’ll be fine with iPhone...

26. 26
Versatility vs Cost
VS
UXMemory
Computing power
Sensors
External
Interfaces
How do IoT Developers think?

27. 27
Typical Requirement - Audio
-
+
$ $$
How do IoT Developers think?
DAC
PWM

28. MVP and Future Extensions
Feature set #2
Feature set #1
MVP
How do IoT Developers think?

29. To sum it up
Multidisciplinary
Trade Offs
How do IoT Developers think?

30. Hardware “vs” Software
30
4
PRD Guidelines
MUST requirements
How do IoT developers think?
Hardware vs Software
Create our own PRD

31. 31
Compilation
Differences between HW and SW
Scale up
SW Update
Hardware vs Software

32. 32
Hardware related risks
Scalability
Battery
Life Security
Safety
TTM
Communication
Performance
Hardware vs Software

33. 33
Let’s create
our own
PRD!

34. Create our own PRD
34
Tips:
● Mark issues that need
further technical
investigation
● Plan MVP and Future
features in advance
● Keep it simple

35. THANKS!
Any questions?
You can reach me at
nir@iotchefs.com
+972-50-6521818
linkedin.com/in/nirklein