�ݺ�ߣshows by User: dwhelan

�ݺ�ߣshows by User: dwhelan / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: dwhelan / Fri, 10 Nov 2017 21:08:58 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: dwhelan Technical debt is a systemic problem - not a personal failing /slideshow/technical-debt-is-a-systemic-problem-not-a-personal-failing/81869394 technicaldebtisasystemicproblem-notapersonalfailing-171110210858
This is a presentation Chris Chapman I delivered at the Toronto Agile Conference 2017. We take a 'systems thinking' view of technical debt. The premise is that mounting technical debt is a not a problem ... it's a system problem. We depict system problems using causal loop diagrams and propose steps, via balancing loops, to shift the system to a healthier state. We use the term 'technical health' to describe this systems view of technical debt.]]>
This is a presentation Chris Chapman I delivered at the Toronto Agile Conference 2017. We take a 'systems thinking' view of technical debt. The premise is that mounting technical debt is a not a problem ... it's a system problem. We depict system problems using causal loop diagrams and propose steps, via balancing loops, to shift the system to a healthier state. We use the term 'technical health' to describe this systems view of technical debt.]]> Fri, 10 Nov 2017 21:08:58 GMT /slideshow/technical-debt-is-a-systemic-problem-not-a-personal-failing/81869394 dwhelan@slideshare.net(dwhelan) Technical debt is a systemic problem - not a personal failing dwhelan This is a presentation Chris Chapman I delivered at the Toronto Agile Conference 2017. We take a 'systems thinking' view of technical debt. The premise is that mounting technical debt is a not a problem ... it's a system problem. We depict system problems using causal loop diagrams and propose steps, via balancing loops, to shift the system to a healthier state. We use the term 'technical health' to describe this systems view of technical debt. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/technicaldebtisasystemicproblem-notapersonalfailing-171110210858-thumbnail.jpg?width=120&height=120&fit=bounds" /> This is a presentation Chris Chapman I delivered at the Toronto Agile Conference 2017. We take a 'systems thinking' view of technical debt. The premise is that mounting technical debt is a not a problem ... it's a system problem. We depict system problems using causal loop diagrams and propose steps, via balancing loops, to shift the system to a healthier state. We use the term 'technical health' to describe this systems view of technical debt.

Technical debt is a systemic problem - not a personal failing from Declan Whelan

]]> 1331 8 https://cdn.slidesharecdn.com/ss_thumbnails/technicaldebtisasystemicproblem-notapersonalfailing-171110210858-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 From Technical Debt to Technical Health /slideshow/from-technical-debt-to-technical-health/69105660 aatdwebinarv7-161116162117
Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem? In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team.]]>
Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem? In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team.]]> Wed, 16 Nov 2016 16:21:17 GMT /slideshow/from-technical-debt-to-technical-health/69105660 dwhelan@slideshare.net(dwhelan) From Technical Debt to Technical Health dwhelan Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem? In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/aatdwebinarv7-161116162117-thumbnail.jpg?width=120&height=120&fit=bounds" /> Everyone agrees that technical debt is a burden on software innovation that we would rather avoid, and certainly clean up whenever possible. However, in most organizations, people don't prevent technical debt nearly as much as they should, and they don't ever get the time to clean it up. Why, then, if there are clear incentives to deal with technical debt, is it a rampant problem? In this session, we will focus on how to deal with technical debt on several levels, including the individual developer, the team, the software value stream, and the larger organization. While technical debt may manifest itself in a developer's IDE, the problem starts long before the developer decides to copy and paste some code, or creates an overly-complex and under-documented class. The pressures on teams and individuals to take on more debt than they should come from many sources. Therefore, the solutions to the technical debt problem must extend beyond the team.

From Technical Debt to Technical Health from Declan Whelan

]]> 2450 6 https://cdn.slidesharecdn.com/ss_thumbnails/aatdwebinarv7-161116162117-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 effective agile adoption /slideshow/effective-agile-adoption/55181196 effectiveagileadoption-151116223436-lva1-app6891
Many organizations adopting Agile fail to bring about lasting change. This is often because Agile is seen as a developer team "methodology". Effective Agile adoption depends on aligning the adoption strategy with the value stream across the organization. In this talk, Declan will introduce the Agile Fluency model as a mechanism for targeting an Agile adoption to the realities of your organization. Along the way we will talk about aligning your organizational structure with your organization's purpose and the importance of managing technical debt.]]>
Many organizations adopting Agile fail to bring about lasting change. This is often because Agile is seen as a developer team "methodology". Effective Agile adoption depends on aligning the adoption strategy with the value stream across the organization. In this talk, Declan will introduce the Agile Fluency model as a mechanism for targeting an Agile adoption to the realities of your organization. Along the way we will talk about aligning your organizational structure with your organization's purpose and the importance of managing technical debt.]]> Mon, 16 Nov 2015 22:34:36 GMT /slideshow/effective-agile-adoption/55181196 dwhelan@slideshare.net(dwhelan) effective agile adoption dwhelan Many organizations adopting Agile fail to bring about lasting change. This is often because Agile is seen as a developer team "methodology". Effective Agile adoption depends on aligning the adoption strategy with the value stream across the organization. In this talk, Declan will introduce the Agile Fluency model as a mechanism for targeting an Agile adoption to the realities of your organization. Along the way we will talk about aligning your organizational structure with your organization's purpose and the importance of managing technical debt. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/effectiveagileadoption-151116223436-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> Many organizations adopting Agile fail to bring about lasting change. This is often because Agile is seen as a developer team "methodology". Effective Agile adoption depends on aligning the adoption strategy with the value stream across the organization. In this talk, Declan will introduce the Agile Fluency model as a mechanism for targeting an Agile adoption to the realities of your organization. Along the way we will talk about aligning your organizational structure with your organization's purpose and the importance of managing technical debt.

effective agile adoption from Declan Whelan

]]> 912 5 https://cdn.slidesharecdn.com/ss_thumbnails/effectiveagileadoption-151116223436-lva1-app6891-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 Big Balls of Mud /slideshow/big-balls-of-mud-54760970/54760970 bigballofmud-151105030211-lva1-app6891
This is a rough presentation from my notes for the SDEC 2015 conference. The basic premise is that Big Balls of Mud result from rampant technical debt. And the cost of technical debt is large. I believe that the forces driving us to repeatedly build big balls of mud are strong. And while technical craftsmanship is necessary to address it, by itself it is insufficient. I explore some root causes through the use of system archetypes. Finally, I suggest some remedial steps for dealing with technical debt based on the quadrant from Martin Fowler. Thanks for checking this out!]]>
This is a rough presentation from my notes for the SDEC 2015 conference. The basic premise is that Big Balls of Mud result from rampant technical debt. And the cost of technical debt is large. I believe that the forces driving us to repeatedly build big balls of mud are strong. And while technical craftsmanship is necessary to address it, by itself it is insufficient. I explore some root causes through the use of system archetypes. Finally, I suggest some remedial steps for dealing with technical debt based on the quadrant from Martin Fowler. Thanks for checking this out!]]> Thu, 05 Nov 2015 03:02:11 GMT /slideshow/big-balls-of-mud-54760970/54760970 dwhelan@slideshare.net(dwhelan) Big Balls of Mud dwhelan This is a rough presentation from my notes for the SDEC 2015 conference. The basic premise is that Big Balls of Mud result from rampant technical debt. And the cost of technical debt is large. I believe that the forces driving us to repeatedly build big balls of mud are strong. And while technical craftsmanship is necessary to address it, by itself it is insufficient. I explore some root causes through the use of system archetypes. Finally, I suggest some remedial steps for dealing with technical debt based on the quadrant from Martin Fowler. Thanks for checking this out! <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/bigballofmud-151105030211-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> This is a rough presentation from my notes for the SDEC 2015 conference. The basic premise is that Big Balls of Mud result from rampant technical debt. And the cost of technical debt is large. I believe that the forces driving us to repeatedly build big balls of mud are strong. And while technical craftsmanship is necessary to address it, by itself it is insufficient. I explore some root causes through the use of system archetypes. Finally, I suggest some remedial steps for dealing with technical debt based on the quadrant from Martin Fowler. Thanks for checking this out!

Big Balls of Mud from Declan Whelan

]]> 763 4 https://cdn.slidesharecdn.com/ss_thumbnails/bigballofmud-151105030211-lva1-app6891-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 Navigating Organizational Change /slideshow/navigating-organizational-change/54129683 agile2015navigating-organizationalchangev3-151019172014-lva1-app6891
Einstein said "We cannot solve our problems with the same thinking we used when we created them" yet many organizations that want to adopt Agile end up using existing organizational structures to make it happen. That is, they create a centralized team to roll Agile out, define metrics, create a dashboard, communication and training plan and finally a Sharepoint site to push the change outwards. The outcome ends up being another failed Agile transformation story because people either resisted change or they failed to change their organizational culture. This isn't an 'Agile' problem, it's a structure problem. The real issue is that organizational structures are designed to serve the internal purposes of the organization, not their customers or the value they create for their customers. In this session we'll explore why 'being Agile' only gets you so far.]]>
Einstein said "We cannot solve our problems with the same thinking we used when we created them" yet many organizations that want to adopt Agile end up using existing organizational structures to make it happen. That is, they create a centralized team to roll Agile out, define metrics, create a dashboard, communication and training plan and finally a Sharepoint site to push the change outwards. The outcome ends up being another failed Agile transformation story because people either resisted change or they failed to change their organizational culture. This isn't an 'Agile' problem, it's a structure problem. The real issue is that organizational structures are designed to serve the internal purposes of the organization, not their customers or the value they create for their customers. In this session we'll explore why 'being Agile' only gets you so far.]]> Mon, 19 Oct 2015 17:20:14 GMT /slideshow/navigating-organizational-change/54129683 dwhelan@slideshare.net(dwhelan) Navigating Organizational Change dwhelan Einstein said "We cannot solve our problems with the same thinking we used when we created them" yet many organizations that want to adopt Agile end up using existing organizational structures to make it happen. That is, they create a centralized team to roll Agile out, define metrics, create a dashboard, communication and training plan and finally a Sharepoint site to push the change outwards. The outcome ends up being another failed Agile transformation story because people either resisted change or they failed to change their organizational culture. This isn't an 'Agile' problem, it's a structure problem. The real issue is that organizational structures are designed to serve the internal purposes of the organization, not their customers or the value they create for their customers. In this session we'll explore why 'being Agile' only gets you so far. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agile2015navigating-organizationalchangev3-151019172014-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> Einstein said "We cannot solve our problems with the same thinking we used when we created them" yet many organizations that want to adopt Agile end up using existing organizational structures to make it happen. That is, they create a centralized team to roll Agile out, define metrics, create a dashboard, communication and training plan and finally a Sharepoint site to push the change outwards. The outcome ends up being another failed Agile transformation story because people either resisted change or they failed to change their organizational culture. This isn't an 'Agile' problem, it's a structure problem. The real issue is that organizational structures are designed to serve the internal purposes of the organization, not their customers or the value they create for their customers. In this session we'll explore why 'being Agile' only gets you so far.

Navigating Organizational Change from Declan Whelan

]]> 646 7 https://cdn.slidesharecdn.com/ss_thumbnails/agile2015navigating-organizationalchangev3-151019172014-lva1-app6891-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 Simple Design /slideshow/simple-design-46265656/46265656 simpledesign-150325072419-conversion-gate01
]]>
]]> Wed, 25 Mar 2015 07:24:19 GMT /slideshow/simple-design-46265656/46265656 dwhelan@slideshare.net(dwhelan) Simple Design dwhelan <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/simpledesign-150325072419-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" />

Simple Design from Declan Whelan

]]> 802 1 https://cdn.slidesharecdn.com/ss_thumbnails/simpledesign-150325072419-conversion-gate01-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 Domain Driven Design and Hexagonal Architecture with Rails /slideshow/domain-driven-design-and-hexagonal-srchitecture-with-rails/34033026 domaindrivendesignandhexagonalarchitecturewithrailsspeakerdeck-140428095807-phpapp01
You know that Domain Driven Design, Hexagonal Architecture, and the Single Responsibility Principle are important but it’s hard to know how to best apply them to Rails applications. Following the path of least-resistance will get you in trouble. In this session you will learn a way out of the “fat model, skinny controller” hell. You will leave with a roadmap to guide your design based on concepts from Domain Driven Design and Hexagonal Architecture.]]>
You know that Domain Driven Design, Hexagonal Architecture, and the Single Responsibility Principle are important but it’s hard to know how to best apply them to Rails applications. Following the path of least-resistance will get you in trouble. In this session you will learn a way out of the “fat model, skinny controller” hell. You will leave with a roadmap to guide your design based on concepts from Domain Driven Design and Hexagonal Architecture.]]> Mon, 28 Apr 2014 09:58:07 GMT /slideshow/domain-driven-design-and-hexagonal-srchitecture-with-rails/34033026 dwhelan@slideshare.net(dwhelan) Domain Driven Design and Hexagonal Architecture with Rails dwhelan You know that Domain Driven Design, Hexagonal Architecture, and the Single Responsibility Principle are important but it’s hard to know how to best apply them to Rails applications. Following the path of least-resistance will get you in trouble. In this session you will learn a way out of the “fat model, skinny controller” hell. You will leave with a roadmap to guide your design based on concepts from Domain Driven Design and Hexagonal Architecture. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/domaindrivendesignandhexagonalarchitecturewithrailsspeakerdeck-140428095807-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> You know that Domain Driven Design, Hexagonal Architecture, and the Single Responsibility Principle are important but it’s hard to know how to best apply them to Rails applications. Following the path of least-resistance will get you in trouble. In this session you will learn a way out of the “fat model, skinny controller” hell. You will leave with a roadmap to guide your design based on concepts from Domain Driven Design and Hexagonal Architecture.

Domain Driven Design and Hexagonal Architecture with Rails from Declan Whelan

]]> 8682 5 https://cdn.slidesharecdn.com/ss_thumbnails/domaindrivendesignandhexagonalarchitecturewithrailsspeakerdeck-140428095807-phpapp01-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 Win Win Conversations /dwhelan/win-win-conversations win-winconversations-130806092848-phpapp02
A powerful phrase we learn as agile coaches is to “*release the outcome!*”. In other words, coaching is most effective when we distance ourselves from the final outcomes. Instead, we should focus on helping those we are coaching, visualize and achieve the outcomes that are important to them. But many of us are Scrum Masters, managers, executives or in similar positions where we have a vested interest in outcomes. So, how do we effectively coach when we have such a bias? In this session you will learn and practice a powerful conversation tool that allows you to maintain a coaching stance when outcomes are personally important to you. This will allow you to build trust and align others around shared outcomes resulting in win-win situations. Many people also find this conversational tool to be very useful in their personal lives. ]]>
A powerful phrase we learn as agile coaches is to “*release the outcome!*”. In other words, coaching is most effective when we distance ourselves from the final outcomes. Instead, we should focus on helping those we are coaching, visualize and achieve the outcomes that are important to them. But many of us are Scrum Masters, managers, executives or in similar positions where we have a vested interest in outcomes. So, how do we effectively coach when we have such a bias? In this session you will learn and practice a powerful conversation tool that allows you to maintain a coaching stance when outcomes are personally important to you. This will allow you to build trust and align others around shared outcomes resulting in win-win situations. Many people also find this conversational tool to be very useful in their personal lives. ]]> Tue, 06 Aug 2013 09:28:48 GMT /dwhelan/win-win-conversations dwhelan@slideshare.net(dwhelan) Win Win Conversations dwhelan A powerful phrase we learn as agile coaches is to “*release the outcome!*”. In other words, coaching is most effective when we distance ourselves from the final outcomes. Instead, we should focus on helping those we are coaching, visualize and achieve the outcomes that are important to them. But many of us are Scrum Masters, managers, executives or in similar positions where we have a vested interest in outcomes. So, how do we effectively coach when we have such a bias? In this session you will learn and practice a powerful conversation tool that allows you to maintain a coaching stance when outcomes are personally important to you. This will allow you to build trust and align others around shared outcomes resulting in win-win situations. Many people also find this conversational tool to be very useful in their personal lives. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/win-winconversations-130806092848-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> A powerful phrase we learn as agile coaches is to “*release the outcome!*”. In other words, coaching is most effective when we distance ourselves from the final outcomes. Instead, we should focus on helping those we are coaching, visualize and achieve the outcomes that are important to them. But many of us are Scrum Masters, managers, executives or in similar positions where we have a vested interest in outcomes. So, how do we effectively coach when we have such a bias? In this session you will learn and practice a powerful conversation tool that allows you to maintain a coaching stance when outcomes are personally important to you. This will allow you to build trust and align others around shared outcomes resulting in win-win situations. Many people also find this conversational tool to be very useful in their personal lives.

Win Win Conversations from Declan Whelan

]]> 1287 9 https://cdn.slidesharecdn.com/ss_thumbnails/win-winconversations-130806092848-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 2012 Simple Design Applied /slideshow/agile-2012-simple-design/13954604 simpledesign-published-120813010839-phpapp01
Presentation at Agile 2012 Experience and research shows that developers spend as much as 70% of their time reading and understanding code. In this workshop you will learn how the rules of Simple Design help to reduce this percentage so you spend more time creating valuable code. This will be a highly collaborative workshop where you share your insights and learn from others. You’ll get to the heart of Simple Design by reviewing code - both beautiful and ugly. You’ll get to practice by improving the readability and understandability of real code. You’ll leave this workshop ready to apply Simple Design to improve your own code.]]>
Presentation at Agile 2012 Experience and research shows that developers spend as much as 70% of their time reading and understanding code. In this workshop you will learn how the rules of Simple Design help to reduce this percentage so you spend more time creating valuable code. This will be a highly collaborative workshop where you share your insights and learn from others. You’ll get to the heart of Simple Design by reviewing code - both beautiful and ugly. You’ll get to practice by improving the readability and understandability of real code. You’ll leave this workshop ready to apply Simple Design to improve your own code.]]> Mon, 13 Aug 2012 01:08:35 GMT /slideshow/agile-2012-simple-design/13954604 dwhelan@slideshare.net(dwhelan) Agile 2012 Simple Design Applied dwhelan Presentation at Agile 2012 Experience and research shows that developers spend as much as 70% of their time reading and understanding code. In this workshop you will learn how the rules of Simple Design help to reduce this percentage so you spend more time creating valuable code. This will be a highly collaborative workshop where you share your insights and learn from others. You’ll get to the heart of Simple Design by reviewing code - both beautiful and ugly. You’ll get to practice by improving the readability and understandability of real code. You’ll leave this workshop ready to apply Simple Design to improve your own code. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/simpledesign-published-120813010839-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation at Agile 2012 Experience and research shows that developers spend as much as 70% of their time reading and understanding code. In this workshop you will learn how the rules of Simple Design help to reduce this percentage so you spend more time creating valuable code. This will be a highly collaborative workshop where you share your insights and learn from others. You’ll get to the heart of Simple Design by reviewing code - both beautiful and ugly. You’ll get to practice by improving the readability and understandability of real code. You’ll leave this workshop ready to apply Simple Design to improve your own code.

Agile 2012 Simple Design Applied from Declan Whelan

]]> 1748 13 https://cdn.slidesharecdn.com/ss_thumbnails/simpledesign-published-120813010839-phpapp01-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 Releasing your teams energy through 'pull' conversations /slideshow/releasing-your-teams-energy-through-pull-conversations/13254788 releasingyourteamsenergyfinal-120608195521-phpapp01
Release your team's intelligent energy through five powerful conversations. An introduction to the "pull conversation model" from Juice.]]>
Release your team's intelligent energy through five powerful conversations. An introduction to the "pull conversation model" from Juice.]]> Fri, 08 Jun 2012 19:55:19 GMT /slideshow/releasing-your-teams-energy-through-pull-conversations/13254788 dwhelan@slideshare.net(dwhelan) Releasing your teams energy through 'pull' conversations dwhelan Release your team's intelligent energy through five powerful conversations. An introduction to the "pull conversation model" from Juice. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/releasingyourteamsenergyfinal-120608195521-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Release your team's intelligent energy through five powerful conversations. An introduction to the "pull conversation model" from Juice.

Releasing your teams energy through 'pull' conversations from Declan Whelan

]]> 1495 3 https://cdn.slidesharecdn.com/ss_thumbnails/releasingyourteamsenergyfinal-120608195521-phpapp01-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 Specification by Example /slideshow/specification-by-example-12983304/12983304 specificationbyexample-120518090221-phpapp02
An introduction to Specification by Example.]]>
An introduction to Specification by Example.]]> Fri, 18 May 2012 09:02:20 GMT /slideshow/specification-by-example-12983304/12983304 dwhelan@slideshare.net(dwhelan) Specification by Example dwhelan An introduction to Specification by Example. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/specificationbyexample-120518090221-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> An introduction to Specification by Example.

Specification by Example from Declan Whelan

]]> 61497 10 https://cdn.slidesharecdn.com/ss_thumbnails/specificationbyexample-120518090221-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 Solid principles /slideshow/solid-principles-12250495/12250495 solidprinciples-120401205721-phpapp01
This presentation outlines the SOLID principles with some simple code examples to show the principle in action.]]>
This presentation outlines the SOLID principles with some simple code examples to show the principle in action.]]> Sun, 01 Apr 2012 20:57:20 GMT /slideshow/solid-principles-12250495/12250495 dwhelan@slideshare.net(dwhelan) Solid principles dwhelan This presentation outlines the SOLID principles with some simple code examples to show the principle in action. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/solidprinciples-120401205721-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> This presentation outlines the SOLID principles with some simple code examples to show the principle in action.

Solid principles from Declan Whelan

]]> 2934 4 https://cdn.slidesharecdn.com/ss_thumbnails/solidprinciples-120401205721-phpapp01-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 Learning is Key to Agile Success: Agile Vancouver 2010 /slideshow/agile-learning-agile-vancouver-2010/5656354 agilelearning-agilevancouver2010-101103102848-phpapp02
Nurturing a learning culture on your agile team ]]>
Nurturing a learning culture on your agile team ]]> Wed, 03 Nov 2010 10:28:45 GMT /slideshow/agile-learning-agile-vancouver-2010/5656354 dwhelan@slideshare.net(dwhelan) Learning is Key to Agile Success: Agile Vancouver 2010 dwhelan Nurturing a learning culture on your agile team <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agilelearning-agilevancouver2010-101103102848-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Nurturing a learning culture on your agile team

Learning is Key to Agile Success: Agile Vancouver 2010 from Declan Whelan

]]> 849 6 https://cdn.slidesharecdn.com/ss_thumbnails/agilelearning-agilevancouver2010-101103102848-phpapp02-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 learning agile 2010 /slideshow/agile-learning-agile-2010/4971187 agilelearningagile2010-100814165317-phpapp02
This slide deck is about nurturing a learning culture with an agile team. The main ideas are that effective learning is what enables teams to respond to change and deliver exception value. The presentation highlights some key ]]>
This slide deck is about nurturing a learning culture with an agile team. The main ideas are that effective learning is what enables teams to respond to change and deliver exception value. The presentation highlights some key ]]> Sat, 14 Aug 2010 16:53:10 GMT /slideshow/agile-learning-agile-2010/4971187 dwhelan@slideshare.net(dwhelan) Agile learning agile 2010 dwhelan This slide deck is about nurturing a learning culture with an agile team. The main ideas are that effective learning is what enables teams to respond to change and deliver exception value. The presentation highlights some key <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningagile2010-100814165317-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> This slide deck is about nurturing a learning culture with an agile team. The main ideas are that effective learning is what enables teams to respond to change and deliver exception value. The presentation highlights some key

Agile learning agile 2010 from Declan Whelan

]]> 1728 5 https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningagile2010-100814165317-phpapp02-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 Learning (60 minute version) /slideshow/agile-learning-60-minute-version/3964598 agilelearningforpointclickcare-100504084325-phpapp01
Reduced version of Agile Learning presentation to fit in 60 minutes]]>
Reduced version of Agile Learning presentation to fit in 60 minutes]]> Tue, 04 May 2010 08:43:17 GMT /slideshow/agile-learning-60-minute-version/3964598 dwhelan@slideshare.net(dwhelan) Agile Learning (60 minute version) dwhelan Reduced version of Agile Learning presentation to fit in 60 minutes <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningforpointclickcare-100504084325-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Reduced version of Agile Learning presentation to fit in 60 minutes

Agile Learning (60 minute version) from Declan Whelan

]]> 580 3 https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningforpointclickcare-100504084325-phpapp01-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 Cuke2Beer /slideshow/cuke2beer/2111087 cuke2beer-091002090200-phpapp01
5 minute presentation on cucumber presented at DemoCampGuelph11]]>
5 minute presentation on cucumber presented at DemoCampGuelph11]]> Fri, 02 Oct 2009 09:01:54 GMT /slideshow/cuke2beer/2111087 dwhelan@slideshare.net(dwhelan) Cuke2Beer dwhelan 5 minute presentation on cucumber presented at DemoCampGuelph11 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/cuke2beer-091002090200-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> 5 minute presentation on cucumber presented at DemoCampGuelph11

Cuke2Beer from Declan Whelan

]]> 1338 3 https://cdn.slidesharecdn.com/ss_thumbnails/cuke2beer-091002090200-phpapp01-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 Learning from Agile 2009 /slideshow/agile-learning-from-agile-2009/1944324 agilelearningfinal-090902165957-phpapp01
Presentation on building a learning culture melding principles & practices from systems thinking, Satir, Shu Ha Ri. Ends with a learning map you can use to help build a learning culture on your agile team.]]>
Presentation on building a learning culture melding principles & practices from systems thinking, Satir, Shu Ha Ri. Ends with a learning map you can use to help build a learning culture on your agile team.]]> Wed, 02 Sep 2009 16:59:48 GMT /slideshow/agile-learning-from-agile-2009/1944324 dwhelan@slideshare.net(dwhelan) Agile Learning from Agile 2009 dwhelan Presentation on building a learning culture melding principles & practices from systems thinking, Satir, Shu Ha Ri. Ends with a learning map you can use to help build a learning culture on your agile team. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningfinal-090902165957-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation on building a learning culture melding principles & practices from systems thinking, Satir, Shu Ha Ri. Ends with a learning map you can use to help build a learning culture on your agile team.

Agile Learning from Agile 2009 from Declan Whelan

]]> 1584 5 https://cdn.slidesharecdn.com/ss_thumbnails/agilelearningfinal-090902165957-phpapp01-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, Tdd And .Net /slideshow/agile-tdd-and-net-1641991/1641991 agiletddand-net-090625222314-phpapp01
Quick overview of agile craftsmanship. This was a prelude to a Coding Dojo with .NET and C#.]]>
Quick overview of agile craftsmanship. This was a prelude to a Coding Dojo with .NET and C#.]]> Thu, 25 Jun 2009 22:23:04 GMT /slideshow/agile-tdd-and-net-1641991/1641991 dwhelan@slideshare.net(dwhelan) Agile, Tdd And .Net dwhelan Quick overview of agile craftsmanship. This was a prelude to a Coding Dojo with .NET and C#. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiletddand-net-090625222314-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Quick overview of agile craftsmanship. This was a prelude to a Coding Dojo with .NET and C#.

Agile, Tdd And .Net from Declan Whelan

]]> 748 2 https://cdn.slidesharecdn.com/ss_thumbnails/agiletddand-net-090625222314-phpapp01-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 Testing: The Role Of The Agile Tester /slideshow/agile-testing-and-the-role-of-the-agile-tester/1587978 agiletestingandtheroleoftheagiletester2008-09-26rev4-090615163750-phpapp01
This presentation provides an overview of the role of testers on agile teams. In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value. Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.]]>
This presentation provides an overview of the role of testers on agile teams. In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value. Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.]]> Mon, 15 Jun 2009 16:37:45 GMT /slideshow/agile-testing-and-the-role-of-the-agile-tester/1587978 dwhelan@slideshare.net(dwhelan) Agile Testing: The Role Of The Agile Tester dwhelan This presentation provides an overview of the role of testers on agile teams. In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value. Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingandtheroleoftheagiletester2008-09-26rev4-090615163750-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> This presentation provides an overview of the role of testers on agile teams. In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value. Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.

Agile Testing: The Role Of The Agile Tester from Declan Whelan

]]> 47500 23 https://cdn.slidesharecdn.com/ss_thumbnails/agiletestingandtheroleoftheagiletester2008-09-26rev4-090615163750-phpapp01-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-dwhelan-48x48.jpg?cb=1699657915 I provide process and technical agile coaching and training. dpwhelan.com https://cdn.slidesharecdn.com/ss_thumbnails/technicaldebtisasystemicproblem-notapersonalfailing-171110210858-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/technical-debt-is-a-systemic-problem-not-a-personal-failing/81869394 Technical debt is a sy... https://cdn.slidesharecdn.com/ss_thumbnails/aatdwebinarv7-161116162117-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/from-technical-debt-to-technical-health/69105660 From Technical Debt to... https://cdn.slidesharecdn.com/ss_thumbnails/effectiveagileadoption-151116223436-lva1-app6891-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/effective-agile-adoption/55181196 effective agile adoption