�ݺ�ߣshows by User: emgsilva

�ݺ�ߣshows by User: emgsilva / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: emgsilva / Fri, 12 Jun 2020 19:19:01 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: emgsilva Stop Smashing Your Keyboard! Zoom Out and Think! /slideshow/stop-smashing-your-keyboard-zoom-out-and-think-235499780/235499780 spacessummit2018-stopsmashingyourkeyboardzoomout-200612191901
(Presentation from Spaces Summit 2018, bol.com) Dirty little secret: most of the time as developers we have no clear picture of what we are doing; how we are doing it; and especially why we are doing it. We work without a clear perspective, ending up spending too much time building things and later re-building/refactoring them... This is all done in the name of "agility and speed", but we paradoxically end up getting the exact opposite result. My answer to this? Create a basic design and understanding before starting a project... Then iterate on it, as you face new design decisions (and gain knowledge and insights). Let me get you into this mindset with some very pragmatic ideas and tools, like: "visualization of problems and solutions", "just enough upfront design", "evolutionary architectures"... but especially why you should stop smashing your keyboard, zoom out, and THINK! Presentation video here: https://youtu.be/FCqn9iHU9xo]]>
(Presentation from Spaces Summit 2018, bol.com) Dirty little secret: most of the time as developers we have no clear picture of what we are doing; how we are doing it; and especially why we are doing it. We work without a clear perspective, ending up spending too much time building things and later re-building/refactoring them... This is all done in the name of "agility and speed", but we paradoxically end up getting the exact opposite result. My answer to this? Create a basic design and understanding before starting a project... Then iterate on it, as you face new design decisions (and gain knowledge and insights). Let me get you into this mindset with some very pragmatic ideas and tools, like: "visualization of problems and solutions", "just enough upfront design", "evolutionary architectures"... but especially why you should stop smashing your keyboard, zoom out, and THINK! Presentation video here: https://youtu.be/FCqn9iHU9xo]]> Fri, 12 Jun 2020 19:19:01 GMT /slideshow/stop-smashing-your-keyboard-zoom-out-and-think-235499780/235499780 emgsilva@slideshare.net(emgsilva) Stop Smashing Your Keyboard! Zoom Out and Think! emgsilva (Presentation from Spaces Summit 2018, bol.com) Dirty little secret: most of the time as developers we have no clear picture of what we are doing; how we are doing it; and especially why we are doing it. We work without a clear perspective, ending up spending too much time building things and later re-building/refactoring them... This is all done in the name of "agility and speed", but we paradoxically end up getting the exact opposite result. My answer to this? Create a basic design and understanding before starting a project... Then iterate on it, as you face new design decisions (and gain knowledge and insights). Let me get you into this mindset with some very pragmatic ideas and tools, like: "visualization of problems and solutions", "just enough upfront design", "evolutionary architectures"... but especially why you should stop smashing your keyboard, zoom out, and THINK! Presentation video here: https://youtu.be/FCqn9iHU9xo <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2018-stopsmashingyourkeyboardzoomout-200612191901-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> (Presentation from Spaces Summit 2018, bol.com) Dirty little secret: most of the time as developers we have no clear picture of what we are doing; how we are doing it; and especially why we are doing it. We work without a clear perspective, ending up spending too much time building things and later re-building/refactoring them... This is all done in the name of "agility and speed", but we paradoxically end up getting the exact opposite result. My answer to this? Create a basic design and understanding before starting a project... Then iterate on it, as you face new design decisions (and gain knowledge and insights). Let me get you into this mindset with some very pragmatic ideas and tools, like: "visualization of problems and solutions", "just enough upfront design", "evolutionary architectures"... but especially why you should stop smashing your keyboard, zoom out, and THINK! Presentation video here: https://youtu.be/FCqn9iHU9xo

Stop Smashing Your Keyboard! Zoom Out and Think! from Eduardo da Silva

]]> 62 0 https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2018-stopsmashingyourkeyboardzoomout-200612191901-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Agile... we are not there yet! Let's get closer with "well rounded product teams" /slideshow/agile-we-are-not-there-yet-lets-get-closer-with-well-rounded-product-teams/235499675 spacessummit2019-wellroundedproductteams-eduardodasilva-200612191542
(Presentation from Spaces Summit 2019, bol.com) Agile enables us to move away from the classical waterfall approaches, allowing more ownership and autonomy for the teams building products. This leads to higher velocity on building our products. However, we are not there yet! We still have (hidden) "small waterfalls"! Products are defined by "business teams" (a.k.a.: "Business") and then implemented by "technical teams" (a.k.a.: "IT"). The result? Under-optimal agility and products flawed by design! This talk is a call for action to stop these small waterfalls. I will focus on two specific points. First, teams must increase their technical leadership and safeguard the technical vision and design of their products. Second, the team working on the product must act as a single unit (not "Business" and "IT", but "Product Team"). Product Team owns the whole vision and design for the product. These are two essential elements to build what I call "well rounded product teams", which is key to achieve the true ambitions of Agile. Presentation video here: https://youtu.be/ZeupQmwvoa0 ]]>
(Presentation from Spaces Summit 2019, bol.com) Agile enables us to move away from the classical waterfall approaches, allowing more ownership and autonomy for the teams building products. This leads to higher velocity on building our products. However, we are not there yet! We still have (hidden) "small waterfalls"! Products are defined by "business teams" (a.k.a.: "Business") and then implemented by "technical teams" (a.k.a.: "IT"). The result? Under-optimal agility and products flawed by design! This talk is a call for action to stop these small waterfalls. I will focus on two specific points. First, teams must increase their technical leadership and safeguard the technical vision and design of their products. Second, the team working on the product must act as a single unit (not "Business" and "IT", but "Product Team"). Product Team owns the whole vision and design for the product. These are two essential elements to build what I call "well rounded product teams", which is key to achieve the true ambitions of Agile. Presentation video here: https://youtu.be/ZeupQmwvoa0 ]]> Fri, 12 Jun 2020 19:15:42 GMT /slideshow/agile-we-are-not-there-yet-lets-get-closer-with-well-rounded-product-teams/235499675 emgsilva@slideshare.net(emgsilva) Agile... we are not there yet! Let's get closer with "well rounded product teams" emgsilva (Presentation from Spaces Summit 2019, bol.com) Agile enables us to move away from the classical waterfall approaches, allowing more ownership and autonomy for the teams building products. This leads to higher velocity on building our products. However, we are not there yet! We still have (hidden) "small waterfalls"! Products are defined by "business teams" (a.k.a.: "Business") and then implemented by "technical teams" (a.k.a.: "IT"). The result? Under-optimal agility and products flawed by design! This talk is a call for action to stop these small waterfalls. I will focus on two specific points. First, teams must increase their technical leadership and safeguard the technical vision and design of their products. Second, the team working on the product must act as a single unit (not "Business" and "IT", but "Product Team"). Product Team owns the whole vision and design for the product. These are two essential elements to build what I call "well rounded product teams", which is key to achieve the true ambitions of Agile. Presentation video here: https://youtu.be/ZeupQmwvoa0 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2019-wellroundedproductteams-eduardodasilva-200612191542-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> (Presentation from Spaces Summit 2019, bol.com) Agile enables us to move away from the classical waterfall approaches, allowing more ownership and autonomy for the teams building products. This leads to higher velocity on building our products. However, we are not there yet! We still have (hidden) "small waterfalls"! Products are defined by "business teams" (a.k.a.: "Business") and then implemented by "technical teams" (a.k.a.: "IT"). The result? Under-optimal agility and products flawed by design! This talk is a call for action to stop these small waterfalls. I will focus on two specific points. First, teams must increase their technical leadership and safeguard the technical vision and design of their products. Second, the team working on the product must act as a single unit (not "Business" and "IT", but "Product Team"). Product Team owns the whole vision and design for the product. These are two essential elements to build what I call "well rounded product teams", which is key to achieve the true ambitions of Agile. Presentation video here: https://youtu.be/ZeupQmwvoa0

Agile... we are not there yet! Let's get closer with "well rounded product teams" from Eduardo da Silva

]]> 35 2 https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2019-wellroundedproductteams-eduardodasilva-200612191542-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Intro to Sociotechnical Architecture: co-designing technical & organizational architecture to maximize impact /slideshow/intro-to-sociotechnical-architecture-codesigning-technical-organizational-architecture-to-maximize-impact/235499266 spacessummit2020-sociotechnicalarchitecture-eduardodasilva-200612190541
(Presentation from Spaces Summit 2020, bol.com) Traditionally software architecture focuses on designing software systems to provide value to customers. In most organizations there is little emphasis on the design of the organizational structure that will implement and own such technical architecture. However, in our very competitive and fast moving world this can be a major drawback. We cannot design software systems at high-velocity without considering the organization that will deliver and own them. Architecture must be a co-design activity, considering organizational and software systems aspects. This is what Sociotechnical Architecture aims at. In this talk I am going to show you what Sociotechnical Architecture is; why it is extremely relevant; and will also inspire you with several examples and patterns. My goal is to make clear that we must always consider these two dimensions to be able to maximize our impact and be able to achieve high-velocity on our product development. Presentation video here: https://youtu.be/ekMPm78KFj0]]>
(Presentation from Spaces Summit 2020, bol.com) Traditionally software architecture focuses on designing software systems to provide value to customers. In most organizations there is little emphasis on the design of the organizational structure that will implement and own such technical architecture. However, in our very competitive and fast moving world this can be a major drawback. We cannot design software systems at high-velocity without considering the organization that will deliver and own them. Architecture must be a co-design activity, considering organizational and software systems aspects. This is what Sociotechnical Architecture aims at. In this talk I am going to show you what Sociotechnical Architecture is; why it is extremely relevant; and will also inspire you with several examples and patterns. My goal is to make clear that we must always consider these two dimensions to be able to maximize our impact and be able to achieve high-velocity on our product development. Presentation video here: https://youtu.be/ekMPm78KFj0]]> Fri, 12 Jun 2020 19:05:41 GMT /slideshow/intro-to-sociotechnical-architecture-codesigning-technical-organizational-architecture-to-maximize-impact/235499266 emgsilva@slideshare.net(emgsilva) Intro to Sociotechnical Architecture: co-designing technical & organizational architecture to maximize impact emgsilva (Presentation from Spaces Summit 2020, bol.com) Traditionally software architecture focuses on designing software systems to provide value to customers. In most organizations there is little emphasis on the design of the organizational structure that will implement and own such technical architecture. However, in our very competitive and fast moving world this can be a major drawback. We cannot design software systems at high-velocity without considering the organization that will deliver and own them. Architecture must be a co-design activity, considering organizational and software systems aspects. This is what Sociotechnical Architecture aims at. In this talk I am going to show you what Sociotechnical Architecture is; why it is extremely relevant; and will also inspire you with several examples and patterns. My goal is to make clear that we must always consider these two dimensions to be able to maximize our impact and be able to achieve high-velocity on our product development. Presentation video here: https://youtu.be/ekMPm78KFj0 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2020-sociotechnicalarchitecture-eduardodasilva-200612190541-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> (Presentation from Spaces Summit 2020, bol.com) Traditionally software architecture focuses on designing software systems to provide value to customers. In most organizations there is little emphasis on the design of the organizational structure that will implement and own such technical architecture. However, in our very competitive and fast moving world this can be a major drawback. We cannot design software systems at high-velocity without considering the organization that will deliver and own them. Architecture must be a co-design activity, considering organizational and software systems aspects. This is what Sociotechnical Architecture aims at. In this talk I am going to show you what Sociotechnical Architecture is; why it is extremely relevant; and will also inspire you with several examples and patterns. My goal is to make clear that we must always consider these two dimensions to be able to maximize our impact and be able to achieve high-velocity on our product development. Presentation video here: https://youtu.be/ekMPm78KFj0

Intro to Sociotechnical Architecture: co-designing technical & organizational architecture to maximize impact from Eduardo da Silva

]]> 188 0 https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2020-sociotechnicalarchitecture-eduardodasilva-200612190541-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-emgsilva-48x48.jpg?cb=1615841639 Technical Leader, (Sociotechnical) Software Architect, Software Engineer, ex-{Academic, Startup Founder/CEO/CTO} & Continuous Learner. esilva.net https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2018-stopsmashingyourkeyboardzoomout-200612191901-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/stop-smashing-your-keyboard-zoom-out-and-think-235499780/235499780 Stop Smashing Your Key... https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2019-wellroundedproductteams-eduardodasilva-200612191542-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/agile-we-are-not-there-yet-lets-get-closer-with-well-rounded-product-teams/235499675 Agile... we are not th... https://cdn.slidesharecdn.com/ss_thumbnails/spacessummit2020-sociotechnicalarchitecture-eduardodasilva-200612190541-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/intro-to-sociotechnical-architecture-codesigning-technical-organizational-architecture-to-maximize-impact/235499266 Intro to Sociotechnica...