Sven Akerman Jr's guest appearances

Sven Akerman Jr

Ruby Rogues

Devchat.tv Episode Roundup

Carina C Zona

Ben Hammersley

Nell Shamrell

Nell Shamrell-Harrington

Paul Dix

Dylan Andrews

Derek Prior

Ben Orenstein

Chad Fowler

Bob Zeidman

Fabio Perrella

Ilya Grigorik

Milap Neupane

Greg Wilson

Jeff Casimir

OwlTail

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement.  Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward.  Panelists   David Kumura   Charles Max Wood   Guest   Sven Akerman Jr.   Sponsors   Sentry | Use the code “devchat” for $100 credit   RedisGreen   Links   Outlook Insight   Scrum   Agile development   Kubernetes   Picks David Kimura:   NGINX Reverse Proxy   DeWalt Ceramic Rapid Heat Full Size Glue Gun   Charles Max Wood:   Discourse   Sven Akerman Jr.:   Getting off of hardware   Follow Sven on LinkedIn @svenakermanjr or outlookinsight.com 

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement.  Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward.  <h2>Panelists</h2> <ul> <li> David Kumura </li> <li> Charles Max Wood </li> </ul> <h2>Guest</h2> <ul> <li> Sven Akerman Jr. </li> </ul> <h2>Sponsors</h2> <ul> <li> <a href="http://sentry.io/" rel="nofollow" target="_blank">Sentry</a> | Use the code “devchat” for $100 credit </li> <li> <a href="https://redisgreen.net/" rel="nofollow" target="_blank">RedisGreen</a> </li> </ul> <h2>Links</h2> <ul> <li> <a href="http://outlookinsight.com/" rel="nofollow" target="_blank">Outlook Insight</a> </li> <li> <a href="https://www.scrum.org/resources/what-is-scrum" rel="nofollow" target="_blank">Scrum</a> </li> <li> <a href="https://www.agilealliance.org/agile101/" rel="nofollow" target="_blank">Agile development</a> </li> <li> <a href="https://kubernetes.io/" rel="nofollow" target="_blank">Kubernetes</a> </li> </ul> <h2>Picks</h2> David Kimura: <ul> <li> <a href="https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/" rel="nofollow" target="_blank">NGINX Reverse Proxy</a> </li> <li> <a href="https://www.homedepot.com/p/DEWALT-Ceramic-Rapid-Heat-Full-Size-Glue-Gun-DWHTGR50/204293086" rel="nofollow" target="_blank">DeWalt Ceramic Rapid Heat Full Size Glue Gun</a> </li> </ul> Charles Max Wood: <ul> <li> <a href="https://discourse.org/" rel="nofollow" target="_blank">Discourse</a> </li> </ul> Sven Akerman Jr.: <ul> <li> Getting off of hardware </li> <li> Follow Sven on <a href="https://www.linkedin.com/in/svenakermanjr" rel="nofollow" target="_blank">LinkedIn @svenakermanjr</a> or <a href="http://outlookinsight.com/" rel="nofollow" target="_blank">outlookinsight.com</a> </li></ul>

RR 443: Sharing Tips from the Trench with Sven Akerman Jr.

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement. Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward. Panelists David Kumura Charles Max Wood GuestSven Akerman Jr.Sponsors  Sentry | Use the code “devchat” for $100 credit  RedisGreen Links Outlook Insight Scrum Agile development Kubernetes PicksDavid Kimura: NGINX Reverse Proxy DeWalt Ceramic Rapid Heat Full Size Glue Gun Charles Max Wood:DiscourseSven Akerman Jr.: Getting off of hardware  Follow Sven on LinkedIn @svenakermanjr or outlookinsight.com Special Guest: Sven Akerman Jr.

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement. Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward. Panelists<ul> <li>David Kumura</li> <li>Charles Max Wood</li> </ul>Guest<ul><li>Sven Akerman Jr.</li></ul>Sponsors<ul> <li> <a href="http://sentry.io/" rel="nofollow" target="_blank">Sentry</a> | Use the code “devchat” for $100 credit </li> <li><a href="https://redisgreen.net/" rel="nofollow" target="_blank">RedisGreen</a></li> </ul>Links<ul> <li><a href="http://outlookinsight.com/" rel="nofollow" target="_blank">Outlook Insight</a></li> <li><a href="https://www.scrum.org/resources/what-is-scrum" rel="nofollow" target="_blank">Scrum</a></li> <li><a href="https://www.agilealliance.org/agile101/" rel="nofollow" target="_blank">Agile development</a></li> <li><a href="https://kubernetes.io/" rel="nofollow" target="_blank">Kubernetes</a></li> </ul>PicksDavid Kimura:<ul> <li><a href="https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/" rel="nofollow" target="_blank">NGINX Reverse Proxy</a></li> <li><a href="https://www.homedepot.com/p/DEWALT-Ceramic-Rapid-Heat-Full-Size-Glue-Gun-DWHTGR50/204293086" rel="nofollow" target="_blank">DeWalt Ceramic Rapid Heat Full Size Glue Gun</a></li> </ul>Charles Max Wood:<ul><li><a href="https://discourse.org/" rel="nofollow" target="_blank">Discourse</a></li></ul>Sven Akerman Jr.:<ul> <li>Getting off of hardware</li> <li> Follow Sven on <a href="https://www.linkedin.com/in/svenakermanjr" rel="nofollow" target="_blank">LinkedIn @svenakermanjr</a> or <a href="http://outlookinsight.com/" rel="nofollow" target="_blank">outlookinsight.com</a> </li></ul>Special Guest: Sven Akerman Jr.

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement. Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward. Panelists David Kumura Charles Max Wood GuestSven Akerman Jr.Sponsors  Sentry | Use the code “devchat” for $100 credit  RedisGreen Links Outlook Insight Scrum Agile development Kubernetes PicksDavid Kimura: NGINX Reverse Proxy DeWalt Ceramic Rapid Heat Full Size Glue Gun Charles Max Wood:DiscourseSven Akerman Jr.: Getting off of hardware  Follow Sven on LinkedIn @svenakermanjr or outlookinsight.com  Special Guest: Sven Akerman Jr.   Advertising Inquiries: https://redcircle.com/brandsPrivacy &amp; Opt-Out: https://redcircle.com/privacy

Sven Akerman Jr. is the chief architect at Outlook Insight. Today he and the panel are talking about the process behind development, specifically how Sven helped improve the software development process at his previous employer. When he started, they had a formal Scrum/Agile process for the first 5 years, but recognized gaps using key performance indicators like turnaround time. So the company implemented the single piece flow method, which ensures that all developers are focused on one thing from start to finish before moving on. As a company, they have a maximum of 2 products in play at a time, with two in focus. Some of the benefits of single piece flow are that it reduces context switching and increases group knowledge and involvement. Sven talks about how the method was implemented in the company, and admits that it takes a really efficient delivery pipeline to move things this quickly. For those that don’t have much to do with a project, the ‘bored void’ was filled with a list of other important things to work on, finding ways to make their own improvements in an area, and automation. Sven found that the method scales well and works both in an office or remote. One of the biggest drawbacks of this method was the psychological barrier among the workers, as it was hard to get people to change the way things “have always been done”. He notes that conversations in meetings shifted from ‘me’ to ‘us’ since people were more aware of others’ work. This shift occurred naturally with the enforcement of the constraints, though it took a couple of months. Sven talks about more ways he saw things change. Charles and David discuss things about this method that interest them, such as shipping things quicker. They talk about possible difficulties with technical debt, which Sven found actually decreased over time. In order to get started with the single piece flow method, it is important to first understand where you’re at and the size and capabilities of your team before moving forward. Panelists<ul> <li>David Kumura</li> <li>Charles Max Wood</li> </ul>Guest<ul><li>Sven Akerman Jr.</li></ul>Sponsors<ul> <li> <a href="http://sentry.io/" rel="nofollow" target="_blank">Sentry</a> | Use the code “devchat” for $100 credit </li> <li><a href="https://redisgreen.net/" rel="nofollow" target="_blank">RedisGreen</a></li> </ul>Links<ul> <li><a href="http://outlookinsight.com/" rel="nofollow" target="_blank">Outlook Insight</a></li> <li><a href="https://www.scrum.org/resources/what-is-scrum" rel="nofollow" target="_blank">Scrum</a></li> <li><a href="https://www.agilealliance.org/agile101/" rel="nofollow" target="_blank">Agile development</a></li> <li><a href="https://kubernetes.io/" rel="nofollow" target="_blank">Kubernetes</a></li> </ul>PicksDavid Kimura:<ul> <li><a href="https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/" rel="nofollow" target="_blank">NGINX Reverse Proxy</a></li> <li><a href="https://www.homedepot.com/p/DEWALT-Ceramic-Rapid-Heat-Full-Size-Glue-Gun-DWHTGR50/204293086" rel="nofollow" target="_blank">DeWalt Ceramic Rapid Heat Full Size Glue Gun</a></li> </ul>Charles Max Wood:<ul><li><a href="https://discourse.org/" rel="nofollow" target="_blank">Discourse</a></li></ul>Sven Akerman Jr.:<ul> <li>Getting off of hardware</li> <li> Follow Sven on <a href="https://www.linkedin.com/in/svenakermanjr" rel="nofollow" target="_blank">LinkedIn @svenakermanjr</a> or <a href="http://outlookinsight.com/" rel="nofollow" target="_blank">outlookinsight.com</a> </li> </ul>Special Guest: Sven Akerman Jr. Advertising Inquiries: <a href="https://redcircle.com/brands" rel="nofollow" target="_blank">https://redcircle.com/brands</a> Privacy &amp; Opt-Out: <a href="https://redcircle.com/privacy" rel="nofollow" target="_blank">https://redcircle.com/privacy</a>