This episode is all about Leadership. I have Bernd Geropp with me. The man with Leadership in Mind. First of all I’m sure, everybody sooner or later comes across leading. Other leaders might affect you directly. Or you might become a leader by yourself. Because for this topic we’ll need a valid expert, I have asked Bernd to join us. Bernd Geropp is a successful consultant, inspiring trainer, and empathic coach for leadership. He’s a former company owner who has found his purpose in making better leaders. Bernd leads German podcasting scene for Leadership topics. In Mehr Fuehren – Führung auf den Punkt gebracht” which is More leadership – Leading in a nutshell he contributes worthwhile details every week.  He has raised the Leadership-Platform to support his members becoming better leaders, get the coworkers they want and gain more time for the really important things. We’re tackling topics about how to become a better leader. Or ways you can handle micro-management if you’re confronted with. And if you detect yourself has become a micro-manager you need to know what are the underlying reasons. Sooner or later, inevitably you stumble over trust. And how to become a better leader by building trust. However, it is very hard to build trust. While building trust you can also easily loose it in a second. As a result there are tons of obstacles and problems hidden underneath. One good entry point would be to participate in Bernd’s 3-part video training How to become a better leader for free. He shows you the essentials about leading and delegation. If you’re capable of German you definitely should have a look into it. Stay with me and enjoy the interview. Essential Answers Provided In This Episode For:  What do you think is the hidden purpose of micro-management? Why does extrinsic motivation not succeed? Which 3 things do intrinsically motivated people look for? How can you handle your micro-managing boss? Why thinking your boss is an idiot does not help you? How can you handle your own micro-managing? Why trust is essential for delegation? Why mistakes are essential for your managing carreer? And much more  Selected Links and Resources From This Episode  More Leadership Bernd’s website in English Mehr Führen – Bernd’s Webseite auf Deutsch Some english videos by Bernd 3-part video course about how to become a better leader for free (German)  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post The man with the “Leadership Mind” – Bernd Geropp – MES054 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2017/06/MES054.jpg" rel="nofollow" target="_blank"></a>This episode is all about <strong>Leadership</strong>. I have Bernd Geropp with me. The man with <strong>Leadership in Mind</strong>. First of all I’m sure, everybody sooner or later comes across leading. Other leaders might affect you directly. Or you might become a leader by yourself. Because for this topic we’ll need a valid expert, I have asked Bernd to join us. Bernd Geropp is a successful consultant, inspiring trainer, and empathic coach for leadership. He’s a former company owner who has found his purpose in making better leaders.</p> <p>Bernd leads German podcasting scene for Leadership topics. In <a href="https://www.mehr-fuehren.de/buecher-und-tools/podcast-fuehrung/" rel="nofollow" target="_blank"><strong>Mehr Fuehren – Führung auf den Punkt gebracht</strong></a>” which is <a href="https://www.more-leadership.com" rel="nofollow" target="_blank"><strong>More leadership – Leading in a nutshell</strong></a> he contributes worthwhile details every week.</p> <p></p> <p>He has raised the <a href="https://www.leadership-platform.de" rel="nofollow" target="_blank">Leadership-Platform</a> to support his members becoming better leaders, get the coworkers they want and gain more time for the really important things.</p> <p>We’re tackling topics about how to become a better leader. Or ways you can handle micro-management if you’re confronted with. And if you detect yourself has become a micro-manager you need to know what are the underlying reasons. Sooner or later, inevitably you stumble over trust. And how to become a better leader by building trust. However, it is very hard to build trust. While building trust you can also easily loose it in a second. As a result there are tons of obstacles and problems hidden underneath.</p> <p>One good entry point would be to participate in Bernd’s <strong>3-part video training</strong> <strong><a href="https://www.berndgeroppconsulting.de/3-teiliger-videokurs-optin-georg-lohrer/" rel="nofollow" target="_blank">How to become a better leader</a></strong> <strong>for free</strong>. He shows you the essentials about leading and delegation. If you’re capable of German you definitely should have a look into it.</p> <p>Stay with me and enjoy the interview.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What do you think is the hidden purpose of micro-management?</li> <li>Why does extrinsic motivation not succeed?</li> <li>Which 3 things do intrinsically motivated people look for?</li> <li>How can you handle your micro-managing boss?</li> <li>Why thinking your boss is an idiot does not help you?</li> <li>How can you handle your own micro-managing?</li> <li>Why trust is essential for delegation?</li> <li>Why mistakes are essential for your managing carreer?</li> <li>And much more</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://www.more-leadership.com" rel="nofollow" target="_blank">More Leadership</a> Bernd’s website in English</li> <li><a href="https://www.mehr-fuehren" rel="nofollow" target="_blank">Mehr Führen</a> – Bernd’s Webseite auf Deutsch</li> <li><a href="https://www.youtube.com/results?search_query=Bernd+Geropp+english" rel="nofollow" target="_blank">Some english videos by Bernd</a></li> <li><a href="https://www.berndgeroppconsulting.de/3-teiliger-videokurs-optin-georg-lohrer/" rel="nofollow" target="_blank">3-part video course about how to become a better leader for free (German)</a></li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/leadership-in-mind/" rel="nofollow" target="_blank">The man with the “Leadership Mind” – Bernd Geropp – MES054</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

The man with the "Leadership Mind" - Bernd Geropp - MES054

This is the 2nd episode of my 2017 visit to the Embedded World exhibition in Nuremberg. For the 1st part please refer to this episode. I have captured these details on my 2nd day at the Embedded World 2017 in Nuremberg. I once again want to present smaller companies. Of course always with interesting, sometimes even exciting offers. I do not want to ignore the bigger ones, however it’s like looking for nuggets. You have to dig deeper and scrutinize into the inner details. I would be very happy if you find something in for you which is worthwhile to share again. Please do not hesitate and forward this episode to your friends and colleagues. You are a more visual person? You’d like to see some details? Then look at my day#2 video and  day #1 video at YouTube.  The Embedded World topics in this episode are:  Cryptosource’s fleaTLS – a free TLS implementation designed for small footprint. Available royalty free in 3rd quarter 2017. Asaphus Vision presenting their Face Recognition Library. They support head- and eye-tracking and face-identification mainly, but not only, for self-driving vehicles. Timing suite for real-time systems by GLIWA. Supervise and collect timing- and stack-conditions on-the-fly in your embedded device. RTSoft supports you with experts for BSPs, drivers, middleware and APIs. HALCON is the machine vision solution by MVTec. They provide a versatile system supporting deep learning in visual data gathering. Grammatech’s binary code-analysis finally makes analysis of 3rd-party software possible, even you do not have the source-code available. My personal favorite of this day: Fraunhofer’s Equivert as new solution for dizziness therapy. An innovative idea presented as simple headphone with a lot of knowledge and experience inside. It gives dizzy patients the training they need to overcome their disease and step back into regular daily life. And more details and observations from this second day.  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Day 2 of the Embedded World – MES053 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2017/04/MES053.jpg" rel="nofollow" target="_blank"></a>This is the 2nd episode of my 2017 visit to the Embedded World exhibition in Nuremberg. For the 1st part please <a href="https://embeddedsuccess.com/episode52" rel="noopener nofollow" target="_blank">refer to this episode</a>.</p> <p>I have captured these details on my 2nd day at the Embedded World 2017 in Nuremberg. I once again want to present smaller companies. Of course always with interesting, sometimes even exciting offers. I do not want to ignore the bigger ones, however it’s like looking for nuggets. You have to dig deeper and scrutinize into the inner details. I would be very happy if you find something in for you which is worthwhile to share again. Please do not hesitate and forward this episode to your friends and colleagues.</p> <p><strong>You are a more visual person? You’d like to see some details?</strong> <strong>Then look at my <a href="https://youtu.be/Bn-zRB-F3ck" rel="noopener nofollow" target="_blank">day#2 video</a> and  <a href="https://youtu.be/H1ywMJlss4E" rel="noopener nofollow" target="_blank">day #1 video at YouTube</a>.</strong></p> <p></p> <h2>The Embedded World topics in this episode are:</h2> <ul> <li><a href="http://crypto-source.de" rel="noopener nofollow" target="_blank">Cryptosource’s fleaTLS</a> – a free TLS implementation designed for small footprint. Available royalty free in 3rd quarter 2017.</li> <li><a href="https://asaphus.de" rel="noopener nofollow" target="_blank">Asaphus Vision presenting their Face Recognition Library</a>. They support head- and eye-tracking and face-identification mainly, but not only, for self-driving vehicles.</li> <li><a href="https://www.gliwa.com/index.php?page=products_T1&amp;lang=eng" rel="noopener nofollow" target="_blank">Timing suite for real-time systems by GLIWA</a>. Supervise and collect timing- and stack-conditions on-the-fly in your embedded device.</li> <li><a href="http://rtsoft.de/en/" rel="noopener nofollow" target="_blank">RTSoft supports you</a> with experts for BSPs, drivers, middleware and APIs.</li> <li><a href="http://www.mvtec.com/products/halcon/product-information/" rel="noopener nofollow" target="_blank">HALCON is the machine vision solution by MVTec</a>. They provide a versatile system supporting deep learning in visual data gathering.</li> <li><a href="https://www.grammatech.com" rel="noopener nofollow" target="_blank">Grammatech’s binary code-analysis</a> finally makes analysis of 3rd-party software possible, even you do not have the source-code available.</li> <li>My personal favorite of this day: <a href="https://www.ims.fraunhofer.de/en/Media_Center/Information_Sheets.html" rel="noopener nofollow" target="_blank">Fraunhofer’s Equivert as new solution for dizziness therapy</a>. An innovative idea presented as simple headphone with a lot of knowledge and experience inside. It gives dizzy patients the training they need to overcome their disease and step back into regular daily life.</li> <li>And more details and observations from this second day.</li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/news-from-the-embedded-world-exhibition-part-2/" rel="nofollow" target="_blank">Day 2 of the Embedded World – MES053</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Day 2 of the Embedded World - MES053

 In this episode it’s once again, as last year, all about the Embedded World exhibition in Nuremberg. This year I travelled with my microphone and with my camera. It should be the first time for me to shoot photos and videos from an exhibition. I was planning to have at least one episode of a YouTube video available for you. I succeeded! At least I collected rather a lot of material. Interesting details, great devices and sophisticated solutions. See my day #1 video at YouTube, too. The Embedded World topics in this episode are:  HW-security for Qualcom chips. All provided by Rambus. I captured a nice piece of information about the way to harden your IoT-devices. Microchip’s solution for USB-2-ethernet bridge and their astonishing fault-tolerant Gigabit-ethernet-switch. IEI’s innovative gateway into IoT Why it is essential to have an eye-catcher. And how good examples look like. And more general observations and experiences on this very first day.  Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Day 1 of the Embedded World – MES052 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2017/04/MES052.jpg" rel="nofollow" target="_blank"></a><br/> In this episode it’s once again, <a href="https://embeddedsuccess.com/episode30" rel="nofollow" target="_blank">as last year</a>, all about the Embedded World exhibition in Nuremberg.</p> <p>This year I travelled with my microphone and with my camera. It should be the first time for me to shoot photos and videos from an exhibition. I was planning to have at least one episode of a YouTube video available for you.</p> <p>I succeeded! At least I collected rather a lot of material. Interesting details, great devices and sophisticated solutions.</p> <p>See my <a href="https://youtu.be/H1ywMJlss4E" rel="nofollow" target="_blank">day #1 video at YouTube</a>, too.</p> <h2>The Embedded World topics in this episode are:</h2> <ul> <li><a href="https://www.rambus.com/rambus-to-demonstrate-iot-security-technology-in-qualcomm-booth-at-ces/?nabe=4857318206603264:1,6583178454368256:0" rel="nofollow" target="_blank">HW-security for Qualcom chips</a>. All provided by Rambus. I captured a nice piece of information about the way to harden your IoT-devices.</li> <li><a href="http://www.microchip.com/design-centers/usb/usb-hubs-and-devices/products/usb-bridges" rel="nofollow" target="_blank">Microchip’s solution for USB-2-ethernet bridge</a> and their astonishing <a href="http://www.microchip.com/design-centers/ethernet/ethernet-devices/products/ethernet-switches" rel="nofollow" target="_blank">fault-tolerant Gigabit-ethernet-switch</a>.</li> <li><a href="http://new.ieiworld.com/_index/en/" rel="nofollow" target="_blank">IEI’s innovative gateway into IoT</a></li> <li>Why it is essential to have an eye-catcher. And how good examples look like.</li> <li>And more general observations and experiences on this very first day.</li> </ul> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/news-from-the-embedded-world-exhibition-part-1/" rel="nofollow" target="_blank">Day 1 of the Embedded World – MES052</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Day 1 of the Embedded World - MES052

 Let’s have a short Wrap-Up of the MES’s episodes in 2016 before we focus on 2017 and how things might continue. What were the main episode streams in 2016 in the Mastering Embeddeds Systems podcast? Was it the root-cause mini-series in the first half of the year? Or was it the series about Death March Projects? What about the interviews and the interesting characters we got in touch with? Or do we want to emphasize the personal improvement sessions in the last quarter of this year. We have had marvellous guests in the show during this year:  Rinding Jenkins with Oleg Nenashev from CloudBees in MES027 Use multi-core CPUs instead of single-core and automatically transfer legacy code. Jeronimo Castrillon-Mazo from Silixica was in the show in MES031 Big topic – Virtualization in Embedded Systems. We have welcome Baurzhan Ismagulov and Alexander Smirnov from Ilbers Technology. They gave a lot of information and details and presented their Mango bare-metal hypervisor in MES034 In MES036 we have tackled Security in Embedded Systems with Andrej Nikishin from Kaspersky Labs Requirements Engineering was another big topic in 2016. We have had 3 different episodes with Joachim Reinke:  MES038 – Why do you need Requirements Engineering? MES042 – How to relief your pain with requirements engineering? In MES043 Joachim and myself have welcomed Jordan Kyriakidis and Trevor Bredley from QRAcorp. We discussed the way tools can support you in Requirements Engineering.   In the last interview in 2016 there was Maik Pfingsten with us. In MES045 we talked about Maik’s way to maintain derailed projects.  In the finish of this episode I give you some outsights into the future of this podcast and further upcoming activities. Selected Links and Resources From This Episode  Spark at Adobe  Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Year’s-End Wrap-Up 2016 – MES051 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/12/MES051.jpg" rel="nofollow" target="_blank"></a><br/> Let’s have a short Wrap-Up of the MES’s episodes in 2016 before we focus on 2017 and how things might continue.</p> <p>What were the main episode streams in 2016 in the Mastering Embeddeds Systems podcast? Was it the root-cause mini-series in the first half of the year? Or was it the series about Death March Projects? What about the interviews and the interesting characters we got in touch with? Or do we want to emphasize the personal improvement sessions in the last quarter of this year.</p> <p>We have had marvellous guests in the show during this year:</p> <ul> <li>Rinding Jenkins with Oleg Nenashev from CloudBees in <a href="https://embeddedsuccess.com/episode27" rel="nofollow" target="_blank">MES027</a></li> <li>Use multi-core CPUs instead of single-core and automatically transfer legacy code. Jeronimo Castrillon-Mazo from Silixica was in the show in <a href="https://embeddedsuccess.com/episode31" rel="nofollow" target="_blank">MES031</a></li> <li>Big topic – Virtualization in Embedded Systems. We have welcome Baurzhan Ismagulov and Alexander Smirnov from Ilbers Technology. They gave a lot of information and details and presented their Mango bare-metal hypervisor in <a href="https://embeddedsuccess.com/episode34" rel="nofollow" target="_blank">MES034</a></li> <li>In <a href="https://embeddedsuccess.com/episode36" rel="nofollow" target="_blank">MES036</a> we have tackled<br/> Security in Embedded Systems with Andrej Nikishin from Kaspersky Labs</li> <li>Requirements Engineering was another big topic in 2016. We have had 3 different episodes with Joachim Reinke: <ul> <li><a href="https://embeddedsuccess.com/episode38" rel="nofollow" target="_blank">MES038 – Why do you need Requirements Engineering?</a></li> <li><a href="https://embeddedsuccess.com/episode42" rel="nofollow" target="_blank">MES042 – How to relief your pain with requirements engineering?</a></li> <li>In <a href="https://embeddedsuccess.com/episode43" rel="nofollow" target="_blank">MES043</a> Joachim and myself have welcomed Jordan Kyriakidis and Trevor Bredley from QRAcorp. We discussed the way tools can support you in Requirements Engineering.</li> </ul> </li> <li>In the last interview in 2016 there was Maik Pfingsten with us. In <a href="https://embeddedsuccess.com/episode45" rel="nofollow" target="_blank">MES045</a> we talked about Maik’s way to maintain derailed projects.</li> </ul> <p>In the finish of this episode I give you some outsights into the future of this podcast and further upcoming activities.</p> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://spark.adobe.com" rel="nofollow" target="_blank">Spark at Adobe</a></li> </ul> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/years-end-wrap-2016/" rel="nofollow" target="_blank">Year’s-End Wrap-Up 2016 – MES051</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Year's-End Wrap-Up 2016 - MES051

The ESE-Kongress in Sindelfingen. More than 1.300 participants! 100 presentations! 3 days with 4 streams in parallel! Amazing! The German Embedded Software Engineering Kongress is the second largest gathering of Embedded specialists in Europe. I gave my debut presentation with “No belly-flops with virtual teams”. But there are about 100 other presentations in 4 parallel streams on three days. From 29th, November until 1st, December people belonging to the Embedded realm has their gathering in Sindelfingen. It’s a great happening with interesting persons presenting stunning talks, new topics and detailed insights. I picked three topics – diverting, trendy and versatile. It’s of course no representative selection. There were lots of topics from various areas: architecture, real-time and multi-core, safety and security, implementation, open source, IoT, Industrie 4.0, automotive, test and quality, Agile, software engineering and last not least management. Selected pickings  Hardware faults in safety critical systems The renaissance of Ada Agile development processes in normative regulated environments  Stay tuned and be inspired. Selected Links and Resources From This Episode  The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering Embedded Conference Scandinavia QNX ADA Core Who’s using ADA? ADA compilers available on various platforms Parallel ADA – A Requirement for ADA 2020 Heisenbug Scrum QA at Berner-Mattner My experience as a QA in Scrum Some troubles understanding Scrum QA  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post 3 pickings from ESE-Kongress 2016 – MES050 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/12/MES050.jpg" rel="nofollow" target="_blank"></a>The ESE-Kongress in Sindelfingen. More than 1.300 participants! 100 presentations! 3 days with 4 streams in parallel! Amazing!</p> <p>The German Embedded Software Engineering Kongress is the second largest gathering of Embedded specialists in Europe. I gave my debut presentation with “No belly-flops with virtual teams”. But there are about 100 other presentations in 4 parallel streams on three days. From 29th, November until 1st, December people belonging to the Embedded realm has their gathering in Sindelfingen. It’s a great happening with interesting persons presenting stunning talks, new topics and detailed insights.</p> <p>I picked three topics – diverting, trendy and versatile. It’s of course no representative selection. There were lots of topics from various areas: architecture, real-time and multi-core, safety and security, implementation, open source, IoT, Industrie 4.0, automotive, test and quality, Agile, software engineering and last not least management.</p> <h2>Selected pickings</h2> <ul> <li>Hardware faults in safety critical systems</li> <li>The renaissance of Ada</li> <li>Agile development processes in normative regulated environments</li> </ul> <p>Stay tuned and be inspired.</p> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://www.ese-kongress.de/english/" rel="nofollow" target="_blank">The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering</a></li> <li><a href="http://www.embeddedconference.se" rel="nofollow" target="_blank">Embedded Conference Scandinavia</a></li> <li><a href="http://www.qnx.com" rel="nofollow" target="_blank">QNX</a></li> <li><a href="http://www.adacore.com" rel="nofollow" target="_blank">ADA Core</a></li> <li><a href="http://www.seas.gwu.edu/~mfeldman/ada-project-summary.html" rel="nofollow" target="_blank">Who’s using ADA?</a></li> <li><a href="http://libre.adacore.com/download/configurations" rel="nofollow" target="_blank">ADA compilers available on various platforms</a></li> <li><a href="http://cs.york.ac.uk/rts/static/papers/R:Burns:2013g.pdf" rel="nofollow" target="_blank">Parallel ADA – A Requirement for ADA 2020</a></li> <li><a href="https://en.wikipedia.org/wiki/Heisenbug" rel="nofollow" target="_blank">Heisenbug</a></li> <li><a href="http://www.berner-mattner.com" rel="nofollow" target="_blank">Scrum QA at Berner-Mattner</a></li> <li><a href="https://www.infoq.com/articles/experience-qa-scrum" rel="nofollow" target="_blank">My experience as a QA in Scrum</a></li> <li><a href="http://stackoverflow.com/questions/155250/help-me-understand-how-qa-works-in-scrum" rel="nofollow" target="_blank">Some troubles understanding Scrum QA</a></li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/pickings-from-ese-congress-2016/" rel="nofollow" target="_blank">3 pickings from ESE-Kongress 2016 – MES050</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

3 pickings from ESE-Kongress 2016 - MES050

You were misunderstood. Although you have spent a lot of effort to be precise and clear. But nevertheless somehow your counterpart has horribly misunderstood you. And now you’re in big trouble. Perhaps your spouse interpreted your “Nice” for the new dress as inadequate. Or there was this tone of desinterest in your voice. Or you just run into this ugly problem at work and your mind is still in the office. You all remember what happens after such situation. Something has gone wrong. How can we avoid such kind of situation?  Paul Watzlawick once said “We cannot not communicate”. Everything we say OR not say, everything we do OR not do, transfers a message. We cannot decide whether we communicate or do not communicate. We always communicate. Communication happens verbally and non-verbally, explicitely and implicitely. We should be aware that a risen eyebrow, a turn-away face, a dismissive look transfers information to the receiver. But there are ways to improve communcation and decrease misunderstanding. In this episode I will introduce the Four Sides Model for communcation. Friedemann Schulz von Thun has invented this abstraction to let us understand communication ways better. This model gives you a strong background to improve your communcation. In detail I will share with you nine surprisingly simple tips to improve your communication. You guys should listen to this episode if you want to understand why communicating could sometimes be that complicated, erroneous or misleading. If you want to improve your skills herein you’re exactly right in this session. If you want to get the tips in written form, feel free to use the link below to get your personal copy of the tips-list. Stay tuned and be inspired. Essential Answers Provided In This Episode For:  Why do we sometimes communicate that weird? What does communicating mean at all? How does the Four Side Model work? What can go wrong in communication? What does good communication mean? Why listening is essential for good communication? Why pictures or stories support you? How can body talk impact the meaning of messages? And much much more.  Selected Links and Resources From This Episode  Four Side Model of communication Models of Communication Paul Watzlawick Start with Mindfulness  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post 9 surprisingly simple tips to improve your communcation – MES049 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/11/MES049.jpg" rel="nofollow" target="_blank"></a>You were misunderstood.</p> <p>Although you have spent a lot of effort to be precise and clear. But nevertheless somehow your counterpart has horribly misunderstood you. And now you’re in big trouble. Perhaps your spouse interpreted your “Nice” for the new dress as inadequate. Or there was this tone of desinterest in your voice. Or you just run into this ugly problem at work and your mind is still in the office. You all remember what happens after such situation. Something has gone wrong. How can we avoid such kind of situation?</p> <p></p> <p><a href="https://en.wikipedia.org/wiki/Paul_Watzlawick" rel="nofollow" target="_blank">Paul Watzlawick</a> once said <em>“We cannot not communicate”</em>.</p> <p>Everything we say OR not say, everything we do OR not do, transfers a message. We cannot decide whether we communicate or do not communicate. We always communicate. Communication happens verbally and non-verbally, explicitely and implicitely. We should be aware that a risen eyebrow, a turn-away face, a dismissive look transfers information to the receiver.</p> <p>But there are ways to improve communcation and decrease misunderstanding. In this episode I will introduce the Four Sides Model for communcation. <a href="https://en.wikipedia.org/wiki/Four-sides_model" rel="nofollow" target="_blank">Friedemann Schulz von Thun</a> has invented this abstraction to let us understand communication ways better. This model gives you a strong background to improve your communcation. In detail I will share with you nine surprisingly simple tips to improve your communication.</p> <p>You guys should listen to this episode if you want to understand why communicating could sometimes be that complicated, erroneous or misleading. If you want to improve your skills herein you’re exactly right in this session. If you want to get the tips in written form, feel free to use the link below to get your personal copy of the tips-list.</p> <p>Stay tuned and be inspired.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>Why do we sometimes communicate that weird?</li> <li>What does communicating mean at all?</li> <li>How does the Four Side Model work?</li> <li>What can go wrong in communication?</li> <li>What does <em>good</em> communication mean?</li> <li>Why listening is essential for good communication?</li> <li>Why pictures or stories support you?</li> <li>How can body talk impact the meaning of messages?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://en.wikipedia.org/wiki/Four-sides_model" rel="nofollow" target="_blank">Four Side Model of communication</a></li> <li><a href="https://en.wikipedia.org/wiki/Models_of_communication" rel="nofollow" target="_blank">Models of Communication</a></li> <li><a href="https://en.wikipedia.org/wiki/Paul_Watzlawick" rel="nofollow" target="_blank">Paul Watzlawick</a></li> <li><a href="http://mindfulnessforstudents.co.uk/resources/mindfulness-audio-guided-practices/" rel="nofollow" target="_blank">Start with Mindfulness</a></li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/9-tips-to-improve-communication/" rel="nofollow" target="_blank">9 surprisingly simple tips to improve your communcation – MES049</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

9 surprisingly simple tips to improve your communcation - MES049

It’s a pity. That most of us find their best time in staying in their Comfort Zone. In this hammock of regular habits. Full of cosy feelings, thoughts and emotions. Of course, we all have our regular habits, the routins. In the morning in the bathroom or in the evening going to bed. We also follow our inner boosters telling us to be perfect, punctual, or push ourselves and hurry up. But it’s really sad, that we regularly get stuck in this zone. Our Comfort Zone is supposed to keep our life safe. But what it really does is keep our life small. Outside of our comfort zone there seems to be lot of interesting amazing things. Possibilities without end. But it’s outside. And before we can get in touch with these endless possibilities, we have to tackle the wall of pain. Lots of pain are waiting: denial, uncertainty, helplessness or fear. There’s a way to overcome this wall. But first you need to understand the paradoxon of pain. In this episode I wanted to share with you a tool I have detected some time ago. The Tool “Reversal of Desire” was introduced by Phil Stutz and Barry Michels. And it is their gift to all of us who want to lift ourselves to the next level. A tool to propell you out of your comfort zone. That you get in touch with your possibilities overcoming the pain. Stay tuned and be inspired. Essential Answers Provided In This Episode For:  Wy do we have a Comfort Zone? Why do we love it? What does the Comfort Zone do with us? How can we get out of our Comfort Zone? What’s the Pain Paradoxon? Why does the Tool work? What’s the Higher Force? When do use the Tool? How to find courage in your fear? And much much more.  Selected Links and Resources From This Episode  Reversal of Desire – The Tool on YouTube The Tools by Phil Stutz and Barry Michels  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Say YES to your pain and step out of your Comfort Zone – MES048 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/11/MES048.jpg" rel="nofollow" target="_blank"></a>It’s a pity.</p> <p>That most of us find their best time in staying in their Comfort Zone. In this hammock of regular habits. Full of cosy feelings, thoughts and emotions. Of course, we all have our regular habits, the routins. In the morning in the bathroom or in the evening going to bed. We also follow our inner boosters telling us to be perfect, punctual, or push ourselves and hurry up. But it’s really sad, that we regularly get stuck in this zone.</p> <p>Our Comfort Zone is supposed to keep our life safe. But what it really does is keep our life small. Outside of our comfort zone there seems to be lot of interesting amazing things. Possibilities without end. But it’s outside. And before we can get in touch with these endless possibilities, we have to tackle the wall of pain. Lots of pain are waiting: denial, uncertainty, helplessness or fear. There’s a way to overcome this wall. But first you need to understand the paradoxon of pain.</p> <p>In this episode I wanted to share with you a tool I have detected some time ago. The Tool “Reversal of Desire” was introduced by Phil Stutz and Barry Michels. And it is their gift to all of us who want to lift ourselves to the next level. A tool to propell you out of your comfort zone. That you get in touch with your possibilities overcoming the pain.</p> <p>Stay tuned and be inspired.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>Wy do we have a Comfort Zone?</li> <li>Why do we love it?</li> <li>What does the Comfort Zone do with us?</li> <li>How can we get out of our Comfort Zone?</li> <li>What’s the Pain Paradoxon?</li> <li>Why does the Tool work?</li> <li>What’s the Higher Force?</li> <li>When do use the Tool?</li> <li>How to find courage in your fear?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://www.youtube.com/watch?v=kWZaQgDeHYM" rel="nofollow" target="_blank">Reversal of Desire – The Tool on YouTube</a></li> <li><a href="https://www.amazon.com/Tools-Transform-Problems-Confidence-Creativity/dp/B00870F6TA/ref=sr_1_1?ie=UTF8&amp;qid=1478429242&amp;sr=8-1&amp;keywords=tool+phil+stutz" rel="nofollow" target="_blank">The Tools by Phil Stutz and Barry Michels</a></li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/step-out-of-your-comfort-zone/" rel="nofollow" target="_blank">Say YES to your pain and step out of your Comfort Zone – MES048</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Say YES to your pain and step out of your Comfort Zone - MES048

Avoid managing your time – MES047 This is the first episode of my new mini-series “Improve Yourself”. This series is based on the results of my last survey on my podcast listeners. We’ll start today with the episode of Time-Management. Is it really possible to manage time? To do Time-Management? I do not think so. Because time is something we cannot impact or manipulate. The only thing we can do is to change our way to experience time passing by. And this change of perspective drops away all these usual Time-Mangement tools, books, courses, hints and tricks. But you get confronted with yourself. Everybody of us lives in the same time. But some of us seem to have sufficient time. Others seem to always exceed their amount and do not succeed in time. The question is: why is it like that? And what can we do as individuals to get the best out of our time? This episode will support you here. Detect your next steps to realize things which are really important to you. And then start. Stay tuned and be inspired. Essential Answers Provided In This Episode For:  Why time management tipps and tools do not work What are the inner benefits for self-made time problems? If we cannot manage time, what else can we do? Which 3 things have changed my life belonging time? How does the Zegarnik-effect prevent you from being free in your time? Why the Five-Minute-Journal might be the best things to start? And much much more.  Selected Links and Resources From This Episode  HeadSpace – Treat your head right The Five Minute Journal The Zeigarnik Effect Miracle Morning by Hal Elrod  Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Avoid managing your time – MES047 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2016/10/MES047.jpg" rel="nofollow" target="_blank"></a>Avoid managing your time – MES047</h2> <p>This is the first episode of my new mini-series “Improve Yourself”. This series is based on the results of my last survey on my podcast listeners. We’ll start today with the episode of Time-Management.</p> <p>Is it really possible to manage time? To do Time-Management? I do not think so. Because time is something we cannot impact or manipulate. The only thing we can do is to change our way to experience time passing by.</p> <p>And this change of perspective drops away all these usual Time-Mangement tools, books, courses, hints and tricks. But you get confronted with yourself. Everybody of us lives in the same time. But some of us seem to have sufficient time. Others seem to always exceed their amount and do not succeed in time.</p> <p>The question is: why is it like that? And what can we do as individuals to get the best out of our time? This episode will support you here. Detect your next steps to realize things which are really important to you. And then start.</p> <p>Stay tuned and be inspired.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>Why time management tipps and tools do not work</li> <li>What are the inner benefits for self-made time problems?</li> <li>If we cannot manage time, what else can we do?</li> <li>Which 3 things have changed my life belonging time?</li> <li>How does the Zegarnik-effect prevent you from being free in your time?</li> <li>Why the Five-Minute-Journal might be the best things to start?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://www.headspace.com" rel="nofollow" target="_blank">HeadSpace – Treat your head right</a></li> <li><a href="https://www.intelligentchange.com/products/the-five-minute-journal" rel="nofollow" target="_blank">The Five Minute Journal</a></li> <li><a href="https://en.wikipedia.org/wiki/Bluma_Zeigarnik" rel="nofollow" target="_blank">The Zeigarnik Effect</a></li> <li><a href="https://www.amazon.com/Miracle-Morning-Not-So-Obvious-Guaranteed-Transform/dp/0979019710/ref=sr_1_1?ie=UTF8&amp;qid=1477222110&amp;sr=8-1&amp;keywords=the+miracle+morning" rel="nofollow" target="_blank">Miracle Morning by Hal Elrod</a></li> </ul> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/avoid-managing-your-time-mes047/" rel="nofollow" target="_blank">Avoid managing your time – MES047</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Avoid managing your time - MES047

Do you have ever thought about the aftermath for your root cause analysis? What should be done if you have found the real cause of your problem? What do you regularly do after you have made your correction? By the way – do you know whether your correction really corrects the problem? That it only corrects the problem? And does not introduce a ton of new problems? In this episode it’s all about what’s coming after the problem’s analysis. I have given you 3 examples of how to find the root cause of your problem: 5-Whys, Ishikawa and Enhanced Cause-Effect. But finding the root cause is not the end, but the beginning of the whole story. There is so much more in it. You should listen to this episode if you have to analyse problems with a significant depth. And if you want to know what you can do after you have done the root cause analysis? What are the next steps? This episode will support you in improving the outcome of your root cause analysis. You will get an idea how to achieve consistent, substantial, and reliable ways to proceed with your analysis. I have composed a checklist you are free to use to improve your root cause analysis. It will provide you several questions to enlarge your perspective of the problem situation, your correction and your next steps. Feel free to download the checklist here. Stay tuned and be inspired.   Essential Answers Provided In This Episode For:  How to get one step ahead of regular root cause-analysis? What do we miss after regular root cause analysis? What’s this Kaizen and Yokoten about? Do you really improve? Or do you only pretend to improve? Why you should not stop directly after the root cause analysis What kind of questions should you raise to enhance your understanding of the situation? How to establish or improve your process? And much much more.  Selected Links and Resources From This Episode  MES009 – Finding root causes with 5-Whys MES014 – Finding root-causes with Ishikawa MES029 – Find root causes with the Enhanced Cause-Effect approach The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering   Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post It’s a shame that you do not make the best out of your root cause analysis – MES046 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/10/MES046.jpg" rel="nofollow" target="_blank"></a>Do you have ever thought about the aftermath for your root cause analysis? What should be done if you have found the real cause of your problem? What do you regularly do after you have made your correction?<br/> By the way – do you know whether your correction really corrects the problem? That it only corrects the problem? And does not introduce a ton of new problems?</p> <p>In this episode it’s all about what’s coming after the problem’s analysis.</p> <p>I have given you 3 examples of how to find the root cause of your problem: <a href="https://embeddedsuccess.com/episode09" rel="nofollow" target="_blank">5-Whys</a>, <a href="https://embeddedsuccess.com/episode014" rel="nofollow" target="_blank">Ishikawa</a> and <a href="https://embeddedsuccess.com/episode029" rel="nofollow" target="_blank">Enhanced Cause-Effect</a>. But finding the root cause is not the end, but the beginning of the whole story. There is so much more in it.</p> <p>You should listen to this episode if you have to analyse problems with a significant depth. And if you want to know what you can do after you have done the root cause analysis? What are the next steps?</p> <p>This episode will support you in improving the outcome of your root cause analysis. You will get an idea how to achieve consistent, substantial, and reliable ways to proceed with your analysis.</p> <p>I have composed a checklist you are free to use to improve your root cause analysis. It will provide you several questions to enlarge your perspective of the problem situation, your correction and your next steps. Feel free to download the checklist here.</p> <p>Stay tuned and be inspired.</p> <p> </p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>How to get one step ahead of regular root cause-analysis?</li> <li>What do we miss after regular root cause analysis?</li> <li>What’s this Kaizen and Yokoten about?</li> <li>Do you really improve? Or do you only pretend to improve?</li> <li>Why you should not stop directly after the root cause analysis</li> <li>What kind of questions should you raise to enhance your understanding of the situation?</li> <li>How to establish or improve your process?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://embeddedsuccess.com/episode09" rel="nofollow" target="_blank">MES009 – Finding root causes with 5-Whys</a></li> <li><a href="https://embeddedsuccess.com/episode014" rel="nofollow" target="_blank">MES014 – Finding root-causes with Ishikawa</a></li> <li><a href="https://embeddedsuccess.com/episode029" rel="nofollow" target="_blank">MES029 – Find root causes with the Enhanced Cause-Effect approach</a></li> <li><a href="http://www.ese-kongress.de/english/" rel="nofollow" target="_blank">The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/its-a-shame-that-you-do-not-make-the-best-out-of-your-root-cause-analysis-mes046/" rel="nofollow" target="_blank">It’s a shame that you do not make the best out of your root cause analysis – MES046</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

It's a shame that you do not make the best out of your root cause analysis - MES046

Sometimes people ask me: “What’s that about project troubleshooting? What does it mean? Who does anybody need this kind of stuff? What are you guys doing? And what’s the benefit at the end?” I want to provide some answers on these question. I have invited a friend of mine, who has worked as project troubleshooter for a decade. Maik Pfingsten is an elaborated engineer, a versatile project leader and he has saved a lot of projects under rough conditions. He meanwhile works as mentor, speaker, author and coach for specific topics round about projects in trouble. He tells us a lot about his very personal way of coping with projects in trouble. About the regular steps he has used and the experiences he has gathered during his long journey.  You should listen to this episode if your project is in trouble and you have already thought about some external support. Or you want to know details how such kind of external consulting might look like. And it will become especially worthwhile if you consider to work yourself as project troubleshooter, but you do not yet exactly know whether it is the right way. But, of course, you also can listen only if you’re simply interested in the topic  This episode will support you in understanding the different steps how derailed projects might find their way out of trouble. What kind of essentials you have to take into account. And perhaps also whether this approach is the right one for you, your project or your company. Stay with me and enjoy the chat. Essential Answers Provided In This Episode For:  How to become a project troubleshooter? What kind of skill do you have to work successfully as a troubleshooter? Why does Maik follow a specific plan to cope with derailed projects? How does the system footprint supports different perspectives? Why Maik protects the project team first? Why stepping out is that essential for the troubleshooter. Highlight for the ESE-Kongress 2016 in Sindelfingen And much much more.  Selected Links and Resources From This Episode  One of Maik’s Podcasts: Zukunftsarchitekten – Systems Engineering Leadership Maik in LinkedIn Maik in Xing Maik in Twitter @mpfingsten The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Tech-Chat: How to maintain derailed projects with Maik Pfingsten – MES045 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/09/Maik-Pfingsten.jpg" rel="nofollow" target="_blank"></a>Sometimes people ask me: “What’s that about project troubleshooting? What does it mean? Who does anybody need this kind of stuff? What are you guys doing? And what’s the benefit at the end?” I want to provide some answers on these question. I have invited a friend of mine, who has worked as project troubleshooter for a decade. Maik Pfingsten is an elaborated engineer, a versatile project leader and he has saved a lot of projects under rough conditions. He meanwhile works as mentor, speaker, author and coach for specific topics round about projects in trouble.</p> <p>He tells us a lot about his very personal way of coping with projects in trouble. About the regular steps he has used and the experiences he has gathered during his long journey.</p> <p></p> <p>You should listen to this episode if your project is in trouble and you have already thought about some external support. Or you want to know details how such kind of external consulting might look like. And it will become especially worthwhile if you consider to work yourself as project troubleshooter, but you do not yet exactly know whether it is the right way. But, of course, you also can listen only if you’re simply interested in the topic </p> <p>This episode will support you in understanding the different steps how derailed projects might find their way out of trouble. What kind of essentials you have to take into account. And perhaps also whether this approach is the right one for you, your project or your company.</p> <p>Stay with me and enjoy the chat.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>How to become a project troubleshooter?</li> <li>What kind of skill do you have to work successfully as a troubleshooter?</li> <li>Why does Maik follow a specific plan to cope with derailed projects?</li> <li>How does the system footprint supports different perspectives?</li> <li>Why Maik protects the project team first?</li> <li>Why stepping out is that essential for the troubleshooter.</li> <li>Highlight for the ESE-Kongress 2016 in Sindelfingen</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li>One of Maik’s Podcasts: <a href="http://zukunftsarchitekten-podcast.de/" rel="nofollow" target="_blank">Zukunftsarchitekten – Systems Engineering Leadership</a></li> <li><a href="https://de.linkedin.com/in/maikpfingsten" rel="nofollow" target="_blank">Maik in LinkedIn</a></li> <li><a href="https://www.xing.com/profile/Maik_Pfingsten" rel="nofollow" target="_blank">Maik in Xing</a></li> <li><a href="https://twitter.com/mpfingsten" rel="nofollow" target="_blank">Maik in Twitter @mpfingsten</a></li> <li><a href="http://www.ese-kongress.de/english/" rel="nofollow" target="_blank">The ESE Kongress – Germany’s Largest Congress for Professional Embedded Software Engineering</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/tech-chat-how-to-maintain-derailed-projects-mes045/" rel="nofollow" target="_blank">Tech-Chat: How to maintain derailed projects with Maik Pfingsten – MES045</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Tech-Chat: How to maintain derailed projects with Maik Pfingsten - MES045

Out of practice into practice. The podcast for engineers in the Embedded Systems realm.

Excellent stuff about Embedded Systems!

WOW…Mastering Embedded Systems Podcast is flat out awesome. Good production quality. Easy to listen. Very impressed Georg. Keep bringing it.

GREAT JOB!

Mastering Embedded Systems

Find root causes with the Enhanced Cause-Effect approach In the first two sessions about root-cause-analysis I have introduced the 5-Whys and the Ishikawa techniques. Both have their pros and cons. For a long time I was looking for a better way to provide root cause analysis. More sophisticated than the 5-Whys, but not that compilicated and elaborate as the Ishikawa. And hereby I came across with an enhanced version of the regular Cause-Effect approach. It’s again a graphical approach which combines simplicity and logic. It’s especially useful for situations in which multiple goals are affected.  The way to evaluate root-causes using the enhanced cause-effect is my preferred way. And that’s due to two reasons. First, it’s rather progressive and can be driven alone or in groups. You achieve quick results without spending too much effort into nasty categorizations or simplifications. Second, in it’s final stage provided as a diagram, it can be quickly and fully understood. You do not need verbose explanations how to read it or why some things have been dropped. Stay tuned and be inspired. Essential Answers Provided In This Episode For:  What are the major drawbacks of 5-Whys and the Ishikawa? When to use the Cause-Effect approach? How to do the Enhanced Cause-Effect RCA? What are the goals of the affected situation or item? How to determine the causes which impact the goals? Why is it essential accumulate all causes and not only the preferred ones? Where to use the AND clause for combined causes? Why do even nitpicking details need to be mentioned? And much much more.  Selected Links and Resources From This Episode  Boeing 777 Wing Break Test; Sorry, I haven’t found the video of the Airbus 380, but the 777 gives the same show. ThinkReliability The Titanic RCA by ThinkReliability Embedded World 2016 in Nuremberg   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Find root causes with the Enhanced Cause-Effect approach – MES029 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2016/02/Enhanced-Cause-Effect.png" rel="attachment wp-att-843 nofollow" target="_blank"></a>Find root causes with the Enhanced Cause-Effect approach</h2> <p>In the first two sessions about root-cause-analysis I have introduced the <a href="https://embeddedsuccess.com/episode09" rel="nofollow" target="_blank">5-Whys</a> and the <a href="https://embeddedsuccess.com/episode14" rel="nofollow" target="_blank">Ishikawa</a> techniques. Both have their pros and cons.</p> <p>For a long time I was looking for a better way to provide root cause analysis. More sophisticated than the 5-Whys, but not that compilicated and elaborate as the Ishikawa. And hereby I came across with an enhanced version of the regular Cause-Effect approach.</p> <p>It’s again a graphical approach which combines simplicity and logic. It’s especially useful for situations in which multiple goals are affected.</p> <p></p> <p>The way to evaluate root-causes using the enhanced cause-effect is my preferred way. And that’s due to two reasons. First, it’s rather progressive and can be driven alone or in groups. You achieve quick results without spending too much effort into nasty categorizations or simplifications. Second, in it’s final stage provided as a diagram, it can be quickly and fully understood. You do not need verbose explanations how to read it or why some things have been dropped.</p> <p>Stay tuned and be inspired.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What are the major drawbacks of 5-Whys and the Ishikawa?</li> <li>When to use the Cause-Effect approach?</li> <li>How to do the Enhanced Cause-Effect RCA?</li> <li>What are the goals of the affected situation or item?</li> <li>How to determine the causes which impact the goals?</li> <li>Why is it essential accumulate all causes and not only the preferred ones?</li> <li>Where to use the AND clause for combined causes?</li> <li>Why do even nitpicking details need to be mentioned?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://www.youtube.com/watch?v=rak2HldVp9M" rel="nofollow" target="_blank">Boeing 777 Wing Break Test</a>; Sorry, I haven’t found the video of the Airbus 380, but the 777 gives the same show.</li> <li><a href="http://www.thinkreliability.com" rel="nofollow" target="_blank">ThinkReliability</a></li> <li><a href="http://www.thinkreliability.com/Titanic.aspx" rel="nofollow" target="_blank">The Titanic RCA by ThinkReliability</a></li> <li><a href="https://www.embedded-world.de/en" rel="nofollow" target="_blank">Embedded World 2016 in Nuremberg</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/find-root-causes-with-the-enhanced-cause-effect-approach-mes029/" rel="nofollow" target="_blank">Find root causes with the Enhanced Cause-Effect approach – MES029</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Find root causes with the Enhanced Cause-Effect approach - MES029

Right before my holiday I have made a bad experience. Some meetings with a vendor have gone sub-optimal to say the least. There were several road blocks and nit-picking details which brought the meetings close to waste of time. However it was a good opportunity to observe what could be done much more better when talking with vendors for technical problems. I have run a lot of such talks and I wanted to take this bad situation as trigger to collect my 5 hacks to get the most out of vendor discussions. You should listen to this episode if you will sooner or later found yourself confronted with your boss’ request: “Hey man, let’s discuss with vendor #XYZ. They should support us here.” And with “let us” he of course means you. Or you’ve already talked with your vendor (or vendors) and you again and again observe some counterproductive situations, but you do not exactly know how to improve them. This episode enhances you to finish vendor discussions better as average. Or if you’re the vendor, you know exactly whether your customer is well prepared and honest with you in his request for explicit support. Stay with me and enjoy the chat. Essential Answers Provided In This Episode For:  Why do we need to talk with the vendor? Why becomes the meeting invitation that essential? When you should cancel the meeting directly? How can you prepare for the meeting with your vendor? What kind of additional communication channels should you maintain during the meeting? When will superiors in the meeting become counterproductive? Why writing of minutes is the key-point in control? And much much more.  Selected Links and Resources From This Episode  Episode #8 – How to successfully launch a task-force Meeting invitation template Episode #35 – 5 simple tweaks to use Mind-Maps for meeting minutes   Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post 5 hacks to succeed in discussions with your vendor – MES044 appeared first on Embedded Success.

<p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/09/MES044.jpg" rel="nofollow" target="_blank"></a>Right before my holiday I have made a bad experience. Some meetings with a vendor have gone sub-optimal to say the least.<br/> There were several road blocks and nit-picking details which brought the meetings close to waste of time.</p> <p>However it was a good opportunity to observe what could be done much more better when talking with vendors for technical problems. I have run a lot of such talks and I wanted to take this bad situation as trigger to collect my 5 hacks to get the most out of vendor discussions.</p> <p>You should listen to this episode if you will sooner or later found yourself confronted with your boss’ request: “Hey man, let’s discuss with vendor #XYZ. They should support us here.” And with “let us” he of course means you. Or you’ve already talked with your vendor (or vendors) and you again and again observe some counterproductive situations, but you do not exactly know how to improve them.</p> <p>This episode enhances you to finish vendor discussions better as average. Or if you’re the vendor, you know exactly whether your customer is well prepared and honest with you in his request for explicit support.</p> <p>Stay with me and enjoy the chat.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>Why do we need to talk with the vendor?</li> <li>Why becomes the meeting invitation that essential?</li> <li>When you should cancel the meeting directly?</li> <li>How can you prepare for the meeting with your vendor?</li> <li>What kind of additional communication channels should you maintain during the meeting?</li> <li>When will superiors in the meeting become counterproductive?</li> <li>Why writing of minutes is the key-point in control?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://embeddedsuccess.com/mes008-3-mandatory-actions-to-successfully-launch-a-task-force" rel="nofollow" target="_blank">Episode #8 – How to successfully launch a task-force</a></li> <li><a href="https://embeddedsuccess.com/meeting-invitation-template" rel="nofollow" target="_blank">Meeting invitation template</a></li> <li><a href="https://embeddedsuccess.com/5-simple-tweaks-use-mind-maps-meeting-minutes-mes035" rel="nofollow" target="_blank">Episode #35 – 5 simple tweaks to use Mind-Maps for meeting minutes</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/5-hacks-to-succeed-in-discussions-with-your-vendor/" rel="nofollow" target="_blank">5 hacks to succeed in discussions with your vendor – MES044</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

5 hacks to succeed in discussions with your vendor - MES044

Tech Chat: Security in Embedded Systems with Andrey Nikishin You know such kind of story – everybody is talking about security, but not really everybody knows what it effectively means. Especially security in Embedded Systems has become a valid topic in the last years. My today’s guest has an intimate knowledge about all kind of aspects of security for Embedded Devices. I wanted to welcome Andrey Nikishin from Kaspersky Labs. Many of you will remember Kaspersky Labs as one of the main competitors in providing anti-virus software. However they have become much more. Andrey describes himself as evangelist of new technologies and new business directions. As an expert for cyber security he is working very closely with Kaspersky OS – an operating system designed for security from scratch. I got in touch with Andrey at the Embedded World in Nuremberg. I’ve seen their booth and initially thought: “What does the manufacturer of anti-virus software do at such exhibition?” I was so wrong! The threats towards security and integrity of embedded devices has grown heavily over the last decade. But that’s only one aspect. The other side of the medal are the ubiquitously available small embedded devices connected via the Internet. The bare amount of embedded systems in all parts of our life has dramatically increased during the last years. And they will still grow for the next decades. Andrey thankfully provided me some documents and white-papers about the mentioned topics. Have a look at them in the links-section below. Stay with me and enjoy the chat. Essential Answers Provided In This Episode For:  What has changed in the industry belonging security in the last two decades? Why Andrey’s dog is not (yet) connected? What actual security threats do we see for Embedded Devices? Security, safety, and functionality! How shall devices be built from the very beginning? What are the main drawbacks of traditional OSs belonging security? Why do we need a different way of thinking in SW-development? What should be considered by everybody when dealing with security? And much much more.  Selected Links and Resources From This Episode  Andrey Nikishin at LinkedIn Andrey Nikishin on Twitter Kaspersky Labs Kaspersky Labs – Industrial Cyber Security Kaspersky OS – Whitepaper KasperskyOS – Secure OS for the Internet of Thing KasperskyOS – Secure OS for Telecoms Environment Embedded World 2016   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Tech Chat: Security in Embedded Systems – MES036 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2016/05/AndreyNikishin_photo.png" rel="nofollow" target="_blank"></a>Tech Chat: Security in Embedded Systems with Andrey Nikishin</h2> <p>You know such kind of story – everybody is talking about security, but not really everybody knows what it effectively means. Especially security in Embedded Systems has become a valid topic in the last years. My today’s guest has an intimate knowledge about all kind of aspects of security for Embedded Devices. I wanted to welcome Andrey Nikishin from Kaspersky Labs.</p> <p>Many of you will remember Kaspersky Labs as one of the main competitors in providing anti-virus software. However they have become much more. Andrey describes himself as evangelist of new technologies and new business directions. As an expert for cyber security he is working very closely with Kaspersky OS – an operating system designed for security from scratch.</p> <p>I got in touch with Andrey at the Embedded World in Nuremberg. I’ve seen their booth and initially thought: “What does the manufacturer of anti-virus software do at such exhibition?” I was so wrong! The threats towards security and integrity of embedded devices has grown heavily over the last decade. But that’s only one aspect. The other side of the medal are the ubiquitously available small embedded devices connected via the Internet. The bare amount of embedded systems in all parts of our life has dramatically increased during the last years. And they will still grow for the next decades.</p> <p>Andrey thankfully provided me some documents and white-papers about the mentioned topics. Have a look at them in the links-section below.</p> <p>Stay with me and enjoy the chat.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What has changed in the industry belonging security in the last two decades?</li> <li>Why Andrey’s dog is not (yet) connected?</li> <li>What actual security threats do we see for Embedded Devices?</li> <li>Security, safety, and functionality! How shall devices be built from the very beginning?</li> <li>What are the main drawbacks of traditional OSs belonging security?</li> <li>Why do we need a different way of thinking in SW-development?</li> <li>What should be considered by everybody when dealing with security?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://uk.linkedin.com/in/andreynikishin" rel="nofollow" target="_blank">Andrey Nikishin at LinkedIn</a></li> <li><a href="https://twitter.com/andreynikishin" rel="nofollow" target="_blank">Andrey Nikishin on Twitter</a></li> <li><a href="http://kaspersky.com" rel="nofollow" target="_blank">Kaspersky Labs</a></li> <li><a href="http://www.kaspersky.com/enterprise-security/industrial" rel="nofollow" target="_blank">Kaspersky Labs – Industrial Cyber Security</a></li> <li><a href="https://embeddedsuccess.com/wp-content/uploads/2016/05/KasperskyOS-Whitepaper.pdf" rel="nofollow" target="_blank">Kaspersky OS – Whitepaper</a></li> <li><a href="https://embeddedsuccess.com/wp-content/uploads/2016/05/1788_KOS_for_IoT_Leaflet_A4_EN_3.pdf" rel="nofollow" target="_blank">KasperskyOS – Secure OS for the Internet of Thing</a></li> <li><a href="https://embeddedsuccess.com/wp-content/uploads/2016/05/1788_KOS_for_TelCom_Leaflet_A4_EN_3.pdf" rel="nofollow" target="_blank">KasperskyOS – Secure OS for Telecoms Environment</a></li> <li><a href="https://www.embedded-world.de/en" rel="nofollow" target="_blank">Embedded World 2016</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/tech-chat-security-embedded-systems-mes036/" rel="nofollow" target="_blank">Tech Chat: Security in Embedded Systems – MES036</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Tech Chat: Security in Embedded Systems - MES036

Baurzhan IsmagulovTech Chat: Virtualization in Embedded Systems with Baurzhan Ismagulov and Alexander SmirnovToday we’re talking about virtualization in Embedded Systems. This is particularly different from host-based virtualization. For that reason I wanted to welcome major experts in this special area: Baurzhan Ismagulov and Alexander Smirnov from Ilbers – Technology for better life.Ilbers provides Mango – a bare-metal Type 1 hypervisor. If you do not understand a word what this means – jump back to the previous episode #33 of the MES-podcast Combining the Uncombinable and fill up your missing knowledge. Mango was nominated for the Embedded Award 2015 at the Embedded World exhibition in Nuremberg. They have created a great piece of software which will provide a lot of benefit into embedded projects.Alexander Smirnov Already at the Embedded World I have had an amazing talk at their booth. But how much more deeper do we get into our todays tech-chat. We’re tackling the main use cases for using virtualization: combination and isolation. We’re discussing the main feature of Mango, as there are: static partitioning, bounded latency, no scheduler and a marvellous small footprint. And we come up with the general pros and cons of virtualization in embedded systems. For the latter have a look at Alexander’s talk at the Embedded Conference Scandinavia last year. For all the ones out there who believe in doing things by themselves. Here’s the deal: Ilbers provides a Mango-demonstrator for the BananaPI. Just study their Getting Started Manual and give it a try. But first, stay with me and enjoy the chat.  Essential Answers Provided In This Episode For:  What are typical use-cases for Mango? What kind of hardware is supported by Mango? How does Mango intercept the performance of the guest operating system? What’s the interdependency between Mango and the processor’s caches? What are the benefits of using Mango? What are the differences to other virtualization solutions? How can I get as BananaPi-based demonstrator? What are the pros and cons of virtualization in Embedded Systems? And much much more.  Selected Links and Resources From This Episode  Ilbers – Technology for better life Ilbers – Portfolio Mango – The Embedded Systems Hypervisor Mango – Github Baurzhan Ismagulov at LinkedIn Alexander Smirnov at LinkedIn Embedded Conference Scandinavia Embedded Conference Scandinavia program 2015 The Embedded World Award Embedded World 2016   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Tech Chat: Virtualization in Embedded Systems – MES034 appeared first on Embedded Success.

<p>Baurzhan Ismagulov</p><h2>Tech Chat: Virtualization in Embedded Systems with Baurzhan Ismagulov and Alexander Smirnov</h2><p>Today we’re talking about virtualization in Embedded Systems. This is particularly different from host-based virtualization. For that reason I wanted to welcome major experts in this special area: Baurzhan Ismagulov and Alexander Smirnov from <a href="http://ilbers.com" rel="nofollow" target="_blank">Ilbers – Technology for better life</a>.</p><p>Ilbers provides Mango – a bare-metal Type 1 hypervisor. If you do not understand a word what this means – jump back to the previous episode #33 of the MES-podcast <a href="https://embeddedsuccess.com/episode33" rel="nofollow" target="_blank">Combining the Uncombinable</a> and fill up your missing knowledge. Mango was nominated for the Embedded Award 2015 at the Embedded World exhibition in Nuremberg. They have created a great piece of software which will provide a lot of benefit into embedded projects.</p><a href="https://embeddedsuccess.com/wp-content/uploads/2016/04/Alexander-Smirnov-400x541.png" rel="nofollow" target="_blank"></a><p>Alexander Smirnov</p> <p>Already at the Embedded World I have had an amazing talk at their booth. But how much more deeper do we get into our todays tech-chat. We’re tackling the main use cases for using virtualization: combination and isolation. We’re discussing the main feature of Mango, as there are: static partitioning, bounded latency, no scheduler and a marvellous small footprint. And we come up with the general pros and cons of virtualization in embedded systems. For the latter have a look at <a href="http://www.slideshare.net/AlexanderSmirnov15/virtbenefits" rel="nofollow" target="_blank">Alexander’s talk</a> at the <a href="http://www.embeddedconference.se" rel="nofollow" target="_blank">Embedded Conference Scandinavia</a> last year.</p> <p>For all the ones out there who believe in doing things by themselves. Here’s the deal: Ilbers provides a Mango-demonstrator for the BananaPI. Just study their <a href="https://github.com/ilbers/meta-lotos/raw/master/doc/getting_started.pdf" rel="nofollow" target="_blank">Getting Started Manual</a> and give it a try.</p> <p>But first, stay with me and enjoy the chat.</p> <p></p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What are typical use-cases for Mango?</li> <li>What kind of hardware is supported by Mango?</li> <li>How does Mango intercept the performance of the guest operating system?</li> <li>What’s the interdependency between Mango and the processor’s caches?</li> <li>What are the benefits of using Mango?</li> <li>What are the differences to other virtualization solutions?</li> <li>How can I get as BananaPi-based demonstrator?</li> <li>What are the pros and cons of virtualization in Embedded Systems?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://ilbers.com" rel="nofollow" target="_blank">Ilbers – Technology for better life</a></li> <li><a href="http://www.ilbers.de/en/products.html" rel="nofollow" target="_blank">Ilbers – Portfolio</a></li> <li><a href="http://www.ilbers.de/en/mango.html" rel="nofollow" target="_blank">Mango – The Embedded Systems Hypervisor</a></li> <li><a href="https://github.com/ilbers" rel="nofollow" target="_blank">Mango – Github</a></li> <li><a href="https://www.linkedin.com/in/baurzhan-ismagulov-1309551" rel="nofollow" target="_blank">Baurzhan Ismagulov at LinkedIn</a></li> <li><a href="https://www.linkedin.com/in/alexander-smirnov-b05b6728" rel="nofollow" target="_blank">Alexander Smirnov at LinkedIn</a></li> <li><a href="http://www.embeddedconference.se" rel="nofollow" target="_blank">Embedded Conference Scandinavia</a></li> <li><a href="https://www.delegia.com/app/Data/ProjectImages/5796/ECS_agenda_2015-20sid.pdf" rel="nofollow" target="_blank">Embedded Conference Scandinavia program 2015</a></li> <li><a href="https://www.embedded-world.de/en/highlights/embedded-award" rel="nofollow" target="_blank">The Embedded World Award</a></li> <li><a href="https://www.embedded-world.de/en" rel="nofollow" target="_blank">Embedded World 2016</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/techchat-virtualization-in-embedded-systems/" rel="nofollow" target="_blank">Tech Chat: Virtualization in Embedded Systems – MES034</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Tech Chat: Virtualization in Embedded Systems - MES034

Jeronimo Castrillon-Mazo

Tech Chat: From SingleCore to MultiCore with Jeronimo Castrillon-Mazo Today it’s up to Jeronimo Castrillon-Mazo. We got acquainted at the Embedded World 2016 in Nuremberg. He is co-founder and adviser at Silexica. They have won the Embedded Award 2015 in the  Tools-category for SLX MultiCore Toolsuite. That drives me to visit their booth. Having an amazing talk I asked Jeronimo to appear in this podcast. Let’s have some tech-chat, widen the topic and enlarge the audience for this interesting topic. Jeronimo has studied Electrical Engineering in Colombia, achieved his Master-degree at ALaRI-institute in Lugano, Switzerland. He has made his Ph.D. 2013 at the well known RWTH Aachen. In 2014 Jeronimo joined the department of computer science of the TU Dresden as professor for compiler construction. He has a proven track record of multi- and many-core programming. Moreover he is known as specialist within the realm of automatic code generation.  Nowadays we have tons of single-core based legacy code. In parallel multicore hardware platforms have overtaken. Usually software for multicore needs to be designed manually. What might happen if the amount of cores still increases in future? How shall we handle existing code bases? Migrate all of them manually? Or might there be automatica ways to move towards multicore structures? And how can we improve software design for multicore deployment? For all of that the SLX MultiCore Toolsuite’s solutions will support. We’re discussing the benefits a tool has instead of redesigning code manually for multicore systems. We dive into the models and operations necessary to paralellize existing code. We identify user-stories and we mention tricky pitfalls. Jeronimo unveils details of automatic code-analysis and problems solved to provide a tool like SLX MultiCore. Stay with me and enjoy the chat. Essential Answers Provided In This Episode For:  What stands the SLX Multicore Toolsuite stands for? When does the attempt to parallelize do not make much sense? What kind of applications and languages are supported by SLX? Who are the 3 different kind of users? What different models are in use to support our migration from single- to multi-core? How do we handle and prevent race-conditions? How does Silexica prevent resource bottlenecks created by parallelism? What are the general benefits of using a tool like SLX? And much much more.  Selected Links and Resources From This Episode  SLX MultiCore Toolsuite Silexica at LinkedIn Silexica at Twitter Silexica at Facebook Jeronimo at LinkedIn The Embedded World Award Embedded World 2016   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Tech Chat: From SingleCore to MultiCore with Jeronimo Castrillon-Mazo – MES031 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2016/03/jeronimo4-800x533.jpg" rel="attachment wp-att-854 nofollow" target="_blank"></a>Tech Chat: From SingleCore to MultiCore with Jeronimo Castrillon-Mazo</h2> <p>Today it’s up to Jeronimo Castrillon-Mazo. We got acquainted at the Embedded World 2016 in Nuremberg. He is co-founder and adviser at Silexica. They have won the Embedded Award 2015 in the  Tools-category for <a href="http://www.silexica.com" rel="nofollow" target="_blank">SLX MultiCore Toolsuite</a>. That drives me to visit their booth. Having an amazing talk I asked Jeronimo to appear in this podcast. Let’s have some tech-chat, widen the topic and enlarge the audience for this interesting topic.</p> <p>Jeronimo has studied Electrical Engineering in Colombia, achieved his Master-degree at <a href="http://www.alari.ch" rel="nofollow" target="_blank">ALaRI-institute</a> in Lugano, Switzerland. He has made his Ph.D. 2013 at the well known <a href="www.ice.rwth-aachen.de" rel="nofollow" target="_blank">RWTH Aachen</a>. In 2014 Jeronimo joined the department of computer science of the TU Dresden as professor for compiler construction. He has a proven track record of multi- and many-core programming. Moreover he is known as specialist within the realm of automatic code generation.</p> <p></p> <p>Nowadays we have tons of single-core based legacy code. In parallel multicore hardware platforms have overtaken. Usually software for multicore needs to be designed manually. What might happen if the amount of cores still increases in future? How shall we handle existing code bases? Migrate all of them manually? Or might there be automatica ways to move towards multicore structures? And how can we improve software design for multicore deployment? For all of that the SLX MultiCore Toolsuite’s solutions will support.</p> <p>We’re discussing the benefits a tool has instead of redesigning code manually for multicore systems. We dive into the models and operations necessary to paralellize existing code. We identify user-stories and we mention tricky pitfalls. Jeronimo unveils details of automatic code-analysis and problems solved to provide a tool like SLX MultiCore.</p> <p>Stay with me and enjoy the chat.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What stands the SLX Multicore Toolsuite stands for?</li> <li>When does the attempt to parallelize do not make much sense?</li> <li>What kind of applications and languages are supported by SLX?</li> <li>Who are the 3 different kind of users?</li> <li>What different models are in use to support our migration from single- to multi-core?</li> <li>How do we handle and prevent race-conditions?</li> <li>How does Silexica prevent resource bottlenecks created by parallelism?</li> <li>What are the general benefits of using a tool like SLX?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://www.silexica.com" rel="nofollow" target="_blank">SLX MultiCore Toolsuite</a></li> <li><a href="https://www.linkedin.com/company/silexica" rel="nofollow" target="_blank">Silexica at LinkedIn</a></li> <li><a href="https://twitter.com/silexica" rel="nofollow" target="_blank">Silexica at Twitter</a></li> <li><a href="https://www.facebook.com/Silexica-785768688111895" rel="nofollow" target="_blank">Silexica at Facebook</a></li> <li><a href="https://de.linkedin.com/in/jeronimo-castrillon-6161327" rel="nofollow" target="_blank">Jeronimo at LinkedIn</a></li> <li><a href="https://www.embedded-world.de/en/highlights/embedded-award" rel="nofollow" target="_blank">The Embedded World Award</a></li> <li><a href="https://www.embedded-world.de/en" rel="nofollow" target="_blank">Embedded World 2016</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/tech-chat-multi-core/" rel="nofollow" target="_blank">Tech Chat: From SingleCore to MultiCore with Jeronimo Castrillon-Mazo – MES031</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Tech Chat: From SingleCore to MultiCore with Jeronimo Castrillon-Mazo - MES031

Muda, Mura and Muri I have recorded this episode twice. Not by intention – far away from that. But I was neither convinced nor satisfied with the first recording. Also the subject was not really impressive and I decided to do it again from scratch. Thus I got a first hand impression what waste of time and effort is. However one detail in the first record was amazing. It was about waste in SW-development.  You remember episode 4? Already there I have mentioned waste due to over-processing and over-engineering. Both are part of the 7 forms of regular waste in any kind of system. The Toyota Production System (TPS) has introduced to a broader audience the classification of waste forms. In this episode I wanted to connect traditional manufacturing based Kaizen and Muda, Mura, and Muri with Software-development. Is it possible? Do we have parallels? Or is the TPS not adaptable to nowadays IT-based technology? Stay with me and enjoy the show. Essential Answers Provided In This Episode For: What is Kaizen? Kaizen is Japanese and means Improvement. It is regularly used in conjunction with Continuous Improvement. However that’s not the original intention. Kaizen stands for the understanding and the wish that everything can be improved. Why are there different kind of wastes? The classification of wastes for manufacturing and assembly purpose is one of the key-concepts in the Toyota Production System (TPS) as one of the three types of deviation from optimal allocation of resources (muda, mura, muri).[2]. Waste reduction is an effective way to increase profitability. What does Muda stand for? Lean and TPS knows the key step to distinguish between manufacturing steps which add value and which don’t. The classification of all processes involved into these two categories let one improve the one and eliminate the other. That means Muda is any activity or process which does not add value. Thus it is a physical waste of time, effort, resources and finally money. Which forms of waste does Muda indicate?  Transport; the movement of product between operations, and locations. Inventory; the work in progress (WIP) and stocks of finished goods and raw materials that a company holds. Motion; the physical movement of a person or machine whilst conducting an operation. Waiting; the act of waiting for a machine to finish, for product to arrive, or any other cause. Over-Production; Over producing product beyond what the customer has ordered. Over-Processing; conducting operations beyond those that customer requires. Defects; product rejects and rework within your processes.  Which forms of waste cannot be adapted to SW-development? In principle can all forms of waste in Muda be used for SW-development, too. However some of them are quite seldom and do not effectively match always, like Transport or Motion. However others, like Over-Production, Over-Processing and of course Defects seem like exclusively made for SW-development. What does Mura and Muri stand for? Mura and Muri define some more abstract ways how waste can be finally created in Muda-categories. Mura and Muri drive Muda. Mura stands for the waste of unevenness. If the available men, material and equipment are used in a non-balanced way, this finally will result in waste. For example, four weeks ahead of an upcoming milestone the previous measured way of working is changed into a more hectic, confuse and challenging action. The probability of waste, especially defects, will increase. This can be prevented by steering the utilization of all resources in a balanced way. Muri stands for the waste of overburden. If there is unnecessary stress given on employees and processes this will cause Mura and then Muda. Permanent overburden will cause absences of employees, increase of sickness-rate and finally a higher attrition rate. Selected Links and Resources From This Episode  Kaizen Muda The 7 wastes of Muda Muda – Mura – Muri   [saf feature="email" cta="Send me feedback"][saf feature="twitter" cta="Reply on Twitter"] Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Muda, Mura and Muri – Waste in SW-development – MES024 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2015/12/public-bin-for-recycling-1446635-640x480.jpg" rel="attachment wp-att-822 nofollow" target="_blank"></a>Muda, Mura and Muri</h2> <p>I have recorded this episode twice. Not by intention – far away from that. But I was neither convinced nor satisfied with the first recording. Also the subject was not really impressive and I decided to do it again from scratch. Thus I got a first hand impression what waste of time and effort is. However one detail in the first record was amazing. It was about waste in SW-development.</p> <p></p> <p>You remember <a href="https://embeddedsuccess.com/episode4" rel="nofollow" target="_blank">episode 4</a>? Already there I have mentioned waste due to over-processing and over-engineering. Both are part of the 7 forms of regular waste in any kind of system.</p> <p>The <em>Toyota Production System</em> (TPS) has introduced to a broader audience the classification of waste forms. In this episode I wanted to connect traditional manufacturing based Kaizen and Muda, Mura, and Muri with Software-development. Is it possible? Do we have parallels? Or is the TPS not adaptable to nowadays IT-based technology?</p> <p>Stay with me and enjoy the show.</p> <h2>Essential Answers Provided In This Episode For:</h2> <h3>What is Kaizen?</h3> <p><a href="https://en.wikipedia.org/wiki/Kaizen" rel="nofollow" target="_blank">Kaizen</a> is Japanese and means <em>Improvement</em>. It is regularly used in conjunction with <em>Continuous Improvement</em>. However that’s not the original intention. <em>Kaizen</em> stands for the understanding and the wish that everything can be improved.</p> <h3>Why are there different kind of wastes?</h3> <p>The classification of wastes for manufacturing and assembly purpose is one of the key-concepts in the <em>Toyota Production System</em> (TPS) as one of the three types of deviation from optimal allocation of resources (muda, mura, muri).[2]. Waste reduction is an effective way to increase profitability.</p> <h3>What does Muda stand for?</h3> <p>Lean and TPS knows the key step to distinguish between manufacturing steps which add value and which don’t. The classification of all processes involved into these two categories let one improve the one and eliminate the other. That means Muda is any activity or process which does not add value. Thus it is a physical waste of time, effort, resources and finally money.</p> <h3>Which forms of waste does Muda indicate?</h3> <ul> <li><em>Transport</em>; the movement of product between operations, and locations.</li> <li><em>Inventory</em>; the work in progress (WIP) and stocks of finished goods and raw materials that a company holds.</li> <li><em>Motion</em>; the physical movement of a person or machine whilst conducting an operation.</li> <li><em>Waiting</em>; the act of waiting for a machine to finish, for product to arrive, or any other cause.</li> <li><em>Over-Production</em>; Over producing product beyond what the customer has ordered.</li> <li><em>Over-Processing</em>; conducting operations beyond those that customer requires.</li> <li><em>Defects</em>; product rejects and rework within your processes.</li> </ul> <h3>Which forms of waste cannot be adapted to SW-development?</h3> <p>In principle can all forms of waste in Muda be used for SW-development, too. However some of them are quite seldom and do not effectively match always, like Transport or Motion. However others, like <em>Over-Production</em>, <em>Over-Processing</em> and of course <em>Defects</em> seem like exclusively made for SW-development.</p> <h3>What does Mura and Muri stand for?</h3> <p><em>Mura</em> and <em>Muri</em> define some more abstract ways how waste can be finally created in <em>Muda</em>-categories. <em>Mura</em> and <em>Muri</em> drive <em>Muda</em>.</p> <p><em>Mura</em> stands for the <em>waste of </em>unevenness. If the available men, material and equipment are used in a non-balanced way, this finally will result in waste. For example, four weeks ahead of an upcoming milestone the previous measured way of working is changed into a more hectic, confuse and challenging action. The probability of waste, especially defects, will increase. This can be prevented by steering the utilization of all resources in a balanced way.</p> <p><em>Muri</em> stands for the <em>waste of overburden</em>. If there is unnecessary stress given on employees and processes this will cause <em>Mura</em> and then <em>Muda</em>. Permanent overburden will cause absences of employees, increase of sickness-rate and finally a higher attrition rate.</p> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://en.wikipedia.org/wiki/Kaizen" rel="nofollow" target="_blank">Kaizen</a></li> <li><a href="https://en.wikipedia.org/wiki/Muda_(Japanese_term)" rel="nofollow" target="_blank">Muda</a></li> <li><a href="http://leanmanufacturingtools.org/77/the-seven-wastes-7-mudas" rel="nofollow" target="_blank">The 7 wastes of Muda</a></li> <li><a href="http://leanmanufacturingtools.org/71/muda-mura-and-muri-lean-manufacturing-wastes" rel="nofollow" target="_blank">Muda – Mura – Muri</a></li> </ul> <h2></h2> <p><code>[saf feature="email" cta="Send me feedback"][saf feature="twitter" cta="Reply on Twitter"]</code></p> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/muda-mura-and-muri-waste-in-sw-development-mes024/" rel="nofollow" target="_blank">Muda, Mura and Muri – Waste in SW-development – MES024</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Muda, Mura and Muri - Waste in SW-development - MES024

Engineers’ Talk: DevOp and Tester Vassilis Rizopoulos You remember episode 20 where I mentioned the Embedded Testing conference in Munich. One of the presentation was about Applying DevOps Principles to Software-Hardware Integration Test. Vassilis Rizopoulus explained details about DevOps, their tooling, automated testing and the mandatory environment. I was excited and we have had an extraordinary talk after his contribution. Some days later I asked him for an interview. I am sure that Vassilis’ ideas and thoughts will be helpful for a lot of engineers out there. Especially engineers who wanted to try something knew, but who might need some trigger to change their way of thinking and habit. Vassilis has been dabbling in software engineering close to two decades by now. In this time what started as a hobby of a would-be electrical engineer became full time occupation. He specializes in software productivity engineering, a catch all term for the role that integrates the development environment, test automation, continuous integration and deployment, devops and general behind the scenes tooling that enables software teams to concentrate on actually producing useful software.  His language of choice is Ruby and has been for the past dozen of years, but he also has several C and C++ embedded projects under his belt as well as a few C# .NET projects. Most of his professional career has been spent working for large industry firms doing really close to the metal stuff, from devices smaller than an Oreo cookie to as large as 60-ton locomotives. He is one of the co-founders and organizers of thessaloniki.rb the Thessaloniki Ruby Users group and also had the luck to be part of the organizing committee for EuRuKo 2013 that took place in Athens. Whatever free time remains between deadlines and family life goes into open source projects mainly in the Ruby community with the lion’s share reserved for rutema and gaudi. In the Engineers’ Talk we’re discussing about DevOp-priniciples. His will to automatize everything. The infrastructure you need for day-by-day development. And of course the mother of all questions: what are the differences between SW-tester and SW-developer. Stay with me and enjoy the interview. Essential Answers Provided In This Episode For:  What are the DevOps-principles? How does typical tooling for DevOps look like? Why does Vassilis describe himself as Testing hardliner? Where does the classic SW-developer distinguish from a DevOp-Tester Why is it essential to treat your environment as code? What are the 3 most important skills a good and successful tester should have? And much much more.  Selected Links and Resources From This Episode  Vassilis’ personal blog Vassilis’ company blog Vassilis’ github repository Vassilis on Twitter Vassilis on LinkedIn Euruko 2013   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Engineers’ Talk – DevOp and Tester Vassilis Rizopoulos – MES023 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2015/12/Vassilis-Rizopoulos.jpg" rel="nofollow" target="_blank"></a>Engineers’ Talk: DevOp and Tester Vassilis Rizopoulos</h2> <p>You remember <a href="https://embeddedsuccess.com/episode20" rel="nofollow" target="_blank">episode 20</a> where I mentioned the <em>Embedded Testing</em> conference in Munich. One of the presentation was about <em>Applying DevOps Principles to Software-Hardware Integration Test</em>. Vassilis Rizopoulus explained details about DevOps, their tooling, automated testing and the mandatory environment.</p> <p>I was excited and we have had an extraordinary talk after his contribution. Some days later I asked him for an interview. I am sure that Vassilis’ ideas and thoughts will be helpful for a lot of engineers out there. Especially engineers who wanted to try something knew, but who might need some trigger to change their way of thinking and habit.</p> <p>Vassilis has been dabbling in software engineering close to two decades by now. In this time what started as a hobby of a would-be electrical engineer became full time occupation. He specializes in <em>software productivity engineering</em>, a catch all term for the role that integrates the development environment, test automation, continuous integration and deployment, devops and general behind the scenes tooling that enables software teams to concentrate on actually producing useful software.</p> <p></p> <p>His language of choice is Ruby and has been for the past dozen of years, but he also has several C and C++ embedded projects under his belt as well as a few C# .NET projects. Most of his professional career has been spent working for large industry firms doing really close to the metal stuff, from devices smaller than an Oreo cookie to as large as 60-ton locomotives. He is one of the co-founders and organizers of <a href="http://thessaloniki.rb" rel="nofollow" target="_blank">thessaloniki.rb</a> the Thessaloniki Ruby Users group and also had the luck to be part of the organizing committee for <a href="http://euruko2013.org/" rel="nofollow" target="_blank">EuRuKo 2013</a> that took place in Athens. Whatever free time remains between deadlines and family life goes into open source projects mainly in the Ruby community with the lion’s share reserved for <a href="http://github.com/damphyr/rutema" rel="nofollow" target="_blank">rutema</a> and <a href="http://github.com/damphyr/gaudi" rel="nofollow" target="_blank">gaudi</a>.</p> <p>In the Engineers’ Talk we’re discussing about DevOp-priniciples. His will to automatize everything. The infrastructure you need for day-by-day development. And of course the mother of all questions: what are the differences between SW-tester and SW-developer.</p> <p>Stay with me and enjoy the interview.</p> <h2>Essential Answers Provided In This Episode For:</h2> <ul> <li>What are the DevOps-principles?</li> <li>How does typical tooling for DevOps look like?</li> <li>Why does Vassilis describe himself as <em>Testing hardliner</em>?</li> <li>Where does the classic SW-developer distinguish from a DevOp-Tester</li> <li>Why is it essential to treat your environment as code?</li> <li>What are the 3 most important skills a good and successful tester should have?</li> <li>And much much more.</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://www.ampelofilosofies.gr/" rel="nofollow" target="_blank">Vassilis’ personal blog</a></li> <li><a href="http://blog.zuehlke.com/en/author/vassilis-rizopoulos/" rel="nofollow" target="_blank">Vassilis’ company blog</a></li> <li><a href="https://github.com/damphyr" rel="nofollow" target="_blank">Vassilis’ github repository</a></li> <li><a href="https://twitter.com/arcandros" rel="nofollow" target="_blank">Vassilis on Twitter</a></li> <li><a href="https://gr.linkedin.com/in/vassilis-rizopoulos-7369512" rel="nofollow" target="_blank">Vassilis on LinkedIn</a></li> <li><a href="http://euruko2013.org/" rel="nofollow" target="_blank">Euruko 2013</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/engineers-talk-devop-and-tester-vassilis-rizopoulos-mes023/" rel="nofollow" target="_blank">Engineers’ Talk – DevOp and Tester Vassilis Rizopoulos – MES023</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Engineers' Talk - DevOp and Tester Vassilis Rizopoulos - MES023

How everything started – My way to the PDP-11 Holy moly, seems I’m getting old. Two times in the last two weeks I was confronted with this fact. Things which are part of my experience are nostalgic for others. They have never seen or touched them. What has happened? One day I saw an update in LinkedIn highlighting DEC’s PDP-11 as an old system. That’s nothing extraordinary. It is old. But one of my colleagues mentioned it as nostalgic. Bumm, right in the face.  Second, I got a mail by another colleague. In his signature he mentioned that this mail was written from his PDP-11. I doubted this, but he showed me a picture showing him from the backside (hopefully it is him) and a PDP-11 aside. That picture must be old. I do not consider that he really has a PDP-11 in his cellar. But both moments let me think back into that time 30, 40 years ago. Computer Systems were different. Computer Science was slightly different. And of course the systems you own or you could directly touch were dramitically different. Compared with the systems available nowadays the are more like flintstones than real lighters. And these thoughts created this episode. I wanted to go back with you showing some highlights in my computer-life. Not for nostalgic reasons, but to make you aware that things were really different at that time. And that it is of some benefit to know a little bit about it, to understand the situation we’re currently in. Please pay special attention on this video showing the startup phase of the PDP-11. Essential Answers Provided In This Episode For:  Why was the TI-59 hand calculator that desirable? Together with its printer and its magnetic card it was – more or less – a fully equiped computer system. The price was horrible. But it still was only a fraction of a real computer system. What should you take care for if you carry punching cards? As each punching card is representing one line of your batch-job, you should take care that the order is not corrupted. Stumbling or shuffling has to be prevented at any price. Why could the mounting of storage be embarrassing? Mounting of devices at that time really meant that someone, the operator, physically lifted the storage into a storage-equipment. If you liked to mount some storage you do not have privileges for, the operator might come personally to your working place offending you as stupid moron. How could the Atari ST have such a great success? The Atari ST was the first fully graphical desktop system. With its GEM Operating System it opened a whole new world. Out of the familiar character based limitation into the freedom of fully flexible presentation. What was the most weirdest action you have to do with the PDP-11? The PDP-11 has had to be started by using the front-panel in-line keys. These keys were set representing the address and the octal data to setup the boot-code. Why should you know Assembler languages? If you like to deal with computers on a more technical level you should know their very basic language. And assembler is mnemonized object-code. If you know assembler you are directly in touch with the bare metal. Mandatory if you need to know for sure what’s going on. And much much more.   Selected Links and Resources From This Episode  TI-58 and TI-59 HP-41C Atari ST Starting the PDP See 2:40   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post How everything started – My way to the PDP-11 – MES021 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2015/11/Pdp-11-40.jpg" rel="nofollow" target="_blank"></a>How everything started – My way to the PDP-11</h2> <p>Holy moly, seems I’m getting old. Two times in the last two weeks I was confronted with this fact. Things which are part of my experience are nostalgic for others. They have never seen or touched them.</p> <p>What has happened? One day I saw an update in LinkedIn highlighting DEC’s PDP-11 as an old system. That’s nothing extraordinary. It is old. But one of my colleagues mentioned it as nostalgic. Bumm, right in the face.</p> <p></p> <p>Second, I got a mail by another colleague. In his signature he mentioned that this mail was written from his PDP-11. I doubted this, but he showed me a picture showing him from the backside (hopefully it is him) and a PDP-11 aside. That picture must be old. I do not consider that he really has a PDP-11 in his cellar.</p> <p>But both moments let me think back into that time 30, 40 years ago. Computer Systems were different. Computer Science was slightly different. And of course the systems you own or you could directly touch were dramitically different. Compared with the systems available nowadays the are more like flintstones than real lighters.</p> <p>And these thoughts created this episode. I wanted to go back with you showing some highlights in my computer-life. Not for nostalgic reasons, but to make you aware that things were really different at that time. And that it is of some benefit to know a little bit about it, to understand the situation we’re currently in.</p> <p>Please pay special attention on this video showing the <a href="https://www.youtube.com/watch?v=XV-7J5y1TQc" rel="nofollow" target="_blank">startup phase of the PDP-11</a>.</p> <h2>Essential Answers Provided In This Episode For:</h2> <p><a href="https://embeddedsuccess.com/wp-content/uploads/2015/11/TI-59_and_PC-100A.jpg" rel="nofollow" target="_blank"></a></p> <h3>Why was the TI-59 hand calculator that desirable?</h3> <p>Together with its printer and its magnetic card it was – more or less – a fully equiped computer system. The price was horrible. But it still was only a fraction of a real computer system.</p> <h3>What should you take care for if you carry punching cards?</h3> <p><a href="https://embeddedsuccess.com/wp-content/uploads/2015/11/FortranCardPROJ039.agr_.jpg" rel="nofollow" target="_blank"></a>As each punching card is representing one line of your batch-job, you should take care that the order is not corrupted. Stumbling or shuffling has to be prevented at any price.</p> <h3>Why could the mounting of storage be embarrassing?</h3> <p>Mounting of devices at that time really meant that someone, the operator, physically lifted the storage into a storage-equipment. If you liked to mount some storage you do not have privileges for, the operator might come personally to your working place offending you as stupid moron.</p> <h3>How could the Atari ST have such a great success?</h3> <p><a href="https://embeddedsuccess.com/wp-content/uploads/2015/11/Atari_1040STf.jpg" rel="nofollow" target="_blank"></a>The Atari ST was the first fully graphical desktop system. With its GEM Operating System it opened a whole new world. Out of the familiar character based limitation into the freedom of fully flexible presentation.</p> <h3>What was the most weirdest action you have to do with the PDP-11?</h3> <p>The PDP-11 has had to be started by using the front-panel in-line keys. These keys were set representing the address and the octal data to setup the boot-code.</p> <h3>Why should you know Assembler languages?</h3> <p>If you like to deal with computers on a more technical level you should know their very basic language. And assembler is mnemonized object-code. If you know assembler you are directly in touch with the bare metal. Mandatory if you need to know for sure what’s going on.</p> <h3>And much much more.</h3> <p> </p> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://en.wikipedia.org/wiki/TI-59_/_TI-58" rel="nofollow" target="_blank">TI-58 and TI-59</a></li> <li><a href="https://en.wikipedia.org/wiki/HP-41C" rel="nofollow" target="_blank">HP-41C</a></li> <li><a href="https://en.wikipedia.org/wiki/Atari_ST" rel="nofollow" target="_blank">Atari ST</a></li> <li><a href="https://www.youtube.com/watch?v=XV-7J5y1TQc" rel="nofollow" target="_blank">Starting the PDP</a> See 2:40</li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/how-everything-started-my-way-to-the-pdp-11-mes021/" rel="nofollow" target="_blank">How everything started – My way to the PDP-11 – MES021</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

How everything started - My way to the PDP-11 - MES021

Was your last conference poor? You know conferences. For sure you do. You might be a fan of them. Or not. You might be disappointed. As I was after visiting the Embedded Testing 2015 in Munich last week. Although I was invented as presenter, I was not convinced. I mean the topic was really good – no other conference or meeting available covering exactly this specific part in the Embedded Systems realm. But the conference got stuck as a sponsor-driven event which highlights products over general knowledge, marketing over sharing of experience. One could have made a lot more out of this conference. So the participants have finally had only their others to get acquainted with each other, hear the problems, discuss and finally detect the old rule, that the best of conferences are the pauses. Free time which can be used for connecting and sharing.  In this episode I wanted to highlight the approach of traditional conferences in comparison to BarCamps. A BarCamp is an un-conference born from the desire for people to share and learn in an open environment. It is the direct response on all attendees who wanted to create and design their own agenda of content. For me BarCamps, the un-conferences are by far the better conferences. Listen to this episode and create understanding about this popular approach to confer. Essential Answers Provided In This Episode For: What do participants expect from traditional conferences? And what do they really get? Attendees regularly expect sharing of information, knowledge experience. They very often expect ideas and impulses for their own problems. They regularly focus on problem solving. Instead they get sponsors’ driven events only highlighting their own products and particular approaches. What is most missing from traditional conferences? The opportunity to make an impact on the sessions, their schedule or the selection of presentations. Very often there are only one or two presentations you’re really interested in. Why is the quintessence of traditional conferences that poor? As many of the conferences are sponsored the companies behind try to monetize their presentation for their own purposes. That often results in pure product presentation and selling event. This again thwarts the expectations of the audience. What are BarCamps? BarCamps are un-conferences not following the traditional approach of given schedule and predefined structure of speakers. People share and learn in an open environment not preferring the presenter over the audience. Do these kind of un-conferences have rules? And if so, what kind of rules? There are several pre-defined as also inofficial rulse. Listen into the episode to get some of them in detail. The general rules could be also find at BarCamp-rules. When should you prefer BarCamps instead of traditional conferences? If you want to experience know-how and get acquainted with interesting characters out of your environment or industry. You should join BarCamps if you’re interested more in sharing of expertise and problem-solving experience than in particular products. What is expected from you if you join a BarCamp? There are no spectators, but only participants. It is expected that you do not only consume, but actively engage yourself into the sessions, the discussion and share your knowledge. And much much more. Selected Links and Resources From This Episode  Engineers’ talk: Internet of Things with Marcus Behrens – MES007 BarCamp Definition by Wikipedia BarCamp.org Hackathon CloudCamp BarCamp Definition and Rules PMCamp Barcelona Sessions PMCamps in Europe PMCamp Dornbirn registration   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Was your last conference poor? – MES020 appeared first on Embedded Success.

<h2><a href="https://embeddedsuccess.com/wp-content/uploads/2015/11/Conference-.png" rel="nofollow" target="_blank"></a>Was your last conference poor?</h2> <p>You know conferences. For sure you do. You might be a fan of them. Or not. You might be disappointed. As I was after visiting the Embedded Testing 2015 in Munich last week. Although I was invented as presenter, I was not convinced. I mean the topic was really good – no other conference or meeting available covering exactly this specific part in the Embedded Systems realm.</p> <p>But the conference got stuck as a sponsor-driven event which highlights products over general knowledge, marketing over sharing of experience. One could have made a lot more out of this conference. So the participants have finally had only their others to get acquainted with each other, hear the problems, discuss and finally detect the old rule, that the best of conferences are the pauses. Free time which can be used for connecting and sharing.</p> <p></p> <p>In this episode I wanted to highlight the approach of traditional conferences in comparison to BarCamps. A BarCamp is an <em>un-conference born from the desire for people to share and learn in an open environment.</em> It is the direct response on all attendees who wanted to create and design their own agenda of content.</p> <p>For me BarCamps, the <em>un-conferences</em> are by far the better conferences. Listen to this episode and create understanding about this popular approach to confer.</p> <h2>Essential Answers Provided In This Episode For:</h2> <h3>What do participants expect from traditional conferences? And what do they really get?</h3> <p>Attendees regularly expect sharing of information, knowledge experience. They very often expect ideas and impulses for their own problems. They regularly focus on problem solving. Instead they get sponsors’ driven events only highlighting their own products and particular approaches.</p> <h3>What is most missing from traditional conferences?</h3> <p>The opportunity to make an impact on the sessions, their schedule or the selection of presentations. Very often there are only one or two presentations you’re really interested in.</p> <h3>Why is the quintessence of traditional conferences that poor?</h3> <p>As many of the conferences are sponsored the companies behind try to monetize their presentation for their own purposes. That often results in pure product presentation and selling event. This again thwarts the expectations of the audience.</p> <h3>What are BarCamps?</h3> <p><em>BarCamps</em> are <em>un-conferences</em> not following the traditional approach of given schedule and predefined structure of speakers. People share and learn in an open environment not preferring the presenter over the audience.</p> <h3>Do these kind of <em>un-conferences</em> have rules? And if so, what kind of rules?</h3> <p>There are several pre-defined as also inofficial rulse. Listen into the episode to get some of them in detail. The general rules could be also find at <a href="http://barcamp.org/w/page/405173/TheRulesOfBarCamp" rel="nofollow" target="_blank">BarCamp-rules</a>.</p> <h3>When should you prefer BarCamps instead of traditional conferences?</h3> <p>If you want to experience know-how and get acquainted with interesting characters out of your environment or industry. You should join BarCamps if you’re interested more in sharing of expertise and problem-solving experience than in particular products.</p> <h3>What is expected from you if you join a BarCamp?</h3> <p>There are no spectators, but only participants. It is expected that you do not only consume, but actively engage yourself into the sessions, the discussion and share your knowledge.</p> <h3>And much much more.</h3> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://embeddedsuccess.com/episode07" rel="nofollow" target="_blank">Engineers’ talk: Internet of Things with Marcus Behrens – MES007</a></li> <li><a href="https://en.wikipedia.org/wiki/BarCamp" rel="nofollow" target="_blank">BarCamp Definition by Wikipedia</a></li> <li><a href="http://www.barcamp.org" rel="nofollow" target="_blank">BarCamp.org</a></li> <li><a href="https://en.wikipedia.org/wiki/Hackathon" rel="nofollow" target="_blank">Hackathon</a></li> <li><a href="https://en.wikipedia.org/wiki/CloudCamp" rel="nofollow" target="_blank">CloudCamp</a></li> <li><a href="http://barcamp.org/w/page/405173/TheRulesOfBarCamp" rel="nofollow" target="_blank">BarCamp Definition and Rules</a></li> <li><a href="https://www.openpm.info/display/openPM/PM+Camp+Barcelona+2015+-+Sessions" rel="nofollow" target="_blank">PMCamp Barcelona Sessions</a></li> <li><a href="http://www.pm-camp.org/wpx/" rel="nofollow" target="_blank">PMCamps in Europe</a></li> <li><a href="https://www.xing.com/events/pm-camp-dornbirn-2015-1600126" rel="nofollow" target="_blank">PMCamp Dornbirn registration</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/was-your-last-conference-poor-mes020/" rel="nofollow" target="_blank">Was your last conference poor? – MES020</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Was your last conference poor? - MES020

In the first session about root-cause analysis we have introduced the 5-Whys technique. It has its benefits, but also some severe disadvantages. As one of the most obvious ones the limitation on one root-cause can be highlighted. In this episode the Ishikawa technique will be introduced. The Ishikawa-diagram could be assumed as the big brother of the small 5-Whys. The Ishikawa covers all the limitations of the 5-Whys and provides a great way to also handle multiple root-causes and more complicated effects. But it also has its disadvantages and pitfalls.  Root-causes and the Ishikawa technique The Ishikawa-technique is a graphical approach combining both, Brainstorming and Mind-Mapping. It is a valuable technique for group sessions. You will be astonished how progressive and fast you achieve results using the Ishikawa-approach. If you need to dig deeper in your root-cause finding, then you will sooner or later be confronted with Ishikawa. Take this episode as your personal guidance to get an instant understanding how the technique is done. Moreover take my experiences with Ishikawa to circumvent usual problems and overcome common obstacles. Essential Know-How Provided In This Episode:  What helpful tools can be used to create an Ishikawa-diagram? Are there templates for the Ishikawa? When should Ishikawa be used preferrably? Which predefined categories of causes could you use in your Ishikawa? What’s the difference between sufficient and necessary? How mind-mapping can assist you with Ishikawa? And much much more  Possible categories of causes  Traditional: Man, Machine, Milieu, Material, Method, Measurement 4 P’s of Marketing: Product, Place, Price, Promotion 7 P’s of Marketing: Product, Place, Price, Promotion, People/Personel, Process, Physical Evidence 5 M’s of Manufacturing: Machine (technology), Method (process), Material (includes Raw Material, Consumables, but also Information) 5 S’s in Services: Surroundings, Suppliers, Systems, Skills, Safety 7 S’s of McKinsey: Strategy, Structure, Systems, Share Values, Skills, Style, Staff My favorite: Measurement (inspection), Milieu (environment), Equipment, Material (Information), Methods (Processes), People, Management  Selected Links and Resources From This Episode  Cause and Effect Fishbone Diagram Work visually, agile and boost your creativity and project with Stattys   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Finding root-causes with Ishikawa – MES014 appeared first on Embedded Success.

<p>In the <a href="https://embeddedsuccess.com/episode09" rel="nofollow" target="_blank">first session about root-cause analysis</a> we have introduced the 5-Whys technique. It has its benefits, but also some severe disadvantages. As one of the most obvious ones the limitation on one root-cause can be highlighted.</p> <p>In this episode the <em>Ishikawa</em> technique will be introduced. The <em>Ishikawa</em>-diagram could be assumed as the big brother of the small 5-Whys. The <em>Ishikawa</em> covers all the limitations of the 5-Whys and provides a great way to also handle multiple root-causes and more complicated effects. But it also has its disadvantages and pitfalls.</p> <p></p> <h2>Root-causes and the Ishikawa technique</h2> <p>The <em>Ishikawa</em>-technique is a graphical approach combining both, Brainstorming and Mind-Mapping. It is a valuable technique for group sessions. You will be astonished how progressive and fast you achieve results using the<em> Ishikawa</em>-approach.</p> <p>If you need to dig deeper in your root-cause finding, then you will sooner or later be confronted with Ishikawa. Take this episode as your personal guidance to get an instant understanding how the technique is done. Moreover take my experiences with <em>Ishikawa</em> to circumvent usual problems and overcome common obstacles.</p> <h2>Essential Know-How Provided In This Episode:</h2> <ul> <li>What helpful tools can be used to create an <em>Ishikawa</em>-diagram?</li> <li>Are there templates for the <em>Ishikawa</em>?</li> <li>When should <em>Ishikawa</em> be used preferrably?</li> <li>Which predefined categories of causes could you use in your Ishikawa?</li> <li>What’s the difference between <em>sufficient</em> and <em>necessary</em>?</li> <li>How mind-mapping can assist you with Ishikawa?</li> <li>And much much more</li> </ul> <h2>Possible categories of causes</h2> <ul> <li><strong>Traditional</strong>: Man, Machine, Milieu, Material, Method, Measurement</li> <li><strong>4 P’s of Marketing</strong>: Product, Place, Price, Promotion</li> <li><strong>7 P’s of Marketing</strong>: Product, Place, Price, Promotion, People/Personel, Process, Physical Evidence</li> <li><strong>5 M’s of Manufacturing</strong>: Machine (technology), Method (process), Material (includes Raw Material, Consumables, but also Information)</li> <li><strong>5 S’s in Services</strong>: Surroundings, Suppliers, Systems, Skills, Safety</li> <li><strong>7 S’s of McKinsey</strong>: Strategy, Structure, Systems, Share Values, Skills, Style, Staff</li> <li><strong>My favorite</strong>: Measurement (inspection), Milieu (environment), Equipment, Material (Information), Methods (Processes), People, Management</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="http://www.youtube.com/embed/wImI1ItrgfI" rel="nofollow" target="_blank">Cause and Effect Fishbone Diagram</a></li> <li>Work visually, agile and boost your creativity and project with <a href="http://www.stattys.com" rel="nofollow" target="_blank">Stattys</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes014-finding-root-causes-with-ishikawa/" rel="nofollow" target="_blank">Finding root-causes with Ishikawa – MES014</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Finding root-causes with Ishikawa - MES014

Robert Schiele

Tools and Building This episode is about building, maintaining and distributing tools and operating system in large scale projects. With Robert Schiele an expert on all this kind of topics stays with me. He is senior specialist for developing OS-tools, providing toolchains and building operating systems. Robert provides dedicated and verbose insights into the Linux Kernel and the Linux Operating System in particular. He’s one of the guys I know who is eagerly engaged into the OpenSource-community.  In his current role he maintains development tools and OpenSource components for a global mobile network supplier. His main task is to provide running build-systems, tool-chains, toolsets and root-filesystems. He has seen and resolved a lot of problems when providing tools and operating systems. Especially for large scale systems and multiple hardware platforms in multi-site environments. We’re talking about build-systems, root file systems, native and cross building. We tackle observable problems with distributed environments. We discuss about struggles with multiple hardware platforms. And we give you a close look into the way how well prepared tools-provisioning saves you time and prevents waste. Essential Know-How Provided In This Episode:  What are the main challenges when building large scale systems? How can a good building system support you or waste your time dramatically? When to prefer individual build-system over stock products? How to handle circular dependencies? Why is it a very bad idea to put timestamps into your code? What are the benefits of supporting a hardware platform you’re not even using? And much much more  Selected Links and Resources From This Episode  Open SuSE build system   Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Engineers’ talk: Tools and Building with Robert Schiele – MES013 appeared first on Embedded Success.

<h2>Tools and Building</h2> <p>This episode is about building, maintaining and distributing tools and operating system in large scale projects. With Robert Schiele an expert on all this kind of topics stays with me. He is senior specialist for developing OS-tools, providing toolchains and building operating systems.</p> <p>Robert provides dedicated and verbose insights into the Linux Kernel and the Linux Operating System in particular. He’s one of the guys I know who is eagerly engaged into the OpenSource-community.</p> <p></p> <p>In his current role he maintains development tools and OpenSource components for a global mobile network supplier. His main task is to provide running build-systems, tool-chains, toolsets and root-filesystems.</p> <p>He has seen and resolved a lot of problems when providing tools and operating systems. Especially for large scale systems and multiple hardware platforms in multi-site environments.</p> <p>We’re talking about build-systems, root file systems, native and cross building.<br/> We tackle observable problems with distributed environments.<br/> We discuss about struggles with multiple hardware platforms.<br/> And we give you a close look into the way how well prepared tools-provisioning saves you time and prevents waste.</p> <h2>Essential Know-How Provided In This Episode:</h2> <ul> <li>What are the main challenges when building large scale systems?</li> <li>How can a good building system support you or waste your time dramatically?</li> <li>When to prefer individual build-system over stock products?</li> <li>How to handle circular dependencies?</li> <li>Why is it a very bad idea to put timestamps into your code?</li> <li>What are the benefits of supporting a hardware platform you’re not even using?</li> <li>And much much more</li> </ul> <h2>Selected Links and Resources From This Episode</h2> <ul> <li><a href="https://build.opensuse.org/" rel="nofollow" target="_blank">Open SuSE build system</a></li> </ul> <h2></h2> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes013-tools-and-building-with-robert-schiele/" rel="nofollow" target="_blank">Engineers’ talk: Tools and Building with Robert Schiele – MES013</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Engineers' talk: Tools and Building with Robert Schiele - MES013

Root cause? What’s that? Remember your last sickness. Caught a cold or a flew? Weren’t you only curing the symptoms? Usually nobody cares for the real reasons when getting ill with these small diseases. But there are lots of persons who are able to somehow avoid any disease. What’s the difference? Why were you felt sick? It’s like weeding your garden. Very often only the symptoms are cured, but no real solution can be achieved. The weed gets back soon. Removing the root would do the job, but that costs additional effort, back-pain and time. Within the business context regularly the management requests an immediate, complete, fast and reliable solution of problems. But is that possible without finding the real cause of a problem? Without fixing the real cause of a problem it might pop the same way again as the weed does. That’s the ideas of root cause analysis. Dive deeper into a problem to find the real underlying cause of the problem. The diving should be that deep to find not only a cause, but the process which is failing or is insufficient This episode is about the first and basic technique of finding the real root cause of a problem: the 5-Whys technique  5-Whys to find the root cause The 5-Whys is a technique first time introduced by Toyota within the Toyota Production System (TPS). It is an iterative question-asking technique to explore the cause-and-effect relationship underlying a particular problem. The technique belongs to repeating the question “Why?”. Each question forms the basics of the next question. The “5” in the name derives from an empirical observation on the number of iterations, which is typically required to find the real cause of a problem – the root cause. The idea of 5-Whys is to dig deeper. But it’s even more. It not only stupidly asking Why, Why, Why again and again. It’s a change in the paradigm of evaluating the cause of a problem by not getting stucked with the symptoms. It’s like unveiling an onion. You work from one shell to the other until you come to the nucleus. Benefits of 5-Whys The 5-Whys technique has several benefits:  It helps to identify the real cause of a problem It uses small incremental steps to improve the situation It is one of the simplest tools; it’s easy to complete without any statistical analysis It also determins the relationship between different root causes of a problem  The 5-Whys is most useful for problems involving human factors and interactions, like handling, reactive, planning, or design problem. However complex problems might benefit from a more detailed approach. Hereby the 5-Whys can deliver useful insights. Criticism of 5-Whys The 5-Whys technique has several disadvantages and is under critique for:  its tendency for investigators to stop at symptoms rather than going on to lower-level root causes. its inability to go beyond the investigator’s current knowledge. You will not find causes that you do not already know. its lack of support to help investigators for asking the right “Why” questions. its possibility to provide different results for the same analysis. Results are not repeatable. Different people using 5-Whys come up with different causes for the same problem. its tendency to isolate a single root cause, whereas each question could elicit many differenr root causes. its lack of supporting multiple reasons for a problem. You will have to decide to follow one path only.  How to 5-Whys Nevertheless “5-Whys” is a great tool to start with the root-cause analysis. It is fast, in an elaborated hand very effective and therefore efficient in an outstanding way. To improve your understanding of how to do the 5-Whys I have these 3 steps to follow: Start the 5-Whys Start with a description of the problem by providing answers on these questions:  What has happened? Who was engaged? When does it have happened? Who has detected the problem? What impact does the problem have?  Best thing first is to invite for a meeting to start the 5-Whys questioning Do the 5-Whys First you should define a 5-Whys master or moderator. This should be an elaborated person who is able to work on a meta-level of the outstanding communication. It should not be one of the major stakeholders, if he have the tendency to fell blamed for what has happened.  Start with the first “Why” question Note the answer and validate it by reversing the statement and validating the statement. Example: Q: Why do I have forgotten my keys today morning? A: I have forgotten my keys because I was in a great hurry Reversed: If I would have been not in a hurry today morning I would have not forgotten my keys? Right or False? That’s not a clear conclusion! That’s not the cause of having forgotten the keys. Check for additional causes. Eventually us a parallel path of investigation. Ask “Why again” After some iterations and you got the impression to be done change the question to “Why does our process have failed?”  Especially the last step is the most essential one. This changes your perspective from symptoms and easy causes towards a general view. This is the starting point of real improvement. Knowing the failed process is a cornerstone in becoming really better. Report the results of 5-Whys If you have digged out one or multiple root-causes for your problem, then summarize the results:  Provide the historical data Highlight the priorities of the different problems (perhaps by using a Pareto-chart or similar) Show the results of the 5-Whys Provide first ideas of corrective actions and their verification  Pay attention Please be aware that the 5-Whys are simple in concept but sometimes tricky in reality. The following 3 aspects are essential to keep an eye on:  Many times teams will stop once a reason for a defect has been identified. These conclusions often do not get to the root cause. A disciplined 5-why approach will push teams to think outside the box and reach a root cause where the team can actually make a postive difference in the problem, instead of treating symptoms. Avoid intentional or unintentional bias while answering! Find the right person who can answer the 5Why’s! Use other RCA Tools if you’re getting misleading answers. Do not ask your coworkers again and again for the Why. Do not upset them.  Summary 5-Whys are living from experience and excercise. Don’t be impatient if the result is not that good in the first usage. Using it continuously will give you the expertise to do it quicker and more elegant. Don’t hesitate to improve!  Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Finding root causes with 5-Whys – MES009 appeared first on Embedded Success.

<h2>Root cause? What’s that?</h2> <p>Remember your last sickness. Caught a cold or a flew? Weren’t you only curing the symptoms? Usually nobody cares for the real reasons when getting ill with these small diseases. But there are lots of persons who are able to somehow avoid any disease. What’s the difference? Why were you felt sick?</p> <p>It’s like weeding your garden. Very often only the symptoms are cured, but no real solution can be achieved. The weed gets back soon. Removing the root would do the job,<br/> but that costs additional effort, back-pain and time.</p> <p>Within the business context regularly the management requests an immediate, complete, fast and reliable solution of problems. But is that possible without finding the real cause of a problem? Without fixing the real cause of a problem it might pop the same way again as the weed does.</p> <p>That’s the ideas of <em>root cause analysis</em>. Dive deeper into a problem to find the real underlying cause of the problem. The diving should be that deep to find not only a cause, but the process which is failing or is insufficient</p> <p>This episode is about the first and basic technique of finding the real root cause of a problem: the <em>5-Whys</em> technique</p> <p></p> <h2>5-Whys to find the root cause</h2> <p>The <em>5-Whys</em> is a technique first time introduced by Toyota within the <a href="https://en.wikipedia.org/wiki/Toyota_Production_System" rel="nofollow" target="_blank">Toyota Production System (TPS)</a>. It is an iterative question-asking technique to explore the cause-and-effect relationship underlying a particular problem.</p> <p>The technique belongs to repeating the question “Why?”. Each question forms the basics of the next question. The “5” in the name derives from an empirical observation on the number of iterations, which is typically required to find the real cause of a problem – the <em>root cause</em>.</p> <p>The idea of <em>5-Whys</em> is to dig deeper. But it’s even more. It not only stupidly asking Why, Why, Why again and again. It’s a change in the paradigm of evaluating the cause of a problem by not getting stucked with the symptoms. It’s like unveiling an onion. You work from one shell to the other until you come to the nucleus.</p> <h3>Benefits of <em>5-Whys</em></h3> <p>The <em>5-Whys</em> technique has several benefits:</p> <ul> <li>It helps to identify the real cause of a problem</li> <li>It uses small incremental steps to improve the situation</li> <li>It is one of the simplest tools; it’s easy to complete without any statistical analysis</li> <li>It also determins the relationship between different root causes of a problem</li> </ul> <p>The <em>5-Whys</em> is most useful for problems involving human factors and interactions, like handling, reactive, planning, or design problem. However complex problems might benefit from a more detailed approach. Hereby the <em>5-Whys</em> can deliver useful insights.</p> <h3>Criticism of <em>5-Whys</em></h3> <p>The <em>5-Whys</em> technique has several disadvantages and is under critique for:</p> <ul> <li>its tendency for investigators to stop at symptoms rather than going on to lower-level root causes.</li> <li>its inability to go beyond the investigator’s current knowledge. You will not find causes that you do not already know.</li> <li>its lack of support to help investigators for asking the right “Why” questions.</li> <li>its possibility to provide different results for the same analysis. Results are not repeatable. Different people using <em>5-Whys</em> come up with different causes for the same problem.</li> <li>its tendency to isolate a single root cause, whereas each question could elicit many differenr root causes.</li> <li>its lack of supporting multiple reasons for a problem. You will have to decide to follow one path only.</li> </ul> <h2>How to <em>5-Whys</em></h2> <p>Nevertheless “5-Whys” is a great tool to start with the root-cause analysis. It is fast, in an elaborated hand very effective and therefore efficient in an outstanding way.</p> <p>To improve your understanding of how to do the <em>5-Whys</em> I have these 3 steps to follow:</p> <h3>Start the <em>5-Whys</em></h3> <p>Start with a description of the problem by providing answers on these questions:</p> <ul> <li>What has happened?</li> <li>Who was engaged?</li> <li>When does it have happened?</li> <li>Who has detected the problem?</li> <li>What impact does the problem have?</li> </ul> <p>Best thing first is to invite for a meeting to start the <em>5-Whys</em> questioning</p> <h3>Do the <em>5-Whys</em></h3> <p>First you should define a 5-Whys master or moderator. This should be an elaborated person who is able to work on a meta-level of the outstanding communication. It should not be one of the major stakeholders, if he have the tendency to fell blamed for what has happened.</p> <ol> <li>Start with the first “Why” question</li> <li>Note the answer and validate it by reversing the statement and validating the statement. Example:<br/> Q: Why do I have forgotten my keys today morning?<br/> A: I have forgotten my keys because I was in a great hurry<br/> Reversed:<br/> If I would have been not in a hurry today morning I would have not forgotten my keys? Right or False?<br/> That’s not a clear conclusion! That’s not the cause of having forgotten the keys.</li> <li>Check for additional causes. Eventually us a parallel path of investigation.</li> <li>Ask “Why again”</li> <li>After some iterations and you got the impression to be done change the question to “Why does our process have failed?”</li> </ol> <p>Especially the last step is the most essential one. This changes your perspective from symptoms and easy causes towards a general view. This is the starting point of real improvement. Knowing the failed process is a cornerstone in becoming really better.</p> <h3>Report the results of <em>5-Whys</em></h3> <p>If you have digged out one or multiple root-causes for your problem, then summarize the results:</p> <ul> <li>Provide the historical data</li> <li>Highlight the priorities of the different problems (perhaps by using a Pareto-chart or similar)</li> <li>Show the results of the <em>5-Whys</em></li> <li>Provide first ideas of corrective actions and their verification</li> </ul> <h3>Pay attention</h3> <p>Please be aware that the <em>5-Whys</em> are simple in concept but sometimes tricky in reality. The following 3 aspects are essential to keep an eye on:</p> <ol> <li>Many times teams will stop once a reason for a defect has been identified. These conclusions often do not get to the root cause. A disciplined 5-why approach will push teams to think outside the box and reach a root cause where the team can actually make a postive difference in the problem, instead of treating symptoms.</li> <li>Avoid intentional or unintentional bias while answering! Find the right person who can answer the 5Why’s! Use other RCA Tools if you’re getting misleading answers.</li> <li>Do not ask your coworkers again and again for the Why. Do not upset them.</li> </ol> <h2>Summary</h2> <p><em>5-Whys</em> are living from experience and excercise. Don’t be impatient if the result is not that good in the first usage. Using it continuously will give you the expertise to do it quicker and more elegant. Don’t hesitate to improve!</p> <h2></h2> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes009-finding-root-causes-with-5-whys/" rel="nofollow" target="_blank">Finding root causes with 5-Whys – MES009</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Finding root causes with 5-Whys - MES009

Launching a task-force successfully Before you start running a task-force you will have a short moment or phase of planning and launching it. You should use this time carefully and wisely. Potential flaws during this phase might be a constant burden over the whole run-time of the task-force. I’ll show you the questions and the actions you need to successfully launch your task-force. Why do we need a successful launch phase? The launch or kick-off phase of a task-force is like the take-off of an airplane. Even it takes off the conditions might be not good and the overall journey might have started already under a bad star. Key indicators of a successful launch phase  What has to be done? The objectives! What has to be considered? The constraints! Who and what do we need? The members! the environment! When and where? The schedule!  3 mandatory actions for a successful launch The following three actions shall support you in your intention to launch a task-force successfully.  1st Action: Define You need to define the objectives and the needed resources for the task-force. Use the SMART-criteria to define the goals and targets of your task-force. Pay attention to also clarify the knowledge and actions which are needed for your task-force. Objectives and resources are needed for the next action. 2nd Action: Organize This is the major part of your preparation action for the task-force. There are three different parts you need to have an eye on: Participants should be selected …  by their knowledge of the problem, the system, the technology or the methodology; whether they are affected by the problem or the objectives; whether they are involved into the creation or invention of the problem; whether they are involved into evaluating, finding or testing the situation the problem has been observed; whether they could provide a strong push and/or support to your task-force.  The schedule Your task-force should be schedule on a rule of thumb once per day. Usually you do not need more. However if there are extraordinary circumstances or outcomes, then it might be needed to meet more often. For example testing unveiled totally different results of the situation. Or you have team-members in two time-zones that far apart they do not meet each others during regular working hours. But in general keep in mind: as long as needed, as short as possible. The invitation Over the years I collected some details which should be contained in an informative invitation. Follow my Meeting invitation template to provide a meaningful invitation. Please remember that your task-force members will be more willing and more supportive if they immediately understand the purpose and the situation. 3rd Action: Handle limitations During the launch phase you usually run into two different limitations:  You do not get the persons You do not get the time, environment or the budget  For the first my preferred way of working is to decide. If it is not possible from your perspective to fulfill the work without the person you need, decline the task-force. If you do not get the needed expert, but you see a chance to achieve the goal, then accept. But request to get access to the expert on demand. Or accept a substitute which has direct access to the expert. With both approaches I have made good results. For the second and if it is totally out of mind, decline the task-force also. An unrealistic approach needs to be highlighted in such situations. However if it is realistic, then accept with restrictions. Outline crystal clear what you can achieve with the limitations. To provide such statement reliably you need to have a deep insight view of the problem.   Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post 3 mandatory actions to successfully launch a task-force – MES008 appeared first on Embedded Success.

<h2>Launching a task-force successfully</h2> <p>Before you start running a task-force you will have a short moment or phase of planning and launching it. You should use this time carefully and wisely. Potential flaws during this phase might be a constant burden over the whole run-time of the task-force. I’ll show you the questions and the actions you need to successfully launch your task-force.</p> <h2>Why do we need a successful launch phase?</h2> <p>The launch or kick-off phase of a task-force is like the take-off of an airplane. Even it takes off the conditions might be not good and the overall journey might have started already under a bad star.</p> <h2>Key indicators of a successful launch phase</h2> <ul> <li>What has to be done? The objectives!</li> <li>What has to be considered? The constraints!</li> <li>Who and what do we need? The members! the environment!</li> <li>When and where? The schedule!</li> </ul> <h2>3 mandatory actions for a successful launch</h2> <p>The following three actions shall support you in your intention to launch a task-force successfully.</p> <p></p> <h3>1st Action: Define</h3> <p>You need to define the objectives and the needed resources for the task-force. Use the <a href="" rel="nofollow" target="_blank">SMART-criteria</a> to define the goals and targets of your task-force.<br/> Pay attention to also clarify the knowledge and actions which are needed for your task-force.<br/> Objectives and resources are needed for the next action.</p> <h3>2nd Action: Organize</h3> <p>This is the major part of your preparation action for the task-force. There are three different parts you need to have an eye on:</p> <h4>Participants should be selected …</h4> <ul> <li>by their <strong>knowledge</strong> of the problem, the system, the technology or the methodology;</li> <li>whether they are <strong>affected by the problem or the objectives</strong>;</li> <li>whether they are involved into the <strong>creation or invention of the problem</strong>;</li> <li>whether they are involved into <strong>evaluating, finding or testing</strong> the situation <strong>the problem</strong> has been observed;</li> <li>whether they could <strong>provide a strong push</strong> and/or support to your task-force.</li> </ul> <h4>The schedule</h4> <p>Your task-force should be schedule on a rule of thumb once per day. Usually you do not need more. However if there are extraordinary circumstances or outcomes, then it might be needed to meet more often. For example testing unveiled totally different results of the situation. Or you have team-members in two time-zones that far apart they do not meet each others during regular working hours.<br/> But in general keep in mind: as long as needed, as short as possible.</p> <h4>The invitation</h4> <p>Over the years I collected some details which should be contained in an informative invitation. Follow my <a href="https://embeddedsuccess.com/meeting-invitation-template" rel="nofollow" target="_blank">Meeting invitation template</a> to provide a meaningful invitation. Please remember that your task-force members will be more willing and more supportive if they immediately understand the purpose and the situation.</p> <h3>3rd Action: Handle limitations</h3> <p>During the launch phase you usually run into two different limitations:</p> <ol> <li>You do not get the persons</li> <li>You do not get the time, environment or the budget</li> </ol> <p>For the first my preferred way of working is to decide. If it is not possible from your perspective to fulfill the work without the person you need, decline the task-force. If you do not get the needed expert, but you see a chance to achieve the goal, then accept. But request to get access to the expert on demand. Or accept a substitute which has direct access to the expert. With both approaches I have made good results.</p> <p>For the second and if it is totally out of mind, decline the task-force also. An unrealistic approach needs to be highlighted in such situations. However if it is realistic, then accept with restrictions. Outline crystal clear what you can achieve with the limitations. To provide such statement reliably you need to have a deep insight view of the problem.</p> <h2></h2> <h2></h2> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes008-3-mandatory-actions-to-successfully-launch-a-task-force/" rel="nofollow" target="_blank">3 mandatory actions to successfully launch a task-force – MES008</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

3 mandatory actions to successfully launch a task-force - MES008

Marcus Behrens

Talk with Marcus Behrens about IoT Marcus and me joined the IoT-TechDay in Frankfurt end of June. The IoT-TechDay was a one day conference organized by WindRiver, Intel, SalesForce, SAP, Accenture and Microsoft. The intention of meeting was “Moving from talk to transformation” creating business opportunities around IoT. Marcus is a wholehearted engineer and Product Design Director at SAP in Walldorf, Germany. He’s responsible for evaluating the potential of IoT and finding product ideas and opportunities for SAP. On the other side he was and is an engaged engineer within Embedded Systems. This combination made me curious and we have had a good talk already at the IoT-TechDay and later on by mail. Our opinions about IoT and it’s potential, risks and challenges are not always the same. But that makes this talk even more exciting. Enjoy the episode.  We’re talking about:  Our experiences and impression of the IoT-TechDay What IoT really means for us Chances and opportunities of IoT The technical challenges of IoT Potential security problems and legal restrictions Outlook on IoT  Show Notes  Kevin Ashton’s RFID-article first time describing the term Internet of Things Marcus Behrens’ illuminating by mirror on opposite side of valley project Internet of Things Technology Forum: Moving from Talk to Transformation (Keynote session materials)    Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Engineers’ talk: Internet of Things with Marcus Behrens – MES007 appeared first on Embedded Success.

<h2>Talk with Marcus Behrens about IoT</h2> <p>Marcus and me joined the <a href="http://www.windriver.com/events/iot-tech-day-follow-up/" rel="nofollow" target="_blank">IoT-TechDay</a> in Frankfurt end of June. The IoT-TechDay was a one day conference organized by WindRiver, Intel, SalesForce, SAP, Accenture and Microsoft. The intention of meeting was “Moving from talk to transformation” creating business opportunities around IoT.</p> <p>Marcus is a wholehearted engineer and Product Design Director at SAP in Walldorf, Germany. He’s responsible for evaluating the potential of IoT and finding product ideas and opportunities for SAP. On the other side he was and is an engaged engineer within Embedded Systems. This combination made me curious and we have had a good talk already at the IoT-TechDay and later on by mail. Our opinions about IoT and it’s potential, risks and challenges are not always the same. But that makes this talk even more exciting. Enjoy the episode.</p> <p></p> <h2>We’re talking about:</h2> <ul> <li>Our experiences and impression of the IoT-TechDay</li> <li>What IoT really means for us</li> <li>Chances and opportunities of IoT</li> <li>The technical challenges of IoT</li> <li>Potential security problems and legal restrictions</li> <li>Outlook on IoT</li> </ul> <h2>Show Notes</h2> <ul> <li><a href="http://www.rfidjournal.com/articles/view?4986" rel="nofollow" target="_blank">Kevin Ashton’s RFID-article first time describing the term Internet of Things</a></li> <li><a href="https://www.youtube.com/watch?v=7__0DZfnYW8&amp;index=2&amp;list=FLbkZOdem41-ufN1H6SDy3uA" rel="nofollow" target="_blank">Marcus Behrens’ <em>illuminating by mirror on opposite side of valley</em> project</a></li> <li><a href="http://www.windriver.com/events/iot-tech-day-follow-up/" rel="nofollow" target="_blank">Internet of Things Technology Forum: Moving from Talk to Transformation</a> (Keynote session materials)</li> </ul> <p> </p> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes007-engineers-talk-internet-of-things-with-marcus-behrens/" rel="nofollow" target="_blank">Engineers’ talk: Internet of Things with Marcus Behrens – MES007</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Engineers' talk: Internet of Things with Marcus Behrens - MES007

What is a task-force? The term came into extensive use originally by the United States Navy around the beginning of 1941, as a way to increase operational flexibility. The fleet itself was divided into division and squadrons. A task force can be assembled using ships from different divisions and squadrons, without requiring a formal and permanent fleet reorganization, and can be easily dissolved following completion of the operational task Nowadays task-force is something different, no longer using the military speech:  Small group of 4-12 persons With a specific set of skills Accomplished for a short term task Exits only for specific, time-limited purpose (few day until one year) Members often come from different parts of an organization A task-forces enhances enhances the project’s chance for success   When to use a task-force? Task-forces are regularly established in project management when:  Project confronted with complex or thorny issues Solutions require organizational change Involving different perspectives often greases the organizational wheels Task-forces are especially valuable if their outcome impacts people deeply or emotionally. Or impacts a large part of the organization.  Why do task-forces stumble? Task-forces stumble mainly due to three different reasons:  There is no task-force charter given and agreed Task-force members are not made to do the work Task-forces are too often established and therefore loose their crispiness and dedicated flavor  Task-forces are the strongest kind of team In all the different approaches to do work with teams, the task-forces are the strongest way to proceed. You have great chances for rapid progress, you have best heads in the team, and good chance for successful outcome. However you also have to face the disadvantages that task-forces distract from regular work, consumes a lot of (company) energy, and it’s working across hierarchies might be taken as anarchic way of action Especially as in some organizations task-forces are established too often, their effectiveness gets lost quite soon as they become regular. The task-force charter The previously mentioned task-force charter should contain the following topics and need to be agreed by everybody engaged into the task-force:  Purpose and objectives of the task-force Roles and responsibilities of the task-force Others involved into the task-force (project manages, top management, consultants, etc.) A list of tasks and expected work products Overall task-force timeline Resources which will be made available  How-To successful task-force? My list of 5 tips to make your task-force successful: Tip #1 Stand Out Give you task-force a unique name that it is distinguishable from other ongoing activities. And stick with this name until the end. There’s nothing more worse than renaming the activities without real need. Tip #2 Start small Less is beautiful. Take as less persons as possible into the task-force, however as much as needed. Tip #3 Do operations on a schedule Give clear structure to your task-force members. These guys needs to concentrate on resolving the issues. A good structure gives them a solid harness they can concentrate on the essentials. Tip #4 Create and enforce rules It’s essential that agreed rules are also checked and enforced it they are not followed. Make this point clear in the agreement session. Therefore as less rules as better. Tip #5 Be a cheerful leader Laugh and have fun with the guys without loosing your focus on the goals of the task-force. This kind of relaxing and cheerful talk and appearance might decide whether your task-force sustains or gets lost in all day trouble. Outlook The next episodes within this mini-series about Task-Force‘ing  Launching a task-force Running a task-force Doing the aftermath of a task-force  If you already have your preferred solution how to prevent being trapped in such projects – let me know. I do appreciate all of your contributions. [saf feature=”email” cta=”Let me know your way”] Now I’d love to hear from you:  What’s your experience with projects running into trouble? Do you have a warning sign that I didn’t listed here? Or do you wanna agree or disagree with me about these symptoms?   Thank You For ListeningOut of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post 5 tips that your task-force gets successful – MES006 appeared first on Embedded Success.

<h2>What is a task-force?</h2> <p>The term came into extensive use originally by the United States Navy around the beginning of 1941, as a way to increase operational flexibility. The fleet itself was divided into division and squadrons. A task force can be assembled using ships from different divisions and squadrons, without requiring a formal and permanent fleet reorganization, and can be easily dissolved following completion of the operational task</p> <p>Nowadays task-force is something different, no longer using the military speech:</p> <ul> <li>Small group of 4-12 persons</li> <li>With a specific set of skills</li> <li>Accomplished for a short term task</li> <li>Exits only for specific, time-limited purpose (few day until one year)</li> <li>Members often come from different parts of an organization</li> <li>A task-forces enhances enhances the project’s chance for success</li> </ul> <p></p> <h2>When to use a task-force?</h2> <p>Task-forces are regularly established in project management when:</p> <ul> <li>Project confronted with complex or thorny issues</li> <li>Solutions require organizational change</li> <li>Involving different perspectives often greases the organizational wheels</li> <li>Task-forces are especially valuable if their outcome impacts people deeply or emotionally. Or impacts a large part of the organization.</li> </ul> <h3>Why do task-forces stumble?</h3> <p>Task-forces stumble mainly due to three different reasons:</p> <ol> <li>There is no task-force charter given and agreed</li> <li>Task-force members are not made to do the work</li> <li>Task-forces are too often established and therefore loose their crispiness and dedicated flavor</li> </ol> <h3>Task-forces are the strongest kind of team</h3> <p>In all the different approaches to do work with teams, the task-forces are the strongest way to proceed. You have great chances for rapid progress, you have best heads in the team, and good chance for successful outcome. However you also have to face the disadvantages that task-forces distract from regular work, consumes a lot of (company) energy, and it’s working across hierarchies might be taken as anarchic way of action</p> <p>Especially as in some organizations task-forces are established too often, their effectiveness gets lost quite soon as they become regular.</p> <h3>The task-force charter</h3> <p>The previously mentioned task-force charter should contain the following topics and need to be agreed by everybody engaged into the task-force:</p> <ul> <li>Purpose and objectives of the task-force</li> <li>Roles and responsibilities of the task-force</li> <li>Others involved into the task-force (project manages, top management, consultants, etc.)</li> <li>A list of tasks and expected work products</li> <li>Overall task-force timeline</li> <li>Resources which will be made available</li> </ul> <h2>How-To successful task-force?</h2> <p>My list of 5 tips to make your task-force successful:</p> <h4><strong>Tip #1 Stand Out</strong></h4> <p>Give you task-force a unique name that it is distinguishable from other ongoing activities. And stick with this name until the end. There’s nothing more worse than renaming the activities without real need.</p> <h4><strong>Tip #2 Start small</strong></h4> <p>Less is beautiful. Take as less persons as possible into the task-force, however as much as needed.</p> <h4><strong>Tip #3 Do operations on a schedule</strong></h4> <p>Give clear structure to your task-force members. These guys needs to concentrate on resolving the issues. A good structure gives them a solid harness they can concentrate on the essentials.</p> <h4><strong>Tip #4 Create and enforce rules</strong></h4> <p>It’s essential that agreed rules are also checked and enforced it they are not followed. Make this point clear in the agreement session. Therefore as less rules as better.</p> <h4><strong>Tip #5 Be a cheerful leader</strong></h4> <p>Laugh and have fun with the guys without loosing your focus on the goals of the task-force. This kind of relaxing and cheerful talk and appearance might decide whether your task-force sustains or gets lost in all day trouble.</p> <h2>Outlook</h2> <p>The next episodes within this mini-series about <em>Task-Force</em>‘ing</p> <ol> <li>Launching a task-force</li> <li>Running a task-force</li> <li>Doing the aftermath of a task-force</li> </ol> <p>If you already have your preferred solution how to prevent being trapped in such projects – let me know. I do appreciate all of your contributions.</p> <p>[saf feature=”email” cta=”Let me know your way”]</p> <h2>Now I’d love to hear from you:</h2> <ul> <li>What’s your experience with projects running into trouble?</li> <li>Do you have a warning sign that I didn’t listed here?</li> <li>Or do you wanna agree or disagree with me about these symptoms?</li> </ul> <h2></h2> <h2>Thank You For Listening</h2>Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.<br><br>Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!<br><br>Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes006-5-tips-that-your-task-force-gets-successful/" rel="nofollow" target="_blank">5 tips that your task-force gets successful – MES006</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

5 tips that your task-force gets successful - MES006

Why does a project run into trouble? There are a lot of reasons why a project might run into trouble and most project problems are indicated by specific symptoms. Problems of projects are often caused by changes in leadership, company organization or the company itself. All of them create FUD – Fear, Uncertainty, Doubt. As a result we see inappropriate planning, schedule, staffing, and tons of other issues. The reasons for project trouble might be impacted by you or not. From the outside key signs are very often rather clear. But very often they cannot be detected from the inside. Within daily work-load, unaware of changes in environment or the company, with lots of rookies in place, critical symptoms are not recognized or misinterpreted. There are always warning signs – the flashing yellow light indicating that a red light will follow. This episode is about the key-symptoms I have detected during my career indicating that a project is in trouble. They do not mean that the project will fail, but they indicate that there’s something going wrong definitely. And they highlight that additional attention is needed – either to fix them or to escape them. This episode is about this very first step – the symptoms.  What are the warning signs that your project is in trouble? I followed a variation of the Ishikawa-method to categorize the different symptoms. This gives us the opportunity to see the bigger picture. But it does not mean that the different symptoms could not be summarized under a different category. Process &amp; Definitions  Missing or shaky project direction Detectable by: Micro-management; Contradicting statements and direction advises; No direction at all – Silence Results in: Missing of scope and waste Company statements conflict with project goals Detectable by: Less attention by company leaders; Statements about withdrawal of the project; Denial of continuity in support Results in: Loss of reliability by customer; Drop down of credibility Absence of standards and methodology Detectable by: Different process actions for same situations; Constant introduction, withdrawal and re-introduction of tools, processes and methods Results in: Invention of processes and standards on-the-fly; Disturbance, frustration and intolerance; Decline of effectivity and efficiency  Communication  Bad communication within team Detectable by: Personal issues; Hidden conflicts; Unwillingness to speak with everybody Results in: Bad productivity; Frustration; Waste Ignoring expert’s voices Detected by: Expertness requested but not followed; Over simplification of problems Results in: Wrong way of realization; Wrong destination; Waste of effort due to inability to realize the wishful thinking Client becomes unresponsive Detectable by: Requests for information are not responded; There is no “No news is good news”; Critical decisions are made without client attention Results in: Sailing in foggy conditions; Silent drop by client; Withdrawal behind the scenes  People  The “vision guy” leaves Detectable by: No further technical lead guidance; Lack of response in general design questions Results in: Headless chicken mode; Management mess – who will be the successor; Re-planning/-building/-organizing, “Re-“whatsoever Everybody is the visionary person Detectable by: Everybody is barking a different tree; Changes are requested you have already requested long time ago; Team members fight about specs; Project is accounted by corrected faults, not by completed features Results in: Arbitrariness; Bewilderment; Inactivity No visionary guy at all Detectable by: Nobody cares for the project’s progress; Nobody is in charge; No report; No manager/leader; Project does not really matter – to anyone – besides you. Results in: Arbitrariness of project and result; Stopping of project the moment management gets aware of the situation  Management  Project goals less important than company politics Detected by: Management is fiddling into the project’s leaders/managers work; Micro-Management by company-leaders; Thwarted project goals by conflicting company goals; Zero-fault targets (see also Episode #4); Dislikes by Executives; Boss’s statements like: “I know best what the customer wants” Results in: Project members become puppets; Project goals are ignored or silently withdrawn; Nobody takes any risk; Communication with client will drop down Your project’s success is not defined Detected by: Senior management cannot describe the meaning and intention of your project; Stakeholders have different measurements for success; Client’s perspective not requested; Project targets are taken to a minimum level Results in: Wrong project outcome – customer frustration; Waste of effort for arbitrary goals; Frustration and demotivation  Environment  Too much overtime Detectable by: Constant overtime covering bad planning and bad scheduling; Weekend work becomes the regular working mode Results in: Bad morale; Bad mood; Attrition rate increases; Decline of productivity Shortage in money Detectable by: Travel bans; Mandatory investment is not made; Project schedule stretched; Reorganization of company ongoing Results in: Window-to-market missed; Investment failed; The end of the project  Outlook  How could you prevent to be trapped in such a project? How to overcome such projects? Why do you find yourself in such projects again and again?  I want to follow up these questions in one of the following episodes. Stay tuned. If you already have your preferred solution how to prevent being trapped in such projects – let me know. I do appreciate all of your contributions. [saf feature=”email” cta=”Let me know your way”] Now I’d love to hear from you:  What’s your experience with projects running into trouble? Do you have a warning sign that I didn’t listed here? Or do you wanna agree or disagree with me about these symptoms?  I’d love to hear from you about what’s your detection and experience with project failing symptoms. Please comment here in the show notes and let me know what you think.   Thank You For Listening Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at  feedback@embeddedsuccess.com  The post Have you these symptoms of project problems? – MES005 appeared first on Embedded Success.

<h2>Why does a project run into trouble?</h2> <p>There are a lot of reasons why a project might run into trouble and most project problems are indicated by specific symptoms. Problems of projects are often caused by changes in leadership, company organization or the company itself. All of them create FUD – Fear, Uncertainty, Doubt. As a result we see inappropriate planning, schedule, staffing, and tons of other issues.</p> <p>The reasons for project trouble might be impacted by you or not. From the outside key signs are very often rather clear. But very often they cannot be detected from the inside. Within daily work-load, unaware of changes in environment or the company, with lots of rookies in place, critical symptoms are not recognized or misinterpreted. There are always warning signs – the flashing yellow light indicating that a red light will follow.</p> <p>This episode is about the key-symptoms I have detected during my career indicating that a project is in trouble. They do not mean that the project will fail, but they indicate that there’s something going wrong definitely. And they highlight that additional attention is needed – either to fix them or to escape them. This episode is about this very first step – the symptoms.</p> <p></p> <h2>What are the warning signs that your project is in trouble?</h2> <p>I followed a variation of the <a href="https://en.wikipedia.org/wiki/Ishikawa_diagram" rel="nofollow" target="_blank">Ishikawa-method</a> to categorize the different symptoms. This gives us the opportunity to see the bigger picture. But it does not mean that the different symptoms could not be summarized under a different category.</p> <h3>Process &amp; Definitions</h3> <ul> <li><strong>Missing or shaky project direction</strong><br/> Detectable by: Micro-management; Contradicting statements and direction advises; No direction at all – Silence<br/> Results in: Missing of scope and waste</li> <li><strong>Company statements conflict with project goals</strong><br/> Detectable by: Less attention by company leaders; Statements about withdrawal of the project; Denial of continuity in support<br/> Results in: Loss of reliability by customer; Drop down of credibility</li> <li><strong>Absence of standards and methodology</strong><br/> Detectable by: <strong>D</strong>ifferent process actions for same situations; <strong>C</strong>onstant introduction, withdrawal and re-introduction of tools, processes and methods<br/> Results in: <strong>I</strong>nvention of processes and standards on-the-fly; <strong>D</strong>isturbance, frustration and intolerance; <strong>D</strong>ecline of effectivity and efficiency</li> </ul> <h3>Communication</h3> <ul> <li><strong>Bad communication within team</strong><br/> Detectable by: <strong>P</strong>ersonal issues; <strong>H</strong>idden conflicts; <strong>U</strong>nwillingness to speak with everybody<br/> Results in: <strong>B</strong>ad productivity; <strong>F</strong>rustration; <strong>W</strong>aste</li> <li><strong>Ignoring expert’s voices<br/> </strong>Detected by: <strong>E</strong>xpertness requested but not followed; <strong>O</strong>ver simplification of problems<br/> Results in: <strong>W</strong>rong way of realization; Wrong destination; <strong>W</strong>aste of effort due to inability to realize the wishful thinking</li> <li><strong>Client becomes unresponsive</strong><br/> Detectable by: <strong>R</strong>equests for information are not responded; <strong>T</strong>here is no “No news is good news”; <strong>C</strong>ritical decisions are made without client attention<br/> Results in: <strong>S</strong>ailing in foggy conditions; <strong>S</strong>ilent drop by client; <strong>W</strong>ithdrawal behind the scenes</li> </ul> <h3>People</h3> <ul> <li><strong>The “vision guy” leaves</strong><br/> Detectable by: <strong>N</strong>o further technical lead guidance; <strong>L</strong>ack of response in general design questions<br/> Results in: <strong>H</strong>eadless chicken mode; <strong>M</strong>anagement mess – who will be the successor; <strong>R</strong>e-planning/-building/-organizing, “Re-“whatsoever</li> <li><strong>Everybody is the visionary person</strong><br/> Detectable by: <strong>E</strong>verybody is barking a different tree; <strong>C</strong>hanges are requested you have already requested long time ago; <strong>T</strong>eam members fight about specs; <strong>P</strong>roject is accounted by corrected faults, not by completed features<br/> Results in: <strong>A</strong>rbitrariness; <strong>B</strong>ewilderment; <strong>I</strong>nactivity</li> <li><strong>No visionary guy at all</strong><br/> Detectable by: <strong>N</strong>obody cares for the project’s progress; <strong>N</strong>obody is in charge; <strong>N</strong>o report; <strong>N</strong>o manager/leader; <strong>P</strong>roject does not really matter – to anyone – besides you.<br/> Results in: <strong>A</strong>rbitrariness of project and result; <strong>S</strong>topping of project the moment management gets aware of the situation</li> </ul> <h3>Management</h3> <ul> <li><strong>Project goals less important than company politics</strong><br/> Detected by: <strong>M</strong>anagement is fiddling into the project’s leaders/managers work; <strong>M</strong>icro-Management by company-leaders; <strong>T</strong>hwarted project goals by conflicting company goals; <strong>Z</strong>ero-fault targets (see also <a href="https://embeddedsuccess.com/mes004-throw-away-your-zero-fault-targets" rel="nofollow" target="_blank">Episode #4</a>); <strong>D</strong>islikes by Executives; <strong>B</strong>oss’s statements like: “I know best what the customer wants”<br/> Results in: <strong>P</strong>roject members become puppets; <strong>P</strong>roject goals are ignored or silently withdrawn; <strong>N</strong>obody takes any risk; <strong>C</strong>ommunication with client will drop down</li> <li><strong>Your project’s success is not defined</strong><br/> Detected by: <strong>S</strong>enior management cannot describe the meaning and intention of your project; <strong>S</strong>takeholders have different measurements for success; <strong>C</strong>lient’s perspective not requested; <strong>P</strong>roject targets are taken to a minimum level<br/> Results in: <strong>W</strong>rong project outcome – customer frustration; <strong>W</strong>aste of effort for arbitrary goals; <strong>F</strong>rustration and demotivation</li> </ul> <h3>Environment</h3> <ul> <li><strong>Too much overtime</strong><br/> Detectable by: <strong>C</strong>onstant overtime covering bad planning and bad scheduling; <strong>W</strong>eekend work becomes the regular working mode<br/> Results in: <strong>B</strong>ad morale; <strong>B</strong>ad mood; <strong>A</strong>ttrition rate increases; <strong>D</strong>ecline of productivity</li> <li><strong>Shortage in money</strong><br/> Detectable by: <strong>T</strong>ravel bans; <strong>M</strong>andatory investment is not made; <strong>P</strong>roject schedule stretched; <strong>R</strong>eorganization of company ongoing<br/> Results in: <strong>W</strong>indow-to-market missed; <strong>I</strong>nvestment failed; <strong>T</strong>he end of the project</li> </ul> <h2>Outlook</h2> <ul> <li><strong>How could you prevent to be trapped in such a project?</strong></li> <li><strong>How to overcome such projects?</strong></li> <li><strong>Why do you find yourself in such projects again and again?</strong></li> </ul> <p>I want to follow up these questions in one of the following episodes. Stay tuned.</p> <h4>If you already have your preferred solution how to prevent being trapped in such projects – let me know. I do appreciate all of your contributions.</h4> <p>[saf feature=”email” cta=”Let me know your way”]</p> <h2>Now I’d love to hear from you:</h2> <ul> <li>What’s your experience with projects running into trouble?</li> <li>Do you have a warning sign that I didn’t listed here?</li> <li>Or do you wanna agree or disagree with me about these symptoms?</li> </ul> <p><strong>I’d love to hear from you about what’s your detection and experience with project failing symptoms. Please comment here in the show notes and let me know what you think.</strong></p> <p> </p> <h2>Thank You For Listening</h2> Out of all the podcasts available in the Internet you tuned into mine, and I’m grateful for that. If you enjoyed the episode, please share it by using the social media buttons you see at the bottom of this note.  Also, I would be very happy if you would consider taking the minute it takes to leave an honest review or rating for the podcast on iTunes or Stitcher. They’re extremely helpful when it comes to the ranking of the podcast. For sure I read every single one of them personally!  Or, if you prefer a more direct contact, don't hesitate and drop me a note at <a href="mailto:feedback@embeddedsuccess.com"> feedback@embeddedsuccess.com</a> <p></p> <p>The post <a href="https://embeddedsuccess.com/mes005-have-you-these-symptoms-of-project-problems/" rel="nofollow" target="_blank">Have you these symptoms of project problems? – MES005</a> appeared first on <a href="https://embeddedsuccess.com" rel="nofollow" target="_blank">Embedded Success</a>.</p>

Have you these symptoms of project problems? - MES005

The best podcast episodes on non-current politics. Covering topics such as universal basic income, democracy, poverty & justice and more. For anyone interested in learning more about politics that affect that world, not just now, but in the longer term. Add episodes you're interested into your queue below!

Best Non-Current Politics Podcasts

The best podcast episodes on romantic relationships. Episodes talk about the 5 love languages, intimacy, and the taboo topics of sexual desires and infidelity. This topic is a deep dive into the science and complexities that face us in our relationships with others. Add episodes you're interested into your queue below!