Comments on: How to Write the WebRTC Requirements for Your New Product? https://bloggeek.me/write-webrtc-requirements/ The leading authority on WebRTC Sat, 28 Dec 2019 15:14:29 +0000 hourly 1 By: Or Hiltch https://bloggeek.me/write-webrtc-requirements/#comment-118691 Tue, 13 Dec 2016 08:21:20 +0000 https://bloggeek.me/?p=10947#comment-118691 Great write up. Thanks for posting!

]]> By: Tsahi Levent-Levi https://bloggeek.me/write-webrtc-requirements/#comment-118690 Tue, 13 Dec 2016 06:06:26 +0000 https://bloggeek.me/?p=10947#comment-118690 In reply to Jaro.

Thanks for the tip Jaro.

User stories are indeed in fashion for a few years now, though I myself was never really fond of them (I hate writing these). This is probably because I usually capture the whole service in my mind and then break it down to its technical pieces. And yes – adding them does help in reducing miscommunication.

]]> By: Jaro https://bloggeek.me/write-webrtc-requirements/#comment-118689 Mon, 12 Dec 2016 21:07:40 +0000 https://bloggeek.me/?p=10947#comment-118689 Very usefull article – For us “youngsters” is this structure little bit oldfashioned. We started to use user stories when we are about describing any new project. We try to describe step by step user actions in various situations step by step – adding granularity and complexity as the analysis is in progress. This is extremely helpful later by designing GUI, developing user roles, system detailed behavior description etc. And the rest can remain as Tsahi described – and the final document you can seamlessly pass to IT analytics and programmers to create new awesome system 🙂

]]>