際際滷shows by User: AdamBoczek / http://www.slideshare.net/images/logo.gif 際際滷shows by User: AdamBoczek / Wed, 14 Mar 2018 11:00:54 GMT 際際滷Share feed for 際際滷shows by User: AdamBoczek Agile IT Transformation Java Entwicklertag 2018 Keynote https://de.slideshare.net/slideshow/agile-it-transformation-java-entwicklertag-2018-keynote-90633252/90633252 20180219javaentwicklertag2018keynoteagileittransformationv1-180314110055
Begleitfolien zur meiner JE2018-Keynote bei einem Kunden aus der Versicherungsbranche.]]>
Begleitfolien zur meiner JE2018-Keynote bei einem Kunden aus der Versicherungsbranche.]]> Wed, 14 Mar 2018 11:00:54 GMT https://de.slideshare.net/slideshow/agile-it-transformation-java-entwicklertag-2018-keynote-90633252/90633252 AdamBoczek@slideshare.net(AdamBoczek) Agile IT Transformation Java Entwicklertag 2018 Keynote AdamBoczek Begleitfolien zur meiner JE2018-Keynote bei einem Kunden aus der Versicherungsbranche. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/20180219javaentwicklertag2018keynoteagileittransformationv1-180314110055-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Begleitfolien zur meiner JE2018-Keynote bei einem Kunden aus der Versicherungsbranche.
from Adam Boczek
]]> 431 2 https://cdn.slidesharecdn.com/ss_thumbnails/20180219javaentwicklertag2018keynoteagileittransformationv1-180314110055-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 Can We All Be Agile in the Same Way? JAX Conference 2015 | Germany /AdamBoczek/can-wee-all-be-agile-in-the-same-way-jax-conference-2015-accm-v11 adamboczekjax2015accmv1-150424011331-conversion-gate01
Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well.]]>
Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well.]]> Fri, 24 Apr 2015 01:13:31 GMT /AdamBoczek/can-wee-all-be-agile-in-the-same-way-jax-conference-2015-accm-v11 AdamBoczek@slideshare.net(AdamBoczek) Can We All Be Agile in the Same Way? JAX Conference 2015 | Germany AdamBoczek Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekjax2015accmv1-150424011331-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the &quot;Agile Culture Capability Model&quot; (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well.
Can We All Be Agile in the Same Way? JAX Conference 2015 | Germany from Adam Boczek
]]> 1285 1 https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekjax2015accmv1-150424011331-conversion-gate01-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 ACE 2015 Conference Agile Architecture from the Trenches /slideshow/adam-boczek-ace-2015-agile-architecture-from-the-trenches/45923517 adamboczekace2015agilearchitecturev1-150317012841-conversion-gate01
際際滷s from my talk at ACE 2015 in Krakow/Poland about Agile Architecture from the trenches. Abstract: In my latest ten years, working as an IT consultant in the area of enterprise architecture, I got more and more questions about combination of the agile software engineering (not just only development) and the enterprise architecture which comprises business and software architecture. Especially for the big organizations it is a challenging topic due to their internal culture and structure that doesn't really suit to the values and principles of "being agile" as defined by the Agile Manifesto. The main idea of the agile software engineering, besides the responsive, incremental and iterative development process, is to work in a *vertical* and not *horizontal* way. Only *vertical work*, defined e.g. in a form of a user story, can deliver business value as expected by the stakeholders. However this 90 degree turn in the way you work is the biggest problem especially in case of a big organization. It requires involvement of much more departments that work together *in parallel* comparing to the classical *horizontal work* with defined layers and responsibilities. This *vertical work* simply drill down your whole system thus affect many areas, especially architecture, which in this context has also *to be agile*, means that you have to think about agile architecture as a process of building a software system as well as a structure of it. You can find plenty books about architecture. Most of them describe *what* architecture is and *why* you should architect it (yes, it sounds a little bit strange but you actually *architect architecture*). However there are just few books that say *how* to do it. That is exactly what this talk is about. This HOW to architect agile architecture, based on my experience and examples from my current project where I work as a lead architect in one of the biggest insurance companies in Germany.]]>
際際滷s from my talk at ACE 2015 in Krakow/Poland about Agile Architecture from the trenches. Abstract: In my latest ten years, working as an IT consultant in the area of enterprise architecture, I got more and more questions about combination of the agile software engineering (not just only development) and the enterprise architecture which comprises business and software architecture. Especially for the big organizations it is a challenging topic due to their internal culture and structure that doesn't really suit to the values and principles of "being agile" as defined by the Agile Manifesto. The main idea of the agile software engineering, besides the responsive, incremental and iterative development process, is to work in a *vertical* and not *horizontal* way. Only *vertical work*, defined e.g. in a form of a user story, can deliver business value as expected by the stakeholders. However this 90 degree turn in the way you work is the biggest problem especially in case of a big organization. It requires involvement of much more departments that work together *in parallel* comparing to the classical *horizontal work* with defined layers and responsibilities. This *vertical work* simply drill down your whole system thus affect many areas, especially architecture, which in this context has also *to be agile*, means that you have to think about agile architecture as a process of building a software system as well as a structure of it. You can find plenty books about architecture. Most of them describe *what* architecture is and *why* you should architect it (yes, it sounds a little bit strange but you actually *architect architecture*). However there are just few books that say *how* to do it. That is exactly what this talk is about. This HOW to architect agile architecture, based on my experience and examples from my current project where I work as a lead architect in one of the biggest insurance companies in Germany.]]> Tue, 17 Mar 2015 01:28:41 GMT /slideshow/adam-boczek-ace-2015-agile-architecture-from-the-trenches/45923517 AdamBoczek@slideshare.net(AdamBoczek) ACE 2015 Conference Agile Architecture from the Trenches AdamBoczek 際際滷s from my talk at ACE 2015 in Krakow/Poland about Agile Architecture from the trenches. Abstract: In my latest ten years, working as an IT consultant in the area of enterprise architecture, I got more and more questions about combination of the agile software engineering (not just only development) and the enterprise architecture which comprises business and software architecture. Especially for the big organizations it is a challenging topic due to their internal culture and structure that doesn't really suit to the values and principles of "being agile" as defined by the Agile Manifesto. The main idea of the agile software engineering, besides the responsive, incremental and iterative development process, is to work in a *vertical* and not *horizontal* way. Only *vertical work*, defined e.g. in a form of a user story, can deliver business value as expected by the stakeholders. However this 90 degree turn in the way you work is the biggest problem especially in case of a big organization. It requires involvement of much more departments that work together *in parallel* comparing to the classical *horizontal work* with defined layers and responsibilities. This *vertical work* simply drill down your whole system thus affect many areas, especially architecture, which in this context has also *to be agile*, means that you have to think about agile architecture as a process of building a software system as well as a structure of it. You can find plenty books about architecture. Most of them describe *what* architecture is and *why* you should architect it (yes, it sounds a little bit strange but you actually *architect architecture*). However there are just few books that say *how* to do it. That is exactly what this talk is about. This HOW to architect agile architecture, based on my experience and examples from my current project where I work as a lead architect in one of the biggest insurance companies in Germany. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekace2015agilearchitecturev1-150317012841-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 際際滷s from my talk at ACE 2015 in Krakow/Poland about Agile Architecture from the trenches. Abstract: In my latest ten years, working as an IT consultant in the area of enterprise architecture, I got more and more questions about combination of the agile software engineering (not just only development) and the enterprise architecture which comprises business and software architecture. Especially for the big organizations it is a challenging topic due to their internal culture and structure that doesn&#39;t really suit to the values and principles of &quot;being agile&quot; as defined by the Agile Manifesto. The main idea of the agile software engineering, besides the responsive, incremental and iterative development process, is to work in a *vertical* and not *horizontal* way. Only *vertical work*, defined e.g. in a form of a user story, can deliver business value as expected by the stakeholders. However this 90 degree turn in the way you work is the biggest problem especially in case of a big organization. It requires involvement of much more departments that work together *in parallel* comparing to the classical *horizontal work* with defined layers and responsibilities. This *vertical work* simply drill down your whole system thus affect many areas, especially architecture, which in this context has also *to be agile*, means that you have to think about agile architecture as a process of building a software system as well as a structure of it. You can find plenty books about architecture. Most of them describe *what* architecture is and *why* you should architect it (yes, it sounds a little bit strange but you actually *architect architecture*). However there are just few books that say *how* to do it. That is exactly what this talk is about. This HOW to architect agile architecture, based on my experience and examples from my current project where I work as a lead architect in one of the biggest insurance companies in Germany.
ACE 2015 Conference Agile Architecture from the Trenches from Adam Boczek
]]> 1666 1 https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekace2015agilearchitecturev1-150317012841-conversion-gate01-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 Culture Capability Model鐃 or Can We All Be Agile in the Same Way? /slideshow/agile-culture-capability-model-can-we-all-be-agile-in-the-same-way/40136576 adamboczekcodingserbia2014accm-141011011423-conversion-gate02
際際滷s from my talk at Coding Serbia 2014 conference. Abstract: Agile Culture Capability Model can we all be agile in the same way? Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well. Bio: Adam is a Management Consultant at codecentric AG in Germany with more than fifteen years experience helping teams meet challenging project goals. His focus lies on Enterprise Architecture, Agile Software Engineering, and Agile Project Management. During his career, he was involved in various IT projects in Europe and Asia, thus he was able to collect working experience in managing and leading nearshore and offshore IT projects and teams.]]>
際際滷s from my talk at Coding Serbia 2014 conference. Abstract: Agile Culture Capability Model can we all be agile in the same way? Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well. Bio: Adam is a Management Consultant at codecentric AG in Germany with more than fifteen years experience helping teams meet challenging project goals. His focus lies on Enterprise Architecture, Agile Software Engineering, and Agile Project Management. During his career, he was involved in various IT projects in Europe and Asia, thus he was able to collect working experience in managing and leading nearshore and offshore IT projects and teams.]]> Sat, 11 Oct 2014 01:14:23 GMT /slideshow/agile-culture-capability-model-can-we-all-be-agile-in-the-same-way/40136576 AdamBoczek@slideshare.net(AdamBoczek) Agile Culture Capability Model鐃 or Can We All Be Agile in the Same Way? AdamBoczek 際際滷s from my talk at Coding Serbia 2014 conference. Abstract: Agile Culture Capability Model can we all be agile in the same way? Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the "Agile Culture Capability Model" (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well. Bio: Adam is a Management Consultant at codecentric AG in Germany with more than fifteen years experience helping teams meet challenging project goals. His focus lies on Enterprise Architecture, Agile Software Engineering, and Agile Project Management. During his career, he was involved in various IT projects in Europe and Asia, thus he was able to collect working experience in managing and leading nearshore and offshore IT projects and teams. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekcodingserbia2014accm-141011011423-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 際際滷s from my talk at Coding Serbia 2014 conference. Abstract: Agile Culture Capability Model can we all be agile in the same way? Offshore, nearshore, outsourcing? No, I dont want that, not once again many IT managers would say and not without a reason. Plenty of enterprises have already run classical, waterfall projects with the mix of onsite and nearshore or offshore teams. Unfortunately most of them have ended without success. Quite fast a question may arise whether the used methodology was an appropriate one. The hype of the agile project management has created a naive hope that finally the nearshore and offshore projects can be executed successfully. Agile is the cure!. Unfortunately, this naive believe proved to be wrong, and quite often the achieved results of these projects were similarly bad or even worse comparing them to the classical approach. An agile project, when run onsite, delivers much better results than a similar waterfall project. However we have observed many problems with the effectiveness and efficiency of agile projects if they were run in the combination with nearshore or offshore teams. These problems were clearly associated with the cultural differences between the teams. Interestingly, this negative influence of the cultural differences was definite stronger on agile projects comparing to the waterfall projects Do other cultural standards than our western ones hamper the acceptance of the agile values and principles? Is the agility something basically western? Can we measure an agile capability of a team or individual? This session focuses on the &quot;Agile Culture Capability Model&quot; (ACCM) that allows delivering answers to these questions. The ACCM model is based on the proven literature about cultural standards and the personal experience collected by the author during his professional career as an IT-Consultant. The author of this talk is Pole who lives and works for many years in Germany together with his Brazilian wife. He has led successfully many agile projects in Germany with the nearshore (Poland, Romania) and offshore (Japan, China, India) teams. He hopes that he ACCM can help you to be successful as well. Bio: Adam is a Management Consultant at codecentric AG in Germany with more than fifteen years experience helping teams meet challenging project goals. His focus lies on Enterprise Architecture, Agile Software Engineering, and Agile Project Management. During his career, he was involved in various IT projects in Europe and Asia, thus he was able to collect working experience in managing and leading nearshore and offshore IT projects and teams.
Agile Culture Capability Model or Can We All Be Agile in the Same Way? from Adam Boczek
]]> 1935 2 https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekcodingserbia2014accm-141011011423-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 JavaScript & Enterprise BED-Con 2014 Berlin German /AdamBoczek/javascript-enterprise-bedcon-2014-berlin-german bed-conjavascriptfrenterprise2014v1-140404060856-phpapp02
]]>
]]> Fri, 04 Apr 2014 06:08:56 GMT /AdamBoczek/javascript-enterprise-bedcon-2014-berlin-german AdamBoczek@slideshare.net(AdamBoczek) JavaScript & Enterprise BED-Con 2014 Berlin German AdamBoczek <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/bed-conjavascriptfrenterprise2014v1-140404060856-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
JavaScript & Enterprise BED-Con 2014 Berlin German from Adam Boczek
]]> 2172 2 https://cdn.slidesharecdn.com/ss_thumbnails/bed-conjavascriptfrenterprise2014v1-140404060856-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Agile Organization Why & How? /slideshow/agile-organization-2014-my-way-to-think-about-it-v10/30899988 agileorganization2014mywaytothinkaboutitv1-140206084700-phpapp02
Agile Organization 2014 My Way to Think About It]]>
Agile Organization 2014 My Way to Think About It]]> Thu, 06 Feb 2014 08:47:00 GMT /slideshow/agile-organization-2014-my-way-to-think-about-it-v10/30899988 AdamBoczek@slideshare.net(AdamBoczek) Agile Organization Why & How? AdamBoczek Agile Organization 2014 My Way to Think About It <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agileorganization2014mywaytothinkaboutitv1-140206084700-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Agile Organization 2014 My Way to Think About It
Agile Organization Why & How? from Adam Boczek
]]> 911 2 https://cdn.slidesharecdn.com/ss_thumbnails/agileorganization2014mywaytothinkaboutitv1-140206084700-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Agile Architecture v2.0 BITKOM Software Summit 2013 /slideshow/bitkom-software-summit-2013-agile-architecture-v13/26493925 bitkomsoftwaresummit2013agilearchitecturev1-130924071121-phpapp01
This presentation is a second version of my talk about Agile Architecture. Comparing to the first version (also available at slideshare) it contains significant more information about elements that comprise Agile Architecture, focusing on its structure and behavior. We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view. In Unternehmen wird von der IT immer mehr gefordert, einen Wertbeitrag zu leisten. Dahinter steckt der verst辰ndliche Wunsch, flexibler, schneller und messbarer zum gesch辰ftlichen Erfolg beizutragen. Wie gut sind wir, Architekten und Entwickler, ger端stet, diesem Wunsch Folge zu tragen? Wie gut k旦nnen unsere Systeme diese neuen, sehr oft revolution辰ren oder sogar disruptiven Anforderungen unterst端tzen? Unsere Entwicklungsprozesse sind bereits agil. Unsere Entwicklerwerkzeuge sind anspruchsvoll, qualitativ hochwertig und ausgereift. Wie ist aber unsere IT-Architektur? Spiegelt diese die Gesch辰ftsarchitektur eines Unternehmens tats辰chlich wieder oder sind die beiden Welten komplett voneinander getrennt? Wie kann eine gesch辰ftskonforme IT-Architektur entwickelt werden? Wie kann eine bestehende IT-Architektur ggf. angepasst werden? K旦nnen wir 端ber eine flexible oder sogar eine Agile Architektur reden? Und wenn ja, in welchem Kontext? Ist eine agile Architektur nur ein agiler Design-Prozess? Kann eine existierende Architektur refactored werden? Kann die Agilit辰t in ein System eingebaut werden? Kann sich ein System auf architektonischer Ebene agil verhalten? In diesem Talk m旦chten wir 端ber die o.g. Fragestellungen diskutieren. Basierend auf den von dem Vortragenden in den letzten Monaten durchgef端hrten Projekten werden m旦gliche Konzepte, Strategien und L旦sungen f端r eine Agile Architektur Transition in einem Unternehmen dargestellt.]]>
This presentation is a second version of my talk about Agile Architecture. Comparing to the first version (also available at slideshare) it contains significant more information about elements that comprise Agile Architecture, focusing on its structure and behavior. We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view. In Unternehmen wird von der IT immer mehr gefordert, einen Wertbeitrag zu leisten. Dahinter steckt der verst辰ndliche Wunsch, flexibler, schneller und messbarer zum gesch辰ftlichen Erfolg beizutragen. Wie gut sind wir, Architekten und Entwickler, ger端stet, diesem Wunsch Folge zu tragen? Wie gut k旦nnen unsere Systeme diese neuen, sehr oft revolution辰ren oder sogar disruptiven Anforderungen unterst端tzen? Unsere Entwicklungsprozesse sind bereits agil. Unsere Entwicklerwerkzeuge sind anspruchsvoll, qualitativ hochwertig und ausgereift. Wie ist aber unsere IT-Architektur? Spiegelt diese die Gesch辰ftsarchitektur eines Unternehmens tats辰chlich wieder oder sind die beiden Welten komplett voneinander getrennt? Wie kann eine gesch辰ftskonforme IT-Architektur entwickelt werden? Wie kann eine bestehende IT-Architektur ggf. angepasst werden? K旦nnen wir 端ber eine flexible oder sogar eine Agile Architektur reden? Und wenn ja, in welchem Kontext? Ist eine agile Architektur nur ein agiler Design-Prozess? Kann eine existierende Architektur refactored werden? Kann die Agilit辰t in ein System eingebaut werden? Kann sich ein System auf architektonischer Ebene agil verhalten? In diesem Talk m旦chten wir 端ber die o.g. Fragestellungen diskutieren. Basierend auf den von dem Vortragenden in den letzten Monaten durchgef端hrten Projekten werden m旦gliche Konzepte, Strategien und L旦sungen f端r eine Agile Architektur Transition in einem Unternehmen dargestellt.]]> Tue, 24 Sep 2013 07:11:21 GMT /slideshow/bitkom-software-summit-2013-agile-architecture-v13/26493925 AdamBoczek@slideshare.net(AdamBoczek) Agile Architecture v2.0 BITKOM Software Summit 2013 AdamBoczek This presentation is a second version of my talk about Agile Architecture. Comparing to the first version (also available at slideshare) it contains significant more information about elements that comprise Agile Architecture, focusing on its structure and behavior. We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view. In Unternehmen wird von der IT immer mehr gefordert, einen Wertbeitrag zu leisten. Dahinter steckt der verst辰ndliche Wunsch, flexibler, schneller und messbarer zum gesch辰ftlichen Erfolg beizutragen. Wie gut sind wir, Architekten und Entwickler, ger端stet, diesem Wunsch Folge zu tragen? Wie gut k旦nnen unsere Systeme diese neuen, sehr oft revolution辰ren oder sogar disruptiven Anforderungen unterst端tzen? Unsere Entwicklungsprozesse sind bereits agil. Unsere Entwicklerwerkzeuge sind anspruchsvoll, qualitativ hochwertig und ausgereift. Wie ist aber unsere IT-Architektur? Spiegelt diese die Gesch辰ftsarchitektur eines Unternehmens tats辰chlich wieder oder sind die beiden Welten komplett voneinander getrennt? Wie kann eine gesch辰ftskonforme IT-Architektur entwickelt werden? Wie kann eine bestehende IT-Architektur ggf. angepasst werden? K旦nnen wir 端ber eine flexible oder sogar eine Agile Architektur reden? Und wenn ja, in welchem Kontext? Ist eine agile Architektur nur ein agiler Design-Prozess? Kann eine existierende Architektur refactored werden? Kann die Agilit辰t in ein System eingebaut werden? Kann sich ein System auf architektonischer Ebene agil verhalten? In diesem Talk m旦chten wir 端ber die o.g. Fragestellungen diskutieren. Basierend auf den von dem Vortragenden in den letzten Monaten durchgef端hrten Projekten werden m旦gliche Konzepte, Strategien und L旦sungen f端r eine Agile Architektur Transition in einem Unternehmen dargestellt. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/bitkomsoftwaresummit2013agilearchitecturev1-130924071121-phpapp01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This presentation is a second version of my talk about Agile Architecture. Comparing to the first version (also available at slideshare) it contains significant more information about elements that comprise Agile Architecture, focusing on its structure and behavior. We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view. In Unternehmen wird von der IT immer mehr gefordert, einen Wertbeitrag zu leisten. Dahinter steckt der verst辰ndliche Wunsch, flexibler, schneller und messbarer zum gesch辰ftlichen Erfolg beizutragen. Wie gut sind wir, Architekten und Entwickler, ger端stet, diesem Wunsch Folge zu tragen? Wie gut k旦nnen unsere Systeme diese neuen, sehr oft revolution辰ren oder sogar disruptiven Anforderungen unterst端tzen? Unsere Entwicklungsprozesse sind bereits agil. Unsere Entwicklerwerkzeuge sind anspruchsvoll, qualitativ hochwertig und ausgereift. Wie ist aber unsere IT-Architektur? Spiegelt diese die Gesch辰ftsarchitektur eines Unternehmens tats辰chlich wieder oder sind die beiden Welten komplett voneinander getrennt? Wie kann eine gesch辰ftskonforme IT-Architektur entwickelt werden? Wie kann eine bestehende IT-Architektur ggf. angepasst werden? K旦nnen wir 端ber eine flexible oder sogar eine Agile Architektur reden? Und wenn ja, in welchem Kontext? Ist eine agile Architektur nur ein agiler Design-Prozess? Kann eine existierende Architektur refactored werden? Kann die Agilit辰t in ein System eingebaut werden? Kann sich ein System auf architektonischer Ebene agil verhalten? In diesem Talk m旦chten wir 端ber die o.g. Fragestellungen diskutieren. Basierend auf den von dem Vortragenden in den letzten Monaten durchgef端hrten Projekten werden m旦gliche Konzepte, Strategien und L旦sungen f端r eine Agile Architektur Transition in einem Unternehmen dargestellt.
Agile Architecture v2.0 BITKOM Software Summit 2013 from Adam Boczek
]]> 2217 10 https://cdn.slidesharecdn.com/ss_thumbnails/bitkomsoftwaresummit2013agilearchitecturev1-130924071121-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 安艶庄 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Agile Architecture Agile Dev Practices 2013 Keynote /slideshow/agile-dev-practices-2013-agile-architecture-16995112/16995112 agiledevpractices2013agilearchitecturev1-1-130307003638-phpapp02
Keynote: Agile Dev Practices 2013 Adam Boczek, codecentric Agile Architecture Yet Another Oxymoron? We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view.]]>
Keynote: Agile Dev Practices 2013 Adam Boczek, codecentric Agile Architecture Yet Another Oxymoron? We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view.]]> Thu, 07 Mar 2013 00:36:38 GMT /slideshow/agile-dev-practices-2013-agile-architecture-16995112/16995112 AdamBoczek@slideshare.net(AdamBoczek) Agile Architecture Agile Dev Practices 2013 Keynote AdamBoczek Keynote: Agile Dev Practices 2013 Adam Boczek, codecentric Agile Architecture Yet Another Oxymoron? We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiledevpractices2013agilearchitecturev1-1-130307003638-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Keynote: Agile Dev Practices 2013 Adam Boczek, codecentric Agile Architecture Yet Another Oxymoron? We at codecentric, as a technically focused agile organization, get in our projects quite often confronted with the assessment of a customers software architecture, or more precisely with the assessment of the existing solution architecture. In many cases it is ok for us to stay in this technical scope and not to touch other, much wider architectural concepts like e.g. enterprise architecture. However, due to the fact, that more and more organizations want to transform to a more agile organization, the alignment between IT and Business, and thus between IT-architecture and Business-architecture becomes much more relevant for us in our projects than in the past and causes many questions to arise. Can we talk in this context about agile architecture? And if so, is it a model of a system or maybe just a process of creating it? Or maybe both? How long can I delay my architectural decisions? Can I refactor my agile architecture? And so on In this talk I wont give you perfect answers to all these questions, however Im pretty sure I will open your eyes and let you create your own point of view.
Agile Architecture Agile Dev Practices 2013 Keynote from Adam Boczek
]]> 2162 3 https://cdn.slidesharecdn.com/ss_thumbnails/agiledevpractices2013agilearchitecturev1-1-130307003638-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Schwar http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Basta 2012 Mainz Process Intelligence mit Windows Workflow Foundation /slideshow/basta-2012-process-intelligence-with-wf-v13-adam-boczek/15970235 basta2012processintelligencewithwfv1-3adamboczek-130113012103-phpapp02
Process Intelligence erm旦glicht einen Zusammenschluss von Unternehmens- und Prozesskontrolle auf taktischer und operativer Ebene. Sollten Kennzahlen (wie z.B. Durchlaufzeit) von erwarteten Werten abweichen, k旦nnen Ursachen hierf端r in den Gesch辰ftsprozessen analysiert werden. Korrigierende Manahmen k旦nnen in Echtzeit ergriffen werden, bevor das laufende Gesch辰ft beeintr辰chtigt wird.]]>
Process Intelligence erm旦glicht einen Zusammenschluss von Unternehmens- und Prozesskontrolle auf taktischer und operativer Ebene. Sollten Kennzahlen (wie z.B. Durchlaufzeit) von erwarteten Werten abweichen, k旦nnen Ursachen hierf端r in den Gesch辰ftsprozessen analysiert werden. Korrigierende Manahmen k旦nnen in Echtzeit ergriffen werden, bevor das laufende Gesch辰ft beeintr辰chtigt wird.]]> Sun, 13 Jan 2013 01:21:03 GMT /slideshow/basta-2012-process-intelligence-with-wf-v13-adam-boczek/15970235 AdamBoczek@slideshare.net(AdamBoczek) Basta 2012 Mainz Process Intelligence mit Windows Workflow Foundation AdamBoczek Process Intelligence erm旦glicht einen Zusammenschluss von Unternehmens- und Prozesskontrolle auf taktischer und operativer Ebene. Sollten Kennzahlen (wie z.B. Durchlaufzeit) von erwarteten Werten abweichen, k旦nnen Ursachen hierf端r in den Gesch辰ftsprozessen analysiert werden. Korrigierende Manahmen k旦nnen in Echtzeit ergriffen werden, bevor das laufende Gesch辰ft beeintr辰chtigt wird. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/basta2012processintelligencewithwfv1-3adamboczek-130113012103-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Process Intelligence erm旦glicht einen Zusammenschluss von Unternehmens- und Prozesskontrolle auf taktischer und operativer Ebene. Sollten Kennzahlen (wie z.B. Durchlaufzeit) von erwarteten Werten abweichen, k旦nnen Ursachen hierf端r in den Gesch辰ftsprozessen analysiert werden. Korrigierende Manahmen k旦nnen in Echtzeit ergriffen werden, bevor das laufende Gesch辰ft beeintr辰chtigt wird.
Basta 2012 Mainz Process Intelligence mit Windows Workflow Foundation from Adam Boczek
]]> 532 2 https://cdn.slidesharecdn.com/ss_thumbnails/basta2012processintelligencewithwfv1-3adamboczek-130113012103-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 安艶庄 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Manage Agile 2012 Berlin Agile Culture Capability Model /AdamBoczek/121018-manage-agile-2012-accm-v12 121018manageagile2012accmv1-2-130113011704-phpapp02
Agile Culture Capability Model - Impedance Mismatch und Einfluss von Kulturstandards in agilen Projekten mit On-/Near- und Offshore Teams Off-shore, Near-shore, Outsourcing? Nein, das will ich nicht, sagen viele, nicht schon wieder. Und nicht ohne Grund. Viele Organisationen haben bereits klassische (z.B. mit komponentenbasierten Teams und Wasserfall) Near-/Offshore Projekte gemacht, leider sehr oft ohne Erfolg. Bei diesen projekten h辰ttte man sagen k旦nnen, dass die management methodik falsch war. Einfach. Agilit辰t gab uns neune Hoffnung, die Nearshore-/Offshore Projekte richtig machen und erfolgreich abschlieen zu k旦nnen. Agile, das ist die Heilung. Leider 辰hlich wie bei den klassischen Methoden, viele von diesen Agilen Near-/Offshore Projekten waren sogar weniger erfolgreich als wenn man diese mit den klasisichen methoden durchgef端hrt h辰tte. Wenn das Problem nicht in den Methoden lag, dann wo? Vielleicht waren es doch die Kulturstandards die die Akzeptanz von der agilen Werten und Prinzipien erschweren oder sogar unm旦glich machen? Vielleicht ist die Agilit辰t etwas Westliches? Kann man behaupt agile F辰higkeiten messen? In diesem Talk wird der Autor das Thema Einflu von den kulturelen Standards auf genauer angehen. Im Zentrum das Talks steht ACCM im Fokus. Das Model basiert auf zwei Matrizen: die erste beschreibt die korrelation zwischen den kulturelenstandards (wie z.B. eine starke hierarchische struktur) und den agilen und im jedem Projekt erforderlichen soft-skills (wie self-organisation aka decision making and commitments). Ein weigthsystem gibt die Information wie stark ist die Auswirkung der Kunlturenstandards auf diese soft-skills ]]>
Agile Culture Capability Model - Impedance Mismatch und Einfluss von Kulturstandards in agilen Projekten mit On-/Near- und Offshore Teams Off-shore, Near-shore, Outsourcing? Nein, das will ich nicht, sagen viele, nicht schon wieder. Und nicht ohne Grund. Viele Organisationen haben bereits klassische (z.B. mit komponentenbasierten Teams und Wasserfall) Near-/Offshore Projekte gemacht, leider sehr oft ohne Erfolg. Bei diesen projekten h辰ttte man sagen k旦nnen, dass die management methodik falsch war. Einfach. Agilit辰t gab uns neune Hoffnung, die Nearshore-/Offshore Projekte richtig machen und erfolgreich abschlieen zu k旦nnen. Agile, das ist die Heilung. Leider 辰hlich wie bei den klassischen Methoden, viele von diesen Agilen Near-/Offshore Projekten waren sogar weniger erfolgreich als wenn man diese mit den klasisichen methoden durchgef端hrt h辰tte. Wenn das Problem nicht in den Methoden lag, dann wo? Vielleicht waren es doch die Kulturstandards die die Akzeptanz von der agilen Werten und Prinzipien erschweren oder sogar unm旦glich machen? Vielleicht ist die Agilit辰t etwas Westliches? Kann man behaupt agile F辰higkeiten messen? In diesem Talk wird der Autor das Thema Einflu von den kulturelen Standards auf genauer angehen. Im Zentrum das Talks steht ACCM im Fokus. Das Model basiert auf zwei Matrizen: die erste beschreibt die korrelation zwischen den kulturelenstandards (wie z.B. eine starke hierarchische struktur) und den agilen und im jedem Projekt erforderlichen soft-skills (wie self-organisation aka decision making and commitments). Ein weigthsystem gibt die Information wie stark ist die Auswirkung der Kunlturenstandards auf diese soft-skills ]]> Sun, 13 Jan 2013 01:17:04 GMT /AdamBoczek/121018-manage-agile-2012-accm-v12 AdamBoczek@slideshare.net(AdamBoczek) Manage Agile 2012 Berlin Agile Culture Capability Model AdamBoczek Agile Culture Capability Model - Impedance Mismatch und Einfluss von Kulturstandards in agilen Projekten mit On-/Near- und Offshore Teams Off-shore, Near-shore, Outsourcing? Nein, das will ich nicht, sagen viele, nicht schon wieder. Und nicht ohne Grund. Viele Organisationen haben bereits klassische (z.B. mit komponentenbasierten Teams und Wasserfall) Near-/Offshore Projekte gemacht, leider sehr oft ohne Erfolg. Bei diesen projekten h辰ttte man sagen k旦nnen, dass die management methodik falsch war. Einfach. Agilit辰t gab uns neune Hoffnung, die Nearshore-/Offshore Projekte richtig machen und erfolgreich abschlieen zu k旦nnen. Agile, das ist die Heilung. Leider 辰hlich wie bei den klassischen Methoden, viele von diesen Agilen Near-/Offshore Projekten waren sogar weniger erfolgreich als wenn man diese mit den klasisichen methoden durchgef端hrt h辰tte. Wenn das Problem nicht in den Methoden lag, dann wo? Vielleicht waren es doch die Kulturstandards die die Akzeptanz von der agilen Werten und Prinzipien erschweren oder sogar unm旦glich machen? Vielleicht ist die Agilit辰t etwas Westliches? Kann man behaupt agile F辰higkeiten messen? In diesem Talk wird der Autor das Thema Einflu von den kulturelen Standards auf genauer angehen. Im Zentrum das Talks steht ACCM im Fokus. Das Model basiert auf zwei Matrizen: die erste beschreibt die korrelation zwischen den kulturelenstandards (wie z.B. eine starke hierarchische struktur) und den agilen und im jedem Projekt erforderlichen soft-skills (wie self-organisation aka decision making and commitments). Ein weigthsystem gibt die Information wie stark ist die Auswirkung der Kunlturenstandards auf diese soft-skills <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/121018manageagile2012accmv1-2-130113011704-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Agile Culture Capability Model - Impedance Mismatch und Einfluss von Kulturstandards in agilen Projekten mit On-/Near- und Offshore Teams Off-shore, Near-shore, Outsourcing? Nein, das will ich nicht, sagen viele, nicht schon wieder. Und nicht ohne Grund. Viele Organisationen haben bereits klassische (z.B. mit komponentenbasierten Teams und Wasserfall) Near-/Offshore Projekte gemacht, leider sehr oft ohne Erfolg. Bei diesen projekten h辰ttte man sagen k旦nnen, dass die management methodik falsch war. Einfach. Agilit辰t gab uns neune Hoffnung, die Nearshore-/Offshore Projekte richtig machen und erfolgreich abschlieen zu k旦nnen. Agile, das ist die Heilung. Leider 辰hlich wie bei den klassischen Methoden, viele von diesen Agilen Near-/Offshore Projekten waren sogar weniger erfolgreich als wenn man diese mit den klasisichen methoden durchgef端hrt h辰tte. Wenn das Problem nicht in den Methoden lag, dann wo? Vielleicht waren es doch die Kulturstandards die die Akzeptanz von der agilen Werten und Prinzipien erschweren oder sogar unm旦glich machen? Vielleicht ist die Agilit辰t etwas Westliches? Kann man behaupt agile F辰higkeiten messen? In diesem Talk wird der Autor das Thema Einflu von den kulturelen Standards auf genauer angehen. Im Zentrum das Talks steht ACCM im Fokus. Das Model basiert auf zwei Matrizen: die erste beschreibt die korrelation zwischen den kulturelenstandards (wie z.B. eine starke hierarchische struktur) und den agilen und im jedem Projekt erforderlichen soft-skills (wie self-organisation aka decision making and commitments). Ein weigthsystem gibt die Information wie stark ist die Auswirkung der Kunlturenstandards auf diese soft-skills
Manage Agile 2012 Berlin Agile Culture Capability Model from Adam Boczek
]]> 1065 8 https://cdn.slidesharecdn.com/ss_thumbnails/121018manageagile2012accmv1-2-130113011704-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 安艶庄 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 SOA Days 2012 Bonn Process Control Center https://de.slideshare.net/slideshow/adam-boczek-soa-days-bonn-process-control-center/15970164 soadays2012vortragpcc1-1v2-130113011418-phpapp02
]]>
]]> Sun, 13 Jan 2013 01:14:18 GMT https://de.slideshare.net/slideshow/adam-boczek-soa-days-bonn-process-control-center/15970164 AdamBoczek@slideshare.net(AdamBoczek) SOA Days 2012 Bonn Process Control Center AdamBoczek <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/soadays2012vortragpcc1-1v2-130113011418-phpapp02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
from Adam Boczek
]]> 973 67 https://cdn.slidesharecdn.com/ss_thumbnails/soadays2012vortragpcc1-1v2-130113011418-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation 安艶庄 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-AdamBoczek-48x48.jpg?cb=1660892564 Management: IT Strategy, Agile Organization, Management, Leadership, Project Management, Agile Project Management, Nearshore Project Management, Offshore Project Management, Requirements Engineering, Risk Management, Scrum, Kanban, Commitment-based Project Management Architecture: Agile Architecture, Business Architecture, Event Driven Architecture, Clean Architecture, Enterprise Architecture, Risk-driven Architecture, Enterprise Architecture Management, Architecture Governance, Architecture Assessment, Architecture Review, Architecture Trade-off Analysis Method, Open Infrastructure Architecture Method, Service Oriented Architecture, Enterprise Application Integration, Domain Driven Des... boczek.com https://cdn.slidesharecdn.com/ss_thumbnails/20180219javaentwicklertag2018keynoteagileittransformationv1-180314110055-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/agile-it-transformation-java-entwicklertag-2018-keynote-90633252/90633252 Agile IT Transformatio... https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekjax2015accmv1-150424011331-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds AdamBoczek/can-wee-all-be-agile-in-the-same-way-jax-conference-2015-accm-v11 Can We All Be Agile in... https://cdn.slidesharecdn.com/ss_thumbnails/adamboczekace2015agilearchitecturev1-150317012841-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/adam-boczek-ace-2015-agile-architecture-from-the-trenches/45923517 ACE 2015 Conference Ag...