Loading…
XP2019 has ended
Tutorials & Workshops [clear filter]
Tuesday, May 21
 

9:00am EDT

Analysis for Agilists (Michael Bolton)
Abstract:
  • How do we go about understanding something complex?
  • How do we move from confusion to clarity?
  • What strategies and approaches can we use to identify and reason about things that matter?
  • When we’re dropped into a development or testing situation, how do we make sense of it all?
  • How can we rapidly achieve a deeper understanding of things that we know little or nothing about?
  • How do we anticipate and manage product, project, and business risk?
  • How can we develop skills to make us more powerful analysts, developers, testers, and critics?
Analysis – the study of things and ideas by examining their elements and structures — is a way of developing answers to all of these questions. Analysis is central to development and testing, yet not always well studied, discussed, or understood. Analysis can be quick and shallow, slower and deeper, narrowly or broadly focused, formal or informal.

In this one-day workshop, we'll engage in exercises and discussions that highlight ways of analyzing
  • Products
  • Technologies
  • Systems
  • Language
  • Test conditions
  • Risk
  • Social groups
  • Problems
  • Strategies
  • Analysis itself!

Learning Outcomes:
  • Participants may develop insights into
  • Sensemaking; how and why we go about analysis
  • Factoring; identify elements and dimensions that might make a difference
  • Modeling; representing complex things with useful simplifications
  • Revealing and managing assumptions
  • Geometric analysis; patterns, groupings, intervals, boundaries, symmetries…
  • Linguistic analysis; structures of what’s there and what’s missing in the ways we speak
  • General Systems Thinking; the role of the observer; aggregation; decomposition
  • Critical thinking: how might we be fooling ourselves? How can we defend against that?


Speakers
avatar for Michael Bolton

Michael Bolton

Consulting Software Tester, DevelopSense
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software... Read More →



Tuesday May 21, 2019 9:00am - 10:30am EDT
E-2025 (2nd Floor)

9:00am EDT

Experience the Kanban Policy Game - Improving Performance Through Evolutionary Change (Jason Newberg, Rakshinda Aslam)

Abstract:
The Kanban Method emphasizes the importance of policies considerably. In the service delivery principles, “Your organization is an ecosystem of interdependent services steered by its policies, reflect regularly on their effectiveness and improve them.” So, instead of viewing our processes as a sequence of activities, workflows, roles and responsibilities, we view the existing processes as sets of policies and define those policies explicitly. The fourth practice of the Kanban Method asks us to “Make policies explicit", allowing the policies to be challenged and changed.

The Kanban Policy Game is a fun way to experience how policies affect productivity (i.e. number of work items produced per unit time). The game has rules and policies. Rules are fixed and cannot be changed, but the policies evolve experimentally.

In the game we act as an Agile coach hired to improve the performance of teams in the client organization. The game has three iterations.
  • In the first iteration we make our three policies explicit: “Collaboration Policy”, “Pull Policy” and “WIP Policy”. We want to understand and measure the current state of the system. We discover that the organization measures individual productivity and wants their "resources" to be fully utilized.
  • In the second iteration we change only the “WIP Policy” by limiting the work in process.
  • In the third iteration we change only the “Collaboration Policy”. From now on the organization will not measure individual productivity but the performance of a team as a whole.

"When you want to make a change, first, make the change easy. (Warning, this may be hard.) Then make the easy change.” ~ Kent Beck

This session is targeted for practicing agile team members, managers, and coaches.
Kanban Policy Game created by Dimitar Bakardzhiev is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License
Featureban is a game created by Mike Burrows and licensed under a Creative Commons Attribution- ShareAlike 4.0 International License.

Learning Outcomes:
  • “Collaboration Policy”, “Performance Evaluation Policy” and “WIP Policy” have huge impact on productivity.
  • The J-curve effect can be experienced if we limit WIP in an organization where collaboration level is low.
  • Limiting WIP when we measure individual performance has a negative effect on the productivity of the team as a whole.
  • Limiting WIP when we don't measure individual performance has a positive effect on the productivity of the team as a whole.
  • The collaboration level in a team can be measured.
  • Policy changes are cheap and have huge effect on productivity.
  • What a Kanban system looks like and how to apply the 6 practices (Visualize invisible knowledge work, Limit WIP, Manage Flow, Make policies explicit, Implement feedback loops, Improve collaboratively - evolve experimentally)


Speakers
avatar for Jason Newberg

Jason Newberg

JPMorgan Chase
Jason Newberg is member of a team of coaches in Global Technology at JPMorgan Chase focused on enabling organizational and business agility at every level of the organization. Jason’s approach to coaching is grounded in the principles of Socio-Technical Systems theory with a focus... Read More →



Tuesday May 21, 2019 9:00am - 10:30am EDT
E-4025 (4th Floor)

9:00am EDT

Surviving Legacy Code (J. B. Rainsberger)

Abstract:
Working with legacy code remains difficult. We feel afraid to change it, but sometimes we have no choice. Learn key techniques to help you manage your risk. J. B. Rainsberger gives you a safe code base in which to experiment and he guides you through the confusing risk/reward decisions involved in living with legacy code. You will learn and practise several specific, safe techniques that you can start using on your own legacy code once you return to your project.

You should attend this workshop if you have code that seems impossible to change, code that you feel really uncomfortable changing, or you want to avoid creating code like that in the future. J. B.’s advice transcends business domains and programming languages. Moreover, you get to find out how he thinks through the tough choices as well as improve the design with (relative) grace and ease.

After learning a technique, it’s your turn to try it out for yourself. All you need is a working development environment for your favorite programming language and to install git. (Strictly speaking, you don’t even need to do that, but you probably should.) If you get stuck, then J. B. helps you get moving again. If something seems strange, then J. B. helps you make sense of it–or maybe he agrees that it’s strange and you should try something else.

Learning Outcomes:
  • See the central conflict in working with legacy code: I want to add tests to refactor safely, but I need to refactor to add tests at a reasonable cost.
  • Learn how to add tests quickly to existing code using the text-based output that the system already produces.
  • Learn 4 key design techniques that help address the central conflict of legacy code.
  • Learn the core principles of rescuing legacy code: optimize for safety, document everything, embrace imperfection, play the long game, you can't chase all the rabbits.
  • Learn how to maintain focus in the inherently distracting environment of rescuing legacy code.
  • Learn how to work more harmoniously with people in the inherently frustrating and anxiety-inducing atmosphere of legacy systems.
  • Have a few tricks to start using immediately when returning to work in addition to some longer-term plans for improvement.


Speakers
avatar for J. B. Rainsberger

J. B. Rainsberger

Trusted Adviser, jbrains.ca
J. B. Rainsberger helps software companies better satisfy their customers and the businesses they support. Over the years, he has learned to write valuable software, turned himself into a joy to work with, and built a life that he loves. He has traveled the world sharing what he’s... Read More →


Tuesday May 21, 2019 9:00am - 10:30am EDT
E-2022 (2nd Floor)

9:00am EDT

Workshop: Architecture in an Agile World (Dennis Mancl, Steven Fraser, Werner Wild)

Abstract:
The world is moving faster than ever, and our software development techniques are struggling to keep up. We feel we need to have an agile feature set, but without a well-defined and understandable architecture, we feel like everything is in chaos. How do we manage the balance between architecture and agility?

This half-day workshop will be an exploration of the issues and obstacles doing agile development in an environment where we also need to have a sound architecture. Some of the issues are "cultural" -- how to get architects and agilists to communicate and work together effectively. Other issues are technical -- building the right lightweight architectural artifacts that still permit developers to explore and experiment. The workshop will create a report based on the conclusions of the workshop participants.

Learning Outcomes:
  • Understanding some of the risks and opportunities of blending agile and architecture-driven methods
  • Learn how architects establish credibility with agile development team members and how agilists can negotiate with architects
  • Discover some of the “good practices” that should be part of the toolkit of agilists and architects



Speakers
avatar for Steven Fraser

Steven Fraser

Impresario & Principal Consultant, Innoxec (Innovation Executive Services)
Steven Fraser is based in Silicon Valley and has served as an innovation catalyst with global influence for HP, Cisco, Qualcomm, and Nortel. In addition to a year as a Visiting Scientist at Carnegie Mellon University’s Software Engineering Institute (SEI) consulting on domain engineering... Read More →
avatar for Dennis Mancl

Dennis Mancl

MSWX Software Experts
Dennis worked in software development in telecom for many years - he is an advocate for agile methods, and he has been involved in coaching for requirements modeling, software architecture planning, and legacy software techniques.
avatar for Werner Wild

Werner Wild

CEO, EVOLUTION(R)
Agile & Lean in Practice


Tuesday May 21, 2019 9:00am - 10:30am EDT
E-2024 (2nd Floor)

11:00am EDT

Analysis for Agilists (continued) (Michael Bolton)
Abstract:
  • How do we go about understanding something complex?
  • How do we move from confusion to clarity?
  • What strategies and approaches can we use to identify and reason about things that matter?
  • When we’re dropped into a development or testing situation, how do we make sense of it all?
  • How can we rapidly achieve a deeper understanding of things that we know little or nothing about?
  • How do we anticipate and manage product, project, and business risk?
  • How can we develop skills to make us more powerful analysts, developers, testers, and critics?
Analysis – the study of things and ideas by examining their elements and structures — is a way of developing answers to all of these questions. Analysis is central to development and testing, yet not always well studied, discussed, or understood. Analysis can be quick and shallow, slower and deeper, narrowly or broadly focused, formal or informal.

In this one-day workshop, we'll engage in exercises and discussions that highlight ways of analyzing
  • Products
  • Technologies
  • Systems
  • Language
  • Test conditions
  • Risk
  • Social groups
  • Problems
  • Strategies
  • Analysis itself!

Learning Outcomes:
  • Participants may develop insights into
  • Sensemaking; how and why we go about analysis
  • Factoring; identify elements and dimensions that might make a difference
  • Modeling; representing complex things with useful simplifications
  • Revealing and managing assumptions
  • Geometric analysis; patterns, groupings, intervals, boundaries, symmetries…
  • Linguistic analysis; structures of what’s there and what’s missing in the ways we speak
  • General Systems Thinking; the role of the observer; aggregation; decomposition
  • Critical thinking: how might we be fooling ourselves? How can we defend against that?


Speakers
avatar for Michael Bolton

Michael Bolton

Consulting Software Tester, DevelopSense
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software... Read More →


Tuesday May 21, 2019 11:00am - 12:30pm EDT
E-2025 (2nd Floor)

11:00am EDT

Experience the Kanban Policy Game (continued) - Improving Performance Through Evolutionary Change (Jason Newberg, Rakshinda Aslam))

Abstract:
The Kanban Method emphasizes the importance of policies considerably. In the service delivery principles, “Your organization is an ecosystem of interdependent services steered by its policies, reflect regularly on their effectiveness and improve them.” So, instead of viewing our processes as a sequence of activities, workflows, roles and responsibilities, we view the existing processes as sets of policies and define those policies explicitly. The fourth practice of the Kanban Method asks us to “Make policies explicit", allowing the policies to be challenged and changed.

The Kanban Policy Game is a fun way to experience how policies affect productivity (i.e. number of work items produced per unit time). The game has rules and policies. Rules are fixed and cannot be changed, but the policies evolve experimentally.

In the game we act as an Agile coach hired to improve the performance of teams in the client organization. The game has three iterations.
  • In the first iteration we make our three policies explicit: “Collaboration Policy”, “Pull Policy” and “WIP Policy”. We want to understand and measure the current state of the system. We discover that the organization measures individual productivity and wants their "resources" to be fully utilized.
  • In the second iteration we change only the “WIP Policy” by limiting the work in process.
  • In the third iteration we change only the “Collaboration Policy”. From now on the organization will not measure individual productivity but the performance of a team as a whole.

"When you want to make a change, first, make the change easy. (Warning, this may be hard.) Then make the easy change.” ~ Kent Beck

This session is targeted for practicing agile team members, managers, and coaches.
Kanban Policy Game created by Dimitar Bakardzhiev is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License
Featureban is a game created by Mike Burrows and licensed under a Creative Commons Attribution- ShareAlike 4.0 International License.

Learning Outcomes:
  • “Collaboration Policy”, “Performance Evaluation Policy” and “WIP Policy” have huge impact on productivity.
  • The J-curve effect can be experienced if we limit WIP in an organization where collaboration level is low.
  • Limiting WIP when we measure individual performance has a negative effect on the productivity of the team as a whole.
  • Limiting WIP when we don't measure individual performance has a positive effect on the productivity of the team as a whole.
  • The collaboration level in a team can be measured.
  • Policy changes are cheap and have huge effect on productivity.
  • What a Kanban system looks like and how to apply the 6 practices (Visualize invisible knowledge work, Limit WIP, Manage Flow, Make policies explicit, Implement feedback loops, Improve collaboratively - evolve experimentally)


Speakers
avatar for Jason Newberg

Jason Newberg

JPMorgan Chase
Jason Newberg is member of a team of coaches in Global Technology at JPMorgan Chase focused on enabling organizational and business agility at every level of the organization. Jason’s approach to coaching is grounded in the principles of Socio-Technical Systems theory with a focus... Read More →


Tuesday May 21, 2019 11:00am - 12:30pm EDT
E-4025 (4th Floor)

11:00am EDT

Surviving Legacy Code (continued) (J. B. Rainsberger)

Abstract:
Working with legacy code remains difficult. We feel afraid to change it, but sometimes we have no choice.
Learn key techniques to help you manage your risk. J. B. Rainsberger gives you a safe code base in which to experiment and he guides you through the confusing risk/reward decisions involved in living with legacy code. You will learn and practise several specific, safe techniques that you can start using on your own legacy code once you return to your project.
You should attend this workshop if you have code that seems impossible to change, code that you feel really uncomfortable changing, or you want to avoid creating code like that in the future. J. B.’s advice transcends business domains and programming languages. Moreover, you get to find out how he thinks through the tough choices as well as improve the design with (relative) grace and ease.
After learning a technique, it’s your turn to try it out for yourself. All you need is a working development environment for your favorite programming language and to install git. (Strictly speaking, you don’t even need to do that, but you probably should.) If you get stuck, then J. B. helps you get moving again. If something seems strange, then J. B. helps you make sense of it–or maybe he agrees that it’s strange and you should try something else.

Learning Outcomes:
  • See the central conflict in working with legacy code: I want to add tests to refactor safely, but I need to refactor to add tests at a reasonable cost.
  • Learn how to add tests quickly to existing code using the text-based output that the system already produces.
  • Learn 4 key design techniques that help address the central conflict of legacy code.
  • Learn the core principles of rescuing legacy code: optimize for safety, document everything, embrace imperfection, play the long game, you can't chase all the rabbits.
  • Learn how to maintain focus in the inherently distracting environment of rescuing legacy code.
  • Learn how to work more harmoniously with people in the inherently frustrating and anxiety-inducing atmosphere of legacy systems.
  • Have a few tricks to start using immediately when returning to work in addition to some longer-term plans for improvement.


Speakers
avatar for J. B. Rainsberger

J. B. Rainsberger

Trusted Adviser, jbrains.ca
J. B. Rainsberger helps software companies better satisfy their customers and the businesses they support. Over the years, he has learned to write valuable software, turned himself into a joy to work with, and built a life that he loves. He has traveled the world sharing what he’s... Read More →


Tuesday May 21, 2019 11:00am - 12:30pm EDT
E-2022 (2nd Floor)

11:00am EDT

Workshop: Architecture in an Agile World (continued) (Dennis Mancl, Steven Fraser, Werner Wild)

Abstract:
The world is moving faster than ever, and our software development techniques are struggling to keep up. We feel we need to have an agile feature set, but without a well-defined and understandable architecture, we feel like everything is in chaos. How do we manage the balance between architecture and agility?

This half-day workshop will be an exploration of the issues and obstacles doing agile development in an environment where we also need to have a sound architecture. Some of the issues are "cultural" -- how to get architects and agilists to communicate and work together effectively. Other issues are technical -- building the right lightweight architectural artifacts that still permit developers to explore and experiment. The workshop will create a final report based on the conclusions of the workshop participants.

Learning Outcomes:
  • Understanding some of the risks and opportunities of blending agile and architecture-driven methods
  • Learn how architects establish credibility with agile development team members and how agilists can negotiate with architects
  • Discover some of the “good practices” that should be part of the toolkit of agilists and architects



Speakers
avatar for Werner Wild

Werner Wild

CEO, EVOLUTION(R)
Agile & Lean in Practice
avatar for Dennis Mancl

Dennis Mancl

MSWX Software Experts
Dennis worked in software development in telecom for many years - he is an advocate for agile methods, and he has been involved in coaching for requirements modeling, software architecture planning, and legacy software techniques.
avatar for Steven Fraser

Steven Fraser

Impresario & Principal Consultant, Innoxec (Innovation Executive Services)
Steven Fraser is based in Silicon Valley and has served as an innovation catalyst with global influence for HP, Cisco, Qualcomm, and Nortel. In addition to a year as a Visiting Scientist at Carnegie Mellon University’s Software Engineering Institute (SEI) consulting on domain engineering... Read More →


Tuesday May 21, 2019 11:00am - 12:30pm EDT
E-2024 (2nd Floor)

1:30pm EDT

Analysis for Agilists (continued) (Michael Bolton)
Abstract:
  • How do we go about understanding something complex?
  • How do we move from confusion to clarity?
  • What strategies and approaches can we use to identify and reason about things that matter?
  • When we’re dropped into a development or testing situation, how do we make sense of it all?
  • How can we rapidly achieve a deeper understanding of things that we know little or nothing about?
  • How do we anticipate and manage product, project, and business risk?
  • How can we develop skills to make us more powerful analysts, developers, testers, and critics?
Analysis – the study of things and ideas by examining their elements and structures — is a way of developing answers to all of these questions. Analysis is central to development and testing, yet not always well studied, discussed, or understood. Analysis can be quick and shallow, slower and deeper, narrowly or broadly focused, formal or informal.

In this one-day workshop, we'll engage in exercises and discussions that highlight ways of analyzing
  • Products
  • Technologies
  • Systems
  • Language
  • Test conditions
  • Risk
  • Social groups
  • Problems
  • Strategies
  • Analysis itself!

Learning Outcomes:
  • Participants may develop insights into
  • Sensemaking; how and why we go about analysis
  • Factoring; identify elements and dimensions that might make a difference
  • Modeling; representing complex things with useful simplifications
  • Revealing and managing assumptions
  • Geometric analysis; patterns, groupings, intervals, boundaries, symmetries…
  • Linguistic analysis; structures of what’s there and what’s missing in the ways we speak
  • General Systems Thinking; the role of the observer; aggregation; decomposition
  • Critical thinking: how might we be fooling ourselves? How can we defend against that?


Speakers
avatar for Michael Bolton

Michael Bolton

Consulting Software Tester, DevelopSense
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software... Read More →


Tuesday May 21, 2019 1:30pm - 3:00pm EDT
E-2025 (2nd Floor)

1:30pm EDT

Powerful Observational Techniques For Coaching Teams (Sunny Dhillon)
Abstract:
Starting out as a new agile coach is difficult. Where do you go? How do you start? Learn to leverage a structured approach to coaching that defines a way to prepare and execute coaching activities by starting from Observations and moving on by identifying what behavioral Goals, as coaches, we would like the coachee(s) to achieve.

The only way to improve a situation through coaching is by helping improving the behavior of the people involved, that will allow to establish a sustainable and long lasting change. As coaches, our opinions and unconscious biases can mislead or misdirect those we are coaching. This bias happens when an observer expresses their thoughts and expectations about a situation through tone, word choice, and body language in a way that influences how the people they are observing behave.
Right about now, you’re probably thinking “Well I wouldn’t do that! I’m a professional!” and there is bad news for you. We all do it. Because it’s largely unconscious, we can’t help it. Therefore, it is important that we are aware and careful of this effect. Lets leverage a structure that helps us avoid jumping ahead of ourselves in coaching.

You will uncover innovative and a structured approach to coaching which aims at limiting or negating the impact of any observer bias we might bring to the table whilst improving team performance. Through a structured approach, coaches and scrum masters will be able to better target their efforts and create demonstrable improvement in teams.
Attendees will leave this session with a structured approach to guide their ongoing coaching efforts and share those experiences with others in the organization.
Target Audience: Scrum Masters, Agile Coaches, Executives, Managers and Agile Leaders.

Learning Outcomes:
  1. To be able to explain the Team Coaching framework.
  2. Apply different techniques in observational coaching.
  3. Learn to avoid observer bias in your coaching.
  4.  Learn to apply tools and techniques on building a coaching culture in your organisation.
  5. You will demonstrate on how to create transparency in your coaching.
  6.  Learn to inspect and adapt in your coaching.


Speakers
avatar for sunny dhillon

sunny dhillon

Agile Coach, agile42
Sunny graduated with a Masters in Computer Science in the year 2000. Sunny’s developed software in many different industries including investment banking, retail banking, e-commerce and health care in the two decades since. Major projects included PayPal integration for Best Buy... Read More →



Tuesday May 21, 2019 1:30pm - 3:00pm EDT
E-2023 (2nd Floor)

1:30pm EDT

Run Design Sprints like Google (contined) (Judith Sol-Dyess)
Abstract:
The promise of a Design Sprint is simple — and valuable. In just five days, you can learn whether an idea is worthwhile or not. Imagine the effort, time and money that you could save by using a Product Design Sprint to find out in one week whether a product, feature or process was really going to work for users. Instead of devoting months of production work to a hypothesis, you can test it immediately and move forward with facts.

The Google Design Sprint process was developed by the company's investment arm, Google Ventures, to quickly assess whether an idea was worthy of their funding. Today, we've used the Design Sprint framework to help companies at all stages of the product development process validate their work and build with confidence.

In this Google Design Sprint Workshop, you'll learn the skills to bring your ideas to life and put them in front of users in one workweek. We'll walk you through each step of the Product Design Sprint Process, from brainstorming, to prototyping, to testing on real users, to synthesizing the results, so you can bring a new level of proof to all of your projects.

Learning Outcomes:
  • Apply design thinking concepts to a business problem
  • Rapidly collaborate with a team to find solutions
  • Familiarity with the Google Design Sprint process
  • Ability to participate in or facilitate a Google Design Sprint
  • Techniques for turning business ideas into concrete problem statements
  • Techniques for facilitating various decision activities
  • Lightweight sketching and prototyping
  • Hands-on experience interviewing users
  • Learn to value and embrace “failing fast”

Speakers
avatar for Judith Sol-Dyess

Judith Sol-Dyess

Senior Project Strategist, Table XI
I'm a project strategist who, probably like you, wears many hats: project manager, product manager, scrum master and agile transformation coach for my clients. I really enjoy the work I do, and the people I get to meet along the way. I help teams work better together and deliver value... Read More →



Tuesday May 21, 2019 1:30pm - 3:00pm EDT
E-4025 (4th Floor)

1:30pm EDT

Surviving Legacy Code (continued) (J. B. Rainsberger)

Abstract:
Working with legacy code remains difficult. We feel afraid to change it, but sometimes we have no choice.
Learn key techniques to help you manage your risk. J. B. Rainsberger gives you a safe code base in which to experiment and he guides you through the confusing risk/reward decisions involved in living with legacy code. You will learn and practise several specific, safe techniques that you can start using on your own legacy code once you return to your project.
You should attend this workshop if you have code that seems impossible to change, code that you feel really uncomfortable changing, or you want to avoid creating code like that in the future. J. B.’s advice transcends business domains and programming languages. Moreover, you get to find out how he thinks through the tough choices as well as improve the design with (relative) grace and ease.
After learning a technique, it’s your turn to try it out for yourself. All you need is a working development environment for your favorite programming language and to install git. (Strictly speaking, you don’t even need to do that, but you probably should.) If you get stuck, then J. B. helps you get moving again. If something seems strange, then J. B. helps you make sense of it–or maybe he agrees that it’s strange and you should try something else.

Learning Outcomes:
  • See the central conflict in working with legacy code: I want to add tests to refactor safely, but I need to refactor to add tests at a reasonable cost.
  • Learn how to add tests quickly to existing code using the text-based output that the system already produces.
  • Learn 4 key design techniques that help address the central conflict of legacy code.
  • Learn the core principles of rescuing legacy code: optimize for safety, document everything, embrace imperfection, play the long game, you can't chase all the rabbits.
  • Learn how to maintain focus in the inherently distracting environment of rescuing legacy code.
  • Learn how to work more harmoniously with people in the inherently frustrating and anxiety-inducing atmosphere of legacy systems.
  • Have a few tricks to start using immediately when returning to work in addition to some longer-term plans for improvement.


Speakers
avatar for J. B. Rainsberger

J. B. Rainsberger

Trusted Adviser, jbrains.ca
J. B. Rainsberger helps software companies better satisfy their customers and the businesses they support. Over the years, he has learned to write valuable software, turned himself into a joy to work with, and built a life that he loves. He has traveled the world sharing what he’s... Read More →


Tuesday May 21, 2019 1:30pm - 3:00pm EDT
E-2022 (2nd Floor)

3:30pm EDT

Analysis for Agilists (continued) (Michael Bolton)
Abstract:
  • How do we go about understanding something complex?
  • How do we move from confusion to clarity?
  • What strategies and approaches can we use to identify and reason about things that matter?
  • When we’re dropped into a development or testing situation, how do we make sense of it all?
  • How can we rapidly achieve a deeper understanding of things that we know little or nothing about?
  • How do we anticipate and manage product, project, and business risk?
  • How can we develop skills to make us more powerful analysts, developers, testers, and critics?
Analysis – the study of things and ideas by examining their elements and structures — is a way of developing answers to all of these questions. Analysis is central to development and testing, yet not always well studied, discussed, or understood. Analysis can be quick and shallow, slower and deeper, narrowly or broadly focused, formal or informal.

In this one-day workshop, we'll engage in exercises and discussions that highlight ways of analyzing
  • Products
  • Technologies
  • Systems
  • Language
  • Test conditions
  • Risk
  • Social groups
  • Problems
  • Strategies
  • Analysis itself!

Learning Outcomes:
  • Participants may develop insights into
  • Sensemaking; how and why we go about analysis
  • Factoring; identify elements and dimensions that might make a difference
  • Modeling; representing complex things with useful simplifications
  • Revealing and managing assumptions
  • Geometric analysis; patterns, groupings, intervals, boundaries, symmetries…
  • Linguistic analysis; structures of what’s there and what’s missing in the ways we speak
  • General Systems Thinking; the role of the observer; aggregation; decomposition
  • Critical thinking: how might we be fooling ourselves? How can we defend against that?


Speakers
avatar for Michael Bolton

Michael Bolton

Consulting Software Tester, DevelopSense
Michael Bolton is a consulting software tester and testing teacher who helps people to solve testing problems that they didn’t realize they could solve. He is the co-author (with senior author James Bach) of Rapid Software Testing, a methodology and mindset for testing software... Read More →


Tuesday May 21, 2019 3:30pm - 5:00pm EDT
E-2025 (2nd Floor)

3:30pm EDT

Run Design Sprints like Google (continued) (Judith Sol-Dyess)
Abstract:
The promise of a Design Sprint is simple — and valuable. In just five days, you can learn whether an idea is worthwhile or not. Imagine the effort, time and money that you could save by using a Product Design Sprint to find out in one week whether a product, feature or process was really going to work for users. Instead of devoting months of production work to a hypothesis, you can test it immediately and move forward with facts.

The Google Design Sprint process was developed by the company's investment arm, Google Ventures, to quickly assess whether an idea was worthy of their funding. Today, we've used the Design Sprint framework to help companies at all stages of the product development process validate their work and build with confidence.

In this Google Design Sprint Workshop, you'll learn the skills to bring your ideas to life and put them in front of users in one workweek. We'll walk you through each step of the Product Design Sprint Process, from brainstorming, to prototyping, to testing on real users, to synthesizing the results, so you can bring a new level of proof to all of your projects.

Learning Outcomes:
  • Apply design thinking concepts to a business problem
  • Rapidly collaborate with a team to find solutions
  • Familiarity with the Google Design Sprint process
  • Ability to participate in or facilitate a Google Design Sprint
  • Techniques for turning business ideas into concrete problem statements
  • Techniques for facilitating various decision activities
  • Lightweight sketching and prototyping
  • Hands-on experience interviewing users
  • Learn to value and embrace “failing fast”

Speakers
avatar for Judith Sol-Dyess

Judith Sol-Dyess

Senior Project Strategist, Table XI
I'm a project strategist who, probably like you, wears many hats: project manager, product manager, scrum master and agile transformation coach for my clients. I really enjoy the work I do, and the people I get to meet along the way. I help teams work better together and deliver value... Read More →


Tuesday May 21, 2019 3:30pm - 5:00pm EDT
E-4025 (4th Floor)

3:30pm EDT

Surviving Legacy Code (continued) (J. B. Rainsberger)

Abstract:
Working with legacy code remains difficult. We feel afraid to change it, but sometimes we have no choice.
Learn key techniques to help you manage your risk. J. B. Rainsberger gives you a safe code base in which to experiment and he guides you through the confusing risk/reward decisions involved in living with legacy code. You will learn and practise several specific, safe techniques that you can start using on your own legacy code once you return to your project.
You should attend this workshop if you have code that seems impossible to change, code that you feel really uncomfortable changing, or you want to avoid creating code like that in the future. J. B.’s advice transcends business domains and programming languages. Moreover, you get to find out how he thinks through the tough choices as well as improve the design with (relative) grace and ease.
After learning a technique, it’s your turn to try it out for yourself. All you need is a working development environment for your favorite programming language and to install git. (Strictly speaking, you don’t even need to do that, but you probably should.) If you get stuck, then J. B. helps you get moving again. If something seems strange, then J. B. helps you make sense of it–or maybe he agrees that it’s strange and you should try something else.

Learning Outcomes:
  • See the central conflict in working with legacy code: I want to add tests to refactor safely, but I need to refactor to add tests at a reasonable cost.
  • Learn how to add tests quickly to existing code using the text-based output that the system already produces.
  • Learn 4 key design techniques that help address the central conflict of legacy code.
  • Learn the core principles of rescuing legacy code: optimize for safety, document everything, embrace imperfection, play the long game, you can't chase all the rabbits.
  • Learn how to maintain focus in the inherently distracting environment of rescuing legacy code.
  • Learn how to work more harmoniously with people in the inherently frustrating and anxiety-inducing atmosphere of legacy systems.
  • Have a few tricks to start using immediately when returning to work in addition to some longer-term plans for improvement.


Speakers
avatar for J. B. Rainsberger

J. B. Rainsberger

Trusted Adviser, jbrains.ca
J. B. Rainsberger helps software companies better satisfy their customers and the businesses they support. Over the years, he has learned to write valuable software, turned himself into a joy to work with, and built a life that he loves. He has traveled the world sharing what he’s... Read More →


Tuesday May 21, 2019 3:30pm - 5:00pm EDT
E-2022 (2nd Floor)

3:30pm EDT

Unlocking the potential of cybersecurity as a catalyst for agile transformations (Ryan Webster)
Abstract:
This interactive session will share lessons and experiences in balancing cybersecurity and product development from an ongoing digital product incubator program at BCG. Participants will engage in taking the role of the product owner and experience the challenges in balancing business and security priorities in an agile development environment. In addition, we will dive into our methodology and approach to operationalize cybersecurity across product, architecture, and development efforts in program. Join us for this exciting session as we explore cybersecurity from the product owner perspective.

Learning Outcomes:
  • Provide an introduction and to integrating cybersecurity into building digital products
  • Explore an agile-paced, risk based approach to secure development
  •  Experience rapid prioritization of non-functional and functional features in product development
  • Experience the challenges in balancing cybersecurity features with product feature delivery for a MVP release
  • Share our experiences and learn from each other


Speakers


Tuesday May 21, 2019 3:30pm - 5:00pm EDT
E-2024 (2nd Floor)
 
Wednesday, May 22
 

11:00am EDT

Growing Your Personal Design Heuristics (Rebecca Wirfs-Brock)
Abstract:
How can we get better as software designers? By becoming more aware of our design heuristics and continuing to cultivate and refine them. Heuristics aid in design, guide our use of other heuristics, and even determine our attitude and behavior. For example, as agile software developers we value frequent feedback and decomposing larger design problems into smaller, more manageable chunks that we design and test as we go. We each have our own set of heuristics that we have acquired through reading, practice, and experience.

This session introduces simple ways to record design heuristics and how to share them with others. You can grow as a designer by examining and reflecting on the decisions you make and their impacts, becoming more aware of seemingly minor decisions that were more important than you thought, and putting your own spin on the advice of experts. While we may read others’ design advice—be it patterns or stack overflow replies, the heuristics we’ve personally discovered on our own design journey may be even more important.

Come to this hands-on session to try out practical techniques for distilling your design heuristics (so you can explore and explain them to others); learn ways to identify competing heuristics; evaluate shiny new heuristics you may read or hear about; and grow your ability to explain your heuristics to others.


Learning Outcomes:
  • Understand 3 different types of design heuristics: heuristics that aid in design, determine our attitude, and guide use of other heuristics
  • Learn simple techniques for recording heuristics on the fly (Question-Heuristic-Example Cards, Heuristic Gists)
  • Recognize competing heuristics and how to integrate new heuristics into your existing heuristic toolkit


Speakers
avatar for Rebecca Wirfs-Brock

Rebecca Wirfs-Brock

Wirfs-Brock Associates
I'm best known as the "design geek" who invented Responsibility-Driven Design and the xDriven meme (think TDD, BDD, DDD..). I'm keen about team effectiveness, communicating complex requirements, software quality, agile QA, pragmatic TDD, and patterns and practices for architecting... Read More →


Wednesday May 22, 2019 11:00am - 12:30pm EDT
E-4024 (4th Floor)

11:00am EDT

Listen, sketch and remember! (Nienke Alma)
Abstract:
It’s a wrap! You feel inspired by that great conference you have attended. Tomorrow things are going to be different. You go home with new ideas and full commitment to try out that cool practice the keynote speaker told you about. But when you’re back in your office the day to day business requires your full attention again and soon most conference learnings become hard to remember.

If this sounds familiar to you, this workshop might be interesting. Have you ever tried sketchnoting? Or do you think that only works for real artists? That’s exactly what Nienke Alma thought when she joined a sketchnoting workshop during an open space session three years ago. “This could be fun, but probably I will never be good enough to put this into practice”. She was wrong: soon enough she found out the amazing effect on her conference experience and memory by just changing the way she took notes.
You don’t have to become a visual artist. Sketchnoting isn’t about perfection. It is just a way to activate new parts of your brain that enhances your listening. In this workshop Nienke Alma wants to inspire you by sharing her own sketchnoting experiences and providing tips & tricks. Moreover, she encourages you to try it out. Be prepared to do some actual sketchnoting during the workshop!

Learning Outcomes:
  • Learn how to make sketchnoting valuable for yourself
  •  Experience the difference between sketchnoting and taking regular written notes, especially with respect to the way you remember what you have heard
  • Find out how sketchnoting could be applied in your daily job


Speakers
avatar for Nienke Alma

Nienke Alma

Agile Coach, ING
Nienke Alma is a people oriented Agile enthusiast with 12 years of experience as Agile coach, trainer, Scrum Master, tester and test manager. She currently works as an Agile Coach at ING in the Netherlands.She has special interest in team dynamics. Getting the best out of individuals... Read More →



Wednesday May 22, 2019 11:00am - 12:30pm EDT
E-4025 (4th Floor)

11:00am EDT

When Experts Collide- Exploring the Nuance of Team Integration with Popular Drum Beats (john ryskowski)
Abstract:
When forming a team we look for individuals that possess specific skill sets. To be effective, teams must integrate those skill sets and therein lays the challenge.
Empathy is an important tool in an agile coach’s tool box and the quickest route to empathy is first-hand experience. Wouldn’t it be nice to acquire first-hand experience of the nuances of team skills integration and process the whole event in the duration of a single workshop? Oh, and experience it kinesthetically? Dude!

Playing each part of a drum set is much easier than playing all the parts at the same time and in this session we leverage from that experience. Teams of performers will actually play their part of a drum beat then integrate with other performers playing their parts at the same time. These teams will experience a progression through individual mastery, peer team mastery, integrated team mastery (this is where it gets interesting), integrated team agility, and integrated team stability.

Learning Outcomes:
  • There are two important elements in an agile coach’s toolbox. The first is personal awareness in order to mindfully engage another human or group of humans without emotional attachment. Mastery of this element is a multi-faceted and an ongoing journey. The second element is to bring first-hand experiences to their work, especially if the nuances of that experience have been meaningfully studied and processed.
  • The experiences during this session will be discussed at each phase and more richly processed with the help of assigned observers.
Session Takeaways:
  • Team skills integration is physically contextual, but challenged with emotions
  • Apply a construct that defines steps from individual mastery to integrated team mastery
  • Become highly sensitized to the nuances of team skills integration


Speakers
avatar for john ryskowski

john ryskowski

President, JFR Consulting
Q: What makes all the hardware and software in an Apple store come to life? A: Relevant conversations The problem always boils down to the people, but within those people lies the solution. The solution cannot start without a conversation with the right people in the same room... Read More →



Wednesday May 22, 2019 11:00am - 12:30pm EDT
E-2025 (2nd Floor)
 
Thursday, May 23
 

3:30pm EDT

Being Agile with Architecture Decisions: A Short Workshop on Architecture Decision Records (Ken Power)

Abstract:
Some architecture decisions are more consequential and higher impact than others, and need to be preserved. The right level of architecture documentation supports agility. Architecture Decision Records (ADRs) are a useful, lightweight approach for this. This hands-on session shares experiences with ADRs, giving you a set of tools to be successful in your team.
Some of the decisions made by architects are more consequential and higher impact than others, and need to be preserved. This session:
  • Shares the motivation that led to trying Architecture Decision Records (ADRs) for preserving decisions
  • Shares experiences working with ADRs
  • Draws from experiences with multiple large-scale, global organisations and system architectures
  • Builds on established work with ADRs from other authors and practitioners
  • Presents a summary of experiences using ADRs with teams from around the world
  • Shows examples of ADRs from each product line
  • Shares examples of challenges encountered when adopting and using ADRs
  • Provides participants with hands-on practice of creating and reviewing ADRs

Learning Outcomes:
  • Understand how Architecture Decision Records can support agility
  • Options for structuring and tailoring Architecture Decision Record templates, including some examples of how we have tailored ADRs with different teams
  • Understand the types of decisions for which ADRs are appropriate, and what decisions might be better suited to a different medium
  • Factors to consider for creating, storing, and reviewing ADRs
  • Fostering a culture of valuing ADRs
  • Factors to consider when working with distributed teams in multiple geographies
  • Pointers to other work in the area of ADRs


Speakers
avatar for Ken Power

Ken Power

Software Engineering Leader, https://kenpower.dev/
Ken Power has held multiple positions in large technology organizations. His current responsibilities include leading global, large-scale engineering organization transformations. He has been working with agile and lean methods since 1999. He holds patents in virtualization and network... Read More →


Thursday May 23, 2019 3:30pm - 5:00pm EDT
E-2022 (2nd Floor)
 
Friday, May 24
 

3:30pm EDT

Fast Feedback - The Key to Business Agility (David Grabel)

Abstract:
Software engineers get feedback from their development environment and automated test suites in real-time. They get feedback from QA engineers in a day or less. Errors can be fixed and verified in minutes. On the other hand, feedback from stakeholders outside of technology takes days and the “feedback frenzies” can drag on for weeks or even months. It is time for “the business” to dramatically reduce lead time and deliver value quicker without sacrificing quality. Fast feedback is the key to unlocking business agility.
Agile enables organizations to deliver value to customers faster. It took decades for software developers to reduce their delivery cycles from years to weeks or days. Fast feedback for testing and fixing was a significant driver of this acceleration. Companies should keep this lesson in mind as they bring Agile across the enterprise.
Today, feedback on creative designs, user experience, projects, programs, budgets, and contracts can take weeks, delaying the business outcomes. This workshop will provide methods, tips, and techniques to shorten those cycles to minutes. It starts by showing you how value stream mapping can highlight feedback loops which typically introduce significant delays. This helps to identify opportunities for dramatically faster feedback, allowing people outside of technology to complete stories and deliver value within a sprint. You will also hear how creative teams are learning from and adapting modern software techniques that build feedback into their processes in order to accelerate delivery from business teams.

Learning Outcomes:
  • The value of fast delivery
  • Sources of delay, particularly outside of IT
  • How to create a value stream map and use it to identify opportunities to reduce lead time
  • How to calculate process efficiency
  • How to identify high value and low value feedback
  • How to use experiments to safely eliminate feedback frenzies


Speakers
avatar for David Grabel

David Grabel

Enterprise Agile Coach, Fidelity Investments
David Grabel is an enterprise agile coach consulting at Fidelity Investments bringing Agile to the entire organization. He has introduced Scrum, Kanban, XP, and SAFe at both small and large organizations. His previous clients include Vistaprint, Trizetto, Bose, and PayPal where he... Read More →



Friday May 24, 2019 3:30pm - 5:00pm EDT
E-2024 (2nd Floor)
 
Saturday, May 25
 

9:00am EDT

1st Int Workshop on Agile Transformation (Session I) (Torgeir Dingsøyr, Leonor Barroca)
Abstract:
Many organisations are adopting agile approaches, not only in their IT department, but increasingly across the whole organisation. The process of introducing agile practices in organisations is called an "agile transformation". In a review article published in 2016, Dikert et al. identify a number of challenges in agile transformations, such as resistance to change, lack of investment (training, coaching, lack of physical rearrangement to suit new ways of work), agile being "difficult to implement", challenges with coordination across teams, and that different approaches emerge in multi-team environments. The review focuses on software development organisations although many of the challenges identified are not necessarily specific to software development. As organisations increasingly engage in agile transformation processes, advice today is dominated by consultants and from experience reports. Researchers have suggested to understand agile transformation processes through sociotechnical theory, change management theory and we believe that there are a number of other fields to learn from to understand and improve the outcome of agile transformation processes.

We would like to challenge the scientific community to identify what should be of prime interest for researchers in this area, as there are growing opportunities to study agile transformation as companies increasingly adopt new large-scale agile frameworks. Organisations are learning from agile practice to embrace agility in their ways of working; agile practitioners can also benefit from the wider context of organisations undergoing agile transformations, to understand the wider implications of large-scale transformations and how to sustain them. We will create a workshop to provide an interactive arena for knowledge sharing and exchange of experiences between academics and practitioners.

Schedule:
09:15- The agile transformation at Volvo Cars Lucas Gren
09:35- Agile transformation explained under the lens of management innovation implementation Akim Berkani
09:55- “Don’t throw the baby out with the bath water” - agile transformation from the trenches
Johannes Berglind Söderqvist, Ludvig Lindlöf, Lars Trygg and Rashina Hoda
10:15- Head, Heart and Hands Katie Taylor

Speakers
LB

Leonor Barroca

Senior lecturer, The Open University
avatar for Torgeir Dingsøyr

Torgeir Dingsøyr

chief scientist, SINTEF
Torgeir Dingsøyr has studied teamwork and learning in software development, as well as development methods for large software projects and programs. He is chief scientist at the SINTEF research foundation, which is recognized as one of the leading research environments in the world... Read More →



Saturday May 25, 2019 9:00am - 10:30am EDT
E-2024 (2nd Floor)

9:00am EDT

Large Scale Agile Development (Part I) (Julian Bass)
Abstract:
Agile software development methods are conventionally applied in small, collocated development teams. There is growing interest, from researchers and practitioners, in agile methods applied to large-scale projects with several cooperating teams developing complex systems.
Large-scale agile is now a hot topic in software engineering. Agile frameworks, with all their benefits and challenges are being widely discussed and applied. The IEEE Software special issue on large-scale agile put together by Torgeir Dingsøyr, Davide Falessi and Ken Power is expected to come out in Mar./Apr. 2019.
How to apply agile methods to large projects was identified as the "top burning research question" by practitioners at XP2010. At XP2013 to XP2018, this workshop has addressed research challenges in large-scale agile development and identified topics such as inter-team coordination, large project organization, release planning and architecture and practices to scaling agile methods

Schedule:
9:00 - Opening Julian Bass
9:05 – Keynote Scaling Parallel Organisational Structures: The Spotify Guilds' Story Darja Šmite
9:45 – Research Paper 1: SAFe Adoptions in Finland: A Survey Research Maarit Laanti and Petri Kettunen
10:00 – Research Paper 2: Comparing Scaling Agile Frameworks Based on Underlying Practices Sven Theobald, Anna Schmitt 
10:15 – Research Paper 3: Finnish Large-Scale Agile Transformations: A Survey Study Petri Kettunen, Maarit Laanti, Fabian Fagerholm, Tommi Mikkonen and Tomi Männistö



Speakers
ST

Sven Theobald

Researcher, Fraunhofer IESE
avatar for Julian Bass

Julian Bass

Senior Lecturer, University of Salford
I have developed an inventory of activities and behaviours for product owners in large-scale agile development programmes. Check out the articles on large-scale agile in the Mar./Apr. 2019 issue of IEEE Software.
avatar for Darja Smite

Darja Smite

Professor, Blekinge Institute of Technology
Interested in global software development and scaling agile, passionate about revealing the true impacts of offshoring.



Saturday May 25, 2019 9:00am - 10:30am EDT
E-4025 (4th Floor)

9:00am EDT

Sensemaking in organizations (Part I): How to create a practical Cynefin and sensemaking process (Ken Power, Tony Quinlan)
Abstract:
The Cynefin sensemaking framework has grown in popularity in the agile community in recent years. Used to its full potential, sensemaking and the Cynefin framework are powerful and effective approaches to informing action in complex, dynamic, and uncertain situations. Ken and Tony will introduce a practical, effective approach based on their work applying complexity techniques in large global technology organisations. This workshop, based on years of experience with dozens of sensemaking projects, will teach you the fundamentals of using micronarrative-based sensemaking and the Cynefin framework to foster transformation, resilience and agility.

This session will focus on use of sensemkaing to support transformations. You will learn about sensemaking in organizaitons, the Cynefin framework, how to determine appropriate action in a given context, how to design experiments for navigating complex situations, how to tailor a sensemaking framework for a particular purpose, and how to integrate sensemaking into your organizaiton.

Learning Outcomes:
Learning outcomes from this workshop include:
  • An understanding of the Cynefin framework, or a refresher for those who have already come across it
  •  Understanding of sensemaking and where it is useful and appropriate in organisations
  •  Tips for designing a sensemaking framework
  • Feedback and action process - elements of cadence and timing - how often do we have action-focused workshops
  •  How to integrate sensemaking into the cadence of the organization
  • Ensuring different parts of the organisation are represented in the sensemaking and experiment design
  • Getting people to pay attention to the results and take action informed by those results


Speakers
avatar for Ken Power

Ken Power

Software Engineering Leader, https://kenpower.dev/
Ken Power has held multiple positions in large technology organizations. His current responsibilities include leading global, large-scale engineering organization transformations. He has been working with agile and lean methods since 1999. He holds patents in virtualization and network... Read More →
avatar for Tony Quinlan

Tony Quinlan

CEO & Chief Storyteller, Narrate
Complexity, Cynefin and sense-making. Understanding the cultural landscape and making enough sense to take action. Running workshops for organisations to co-create interventions and strategies for transformation. Using SenseMaker to measure the impact of change programmes.


Saturday May 25, 2019 9:00am - 10:30am EDT
E-2023 (2nd Floor)

11:00am EDT

1st Int Workshop on Agile Transformation (Session II) (Torgeir Dingsøyr, Leonor Barroca)
Abstract:
Many organisations are adopting agile approaches, not only in their IT department, but increasingly across the whole organisation. The process of introducing agile practices in organisations is called an "agile transformation". In a review article published in 2016, Dikert et al. identify a number of challenges in agile transformations, such as resistance to change, lack of investment (training, coaching, lack of physical rearrangement to suit new ways of work), agile being "difficult to implement", challenges with coordination across teams, and that different approaches emerge in multi-team environments. The review focuses on software development organisations although many of the challenges identified are not necessarily specific to software development. As organisations increasingly engage in agile transformation processes, advice today is dominated by consultants and from experience reports. Researchers have suggested to understand agile transformation processes through sociotechnical theory, change management theory and we believe that there are a number of other fields to learn from to understand and improve the outcome of agile transformation processes.

We would like to challenge the scientific community to identify what should be of prime interest for researchers in this area, as there are growing opportunities to study agile transformation as companies increasingly adopt new large-scale agile frameworks. Organisations are learning from agile practice to embrace agility in their ways of working; agile practitioners can also benefit from the wider context of organisations undergoing agile transformations, to understand the wider implications of large-scale transformations and how to sustain them. We will create a workshop to provide an interactive arena for knowledge sharing and exchange of experiences between academics and practitioners.

Schedule:
11:00-Keynote - Tips for Successful Large-scale Agile Transformations Maria Paasivaara
11:30- Discussion: Main research challenges in agile transformations


Speakers
LB

Leonor Barroca

Senior lecturer, The Open University
avatar for Torgeir Dingsøyr

Torgeir Dingsøyr

chief scientist, SINTEF
Torgeir Dingsøyr has studied teamwork and learning in software development, as well as development methods for large software projects and programs. He is chief scientist at the SINTEF research foundation, which is recognized as one of the leading research environments in the world... Read More →


Saturday May 25, 2019 11:00am - 12:30pm EDT
E-2024 (2nd Floor)

11:00am EDT

Large Scale Agile Development (Part II) (Julian Bass)
Abstract:

Agile software development methods are conventionally applied in small, collocated development teams. There is growing interest, from researchers and practitioners, in agile methods applied to large-scale projects with several cooperating teams developing complex systems.
Large-scale agile is now a hot topic in software engineering. Agile frameworks, with all their benefits and challenges are being widely discussed and applied. The IEEE Software special issue on large-scale agile put together by Torgeir Dingsøyr, Davide Falessi and Ken Power is expected to come out in Mar./Apr. 2019.
How to apply agile methods to large projects was identified as the "top burning research question" by practitioners at XP2010. At XP2013 to XP2018, this workshop has addressed research challenges in large-scale agile development and identified topics such as inter-team coordination, large project organization, release planning and architecture and practices to scaling agile methods

Schedule:
11:00 – Research Paper 4: Changes Over Time in a Planned Inter-Team Coordination Routine Tomas Gustavsson
11:15 – Research Paper 5: Technical-, Social- and Process Debt in Large-Scale Agile: an exploratory case-study Antonio Martini, Viktoria Stray and Nils Brede Moe
11:30 – Research Trends/Priorities Interactive Discussion Session


Speakers
avatar for Viktoria Stray

Viktoria Stray

Associate Professor, Department of Informatics, University of Oslo
Associate Professor in Software Engineering (University of Oslo), Research Scientist (SINTEF Digital). MSc in Computer Science (Norwegian University of Science and Technology and University of California, Santa Barbara), PhD (University of Oslo and University of New South Wales... Read More →
avatar for Nils Brede Moe

Nils Brede Moe

Research Manager, SINTEF
I work with software process improvement, agile software develop- ment and global software development as a senior scientist at SINTEF Digital. My research interests are related to organizational, socio-technical, and global/distributed aspects. I wrote my thesis for the degree of... Read More →
avatar for Julian Bass

Julian Bass

Senior Lecturer, University of Salford
I have developed an inventory of activities and behaviours for product owners in large-scale agile development programmes. Check out the articles on large-scale agile in the Mar./Apr. 2019 issue of IEEE Software.



Saturday May 25, 2019 11:00am - 12:30pm EDT
E-4025 (4th Floor)

11:00am EDT

Sensemaking in organizations (Part II): How to create a practical Cynefin and sensemaking process (Ken Power, Tony Quinlan)
Abstract:
The Cynefin sensemaking framework has grown in popularity in the agile community in recent years. Used to its full potential, sensemaking and the Cynefin framework are powerful and effective approaches to informing action in complex, dynamic, and uncertain situations. Ken and Tony will introduce a practical, effective approach based on their work applying complexity techniques in large global technology organisations. This workshop, based on years of experience with dozens of sensemaking projects, will teach you the fundamentals of using micronarrative-based sensemaking and the Cynefin framework to foster transformation, resilience and agility.

This session will focus on use of sensemkaing to support transformations. You will learn about sensemaking in organizaitons, the Cynefin framework, how to determine appropriate action in a given context, how to design experiments for navigating complex situations, how to tailor a sensemaking framework for a particular purpose, and how to integrate sensemaking into your organizaiton.

Learning Outcomes:
Learning outcomes from this workshop include:
  • An understanding of the Cynefin framework, or a refresher for those who have already come across it
  •  Understanding of sensemaking and where it is useful and appropriate in organisations
  •  Tips for designing a sensemaking framework
  • Feedback and action process - elements of cadence and timing - how often do we have action-focused workshops
  •  How to integrate sensemaking into the cadence of the organization
  • Ensuring different parts of the organisation are represented in the sensemaking and experiment design
  • Getting people to pay attention to the results and take action informed by those results


Speakers
avatar for Ken Power

Ken Power

Software Engineering Leader, https://kenpower.dev/
Ken Power has held multiple positions in large technology organizations. His current responsibilities include leading global, large-scale engineering organization transformations. He has been working with agile and lean methods since 1999. He holds patents in virtualization and network... Read More →
avatar for Tony Quinlan

Tony Quinlan

CEO & Chief Storyteller, Narrate
Complexity, Cynefin and sense-making. Understanding the cultural landscape and making enough sense to take action. Running workshops for organisations to co-create interventions and strategies for transformation. Using SenseMaker to measure the impact of change programmes.


Saturday May 25, 2019 11:00am - 12:30pm EDT
E-2023 (2nd Floor)

1:30pm EDT

A-teams’19, 2nd Int Workshop on Autonomous Agile Teams (Part I) (Viktoria Stray, Nils Brede Moe)
  • 13:30 - Welcome - program and motivation - Nils Brede Moe and Viktoria Stray (organisers, no abstract)
  • Keynote : What makes your team self-organizing? Rashina Hoda
  • Spotify Tailoring for Promoting Effectiveness in Cross-Functional Autonomous Squads Julian Bass
  • The Influence of Culture and Structure on Autonomous Teams in Established Companies Simone Spiegler
  • Voices From the Teams - Impacts on Autonomy in Large-Scale Agile Software Development Settings Tomas Gustavsson
Abstract:
To succeed in complex environments like large-scale and heterogeneous teams handling innovation development and support, organizations have to find ways to support and regulate teams' autonomy according to the environmental demands and limitations. However, autonomous teams cannot be created simply by tearing down organizational hierarchies, or by instituting one-person-one-vote decision-making processes. Challenges implementing autonomous teams are communication problems, social loafing and group thinking. Further, the agile team is becoming more diverse with the introduction of DevOps and BizDevOps. While heterogenous agile teams create solutions with the highest value, the lowest value is also produced by such teams. Additionally, in large-scale there is a conflict between the need for alignment and team autonomy. Furthermore, they have to take into consideration the degree of change and uncertainty, and that there is no one-size-fits-all autonomy approach. The process of forming and implementing agile teams with high autonomy, as well as the effective functioning of such teams, are not yet adequately addressed and understood in the context of software development organizations.

Thus, there is a need for new knowledge on how organizations shall organize for the right level of team autonomy, and utilize autonomous agile teams, in order to attain better performance, productivity, innovation and value creation, and thus increase competitiveness. We seek to facilitate knowledge sharing about the current practice of autonomous software teams in agile development and also deepen the knowledge of principles of how these teams can succeed. We seek contributions in the form of position papers with experience reports, empirical studies, reviews of relevant literature, and papers arguing for research needs or describing planned research.

The goal of the workshop is to facilitate knowledge sharing about the current practice of autonomous agile teams and deepen the knowledge about practices and strategies that enable autonomous teams. There will be an invited keynote, short talks (lightning talks) followed by a highly interactive session using workshop techniques.

We invite researchers and practitioners to this second international workshop to discuss how to succeed with teamwork in agile projects. One emerging question is “How can organizations give cross-functional agile teams the authority to set directions for new products so that organizations can deliver software more rapidly"?


Speakers
avatar for Tomas Gustavsson

Tomas Gustavsson

PhD Student, Karlstads universitet
Started out as an IT consultant in 1996 and have since worked as project manager, lecturer, author, publisher and CEO but decided to wholeheartedly work within academia and began as PhD student in the fall semester of 2016. I focus on large-scale agile development, specificially within... Read More →
avatar for Simone V. Spiegler

Simone V. Spiegler

PhD Student, University of Stuttgart & Robert Bosch Automotive Steering Gmbh
Agile Coach and researcher on the lateral leadership role of a Scrum Master in established companies. My background in Social Psychology, Organizational Studies and Software Technology help me to integrate divers perspectives on the Scrum Master role.So far, I have worked for 3 different... Read More →
avatar for Rashina Hoda

Rashina Hoda

Senior Lecturer, University of Auckland
I study human aspects of software engineering, agile software development and project management, and serious games design for the 21st century classrooms. More info at www.rashina.com
avatar for Viktoria Stray

Viktoria Stray

Associate Professor, Department of Informatics, University of Oslo
Associate Professor in Software Engineering (University of Oslo), Research Scientist (SINTEF Digital). MSc in Computer Science (Norwegian University of Science and Technology and University of California, Santa Barbara), PhD (University of Oslo and University of New South Wales... Read More →
avatar for Nils Brede Moe

Nils Brede Moe

Research Manager, SINTEF
I work with software process improvement, agile software develop- ment and global software development as a senior scientist at SINTEF Digital. My research interests are related to organizational, socio-technical, and global/distributed aspects. I wrote my thesis for the degree of... Read More →
avatar for Julian Bass

Julian Bass

Senior Lecturer, University of Salford
I have developed an inventory of activities and behaviours for product owners in large-scale agile development programmes. Check out the articles on large-scale agile in the Mar./Apr. 2019 issue of IEEE Software.



Saturday May 25, 2019 1:30pm - 3:00pm EDT
E-2024 (2nd Floor)

1:30pm EDT

Domain-Driven Design with User Story Mapping (Part I) (Dion Stewart)
Abstract:

In his book User Story Mapping: Discover the Whole Story, Build the Right Product, Jeff Patton explains how to write better stories by creating story maps. Story maps foster better collaboration within and across teams, leading to shared understanding about the product.

Dion Stewart learned story mapping from Jeff Patton and David Hussman six years ago. After using story mapping on a product as a developer, he was hooked. As a coach, Dion has taught story mapping to dozens of organizations. Along the way, story mapping has evolved.

Dion explores how teams are using annotated journeys with story maps to drive modeling discussions around testing, ensuring outcomes and key results can be met, and how annotated journeys have most recently been used in applying domain driven design.

Topics include:
• Story mapping basics
• User journeys
• Annotations for testing
• Ensuring outcomes/key results
• Using user journeys to drive collaboration around DDD concepts (ubiquitous language, defining the domain, evolving the model, and establishing context)
• Defining bounded contexts
• Identifying core and extended data attributes
• Understanding the rate at which data changes over time

Learning Outcomes:
  • How to link application architecture to user experience design
  • Story Mapping (basics and newer, advanced concepts)
  • Domain-Driven Design Concepts (Bounded Contexts, Aggregates, Entities, Domain Events, Commands)
  • Collaboration Techniques
  • How to Build Shared Understanding
  • Cloud/Distributed Systems Architecture


Speakers
DS

Dion Stewart

Consultant/Founder, Dojo and Co


Saturday May 25, 2019 1:30pm - 3:00pm EDT
E-4025 (4th Floor)

1:30pm EDT

Sensemaking in organizations (Part III): How to create a practical Cynefin and sensemaking process (Ken Power, Tony Quinlan)
Abstract:
The Cynefin sensemaking framework has grown in popularity in the agile community in recent years. Used to its full potential, sensemaking and the Cynefin framework are powerful and effective approaches to informing action in complex, dynamic, and uncertain situations. Ken and Tony will introduce a practical, effective approach based on their work applying complexity techniques in large global technology organisations. This workshop, based on years of experience with dozens of sensemaking projects, will teach you the fundamentals of using micronarrative-based sensemaking and the Cynefin framework to foster transformation, resilience and agility.

This session will focus on use of sensemkaing to support transformations. You will learn about sensemaking in organizaitons, the Cynefin framework, how to determine appropriate action in a given context, how to design experiments for navigating complex situations, how to tailor a sensemaking framework for a particular purpose, and how to integrate sensemaking into your organizaiton.

Learning Outcomes:
Learning outcomes from this workshop include:
  • An understanding of the Cynefin framework, or a refresher for those who have already come across it
  •  Understanding of sensemaking and where it is useful and appropriate in organisations
  •  Tips for designing a sensemaking framework
  • Feedback and action process - elements of cadence and timing - how often do we have action-focused workshops
  •  How to integrate sensemaking into the cadence of the organization
  • Ensuring different parts of the organisation are represented in the sensemaking and experiment design
  • Getting people to pay attention to the results and take action informed by those results


Speakers
avatar for Ken Power

Ken Power

Software Engineering Leader, https://kenpower.dev/
Ken Power has held multiple positions in large technology organizations. His current responsibilities include leading global, large-scale engineering organization transformations. He has been working with agile and lean methods since 1999. He holds patents in virtualization and network... Read More →
avatar for Tony Quinlan

Tony Quinlan

CEO & Chief Storyteller, Narrate
Complexity, Cynefin and sense-making. Understanding the cultural landscape and making enough sense to take action. Running workshops for organisations to co-create interventions and strategies for transformation. Using SenseMaker to measure the impact of change programmes.


Saturday May 25, 2019 1:30pm - 3:00pm EDT
E-2023 (2nd Floor)

1:30pm EDT

Threat Modelling (Part I) - Build security into your project from the ground up. (Kelsey Haaster, Robin Doherty)
Abstract:
When a group of stakeholders and team members come together to plan a new product or feature, they often focus on identifying stories that deliver end user value through solving a business problem, delighting the customer or disrupting a competitor. While these are critical stories, they are not the whole picture.

Every product has non-functional or cross-functional stories which must be played.
Security stories are an important part of these but are often not considered at all. When they are considered, they are often an afterthought or are assumed to be part of the project infrastructure. Trying to bolt on security as an afterthought in this way is a mistake that can lead to disaster at one extreme, and compromises to reduce product usability, or don't support good end-user security practices at the other.
The challenge, of course, is that from the stakeholder perspective, security is not seen as a priority. This workshop is for software delivery teams who want to learn how to change this perspective and work with their stakeholders to help them to understand more about the importance of security. The goal is to help technical and non-technical stakeholders understand security and why it should be given priority and built into their product from the ground up. We show participants how to facilitate a structured meeting or workshop with their stakeholders where they use a simplified threat modelling technique to identify risks.

The outcome is the identification of user stories (or evil user stories) which when played will mitigate identified risks.

Learning Outcomes:
  • How to facilitate a threat modelling workshop.
  • How to identify the most important security risks, especially the not-so-obvious ones.
  • How to identify mitigations for security risks and turn them into playable user stories.


Speakers
avatar for Robin Doherty

Robin Doherty

Security Lead, ThoughtWorks


Saturday May 25, 2019 1:30pm - 3:00pm EDT
E-2025 (2nd Floor)

3:30pm EDT

A-teams’19, 2nd Int Workshop on Autonomous Agile Teams (Part II) (Viktoria Stray, Nils Brede Moe)
  • Exploring the challenges of integrating data science roles in agile autonomous teams Ivar Hukkelberg
  • Agile autonomous teams in complex organizations Marius Mikalsen
  • Earn Your Wings: A Novel Approach to Deployment Governance Yvan Petit
  • Autonomous agile teams: Future directions for research Nils Brede Moe and Viktoria Stray
  • 16:50 - 17:00 Closing Nils Brede Moe and Viktoria Stray

Abstract:
To succeed in complex environments like large-scale and heterogeneous teams handling innovation development and support, organizations have to find ways to support and regulate teams' autonomy according to the environmental demands and limitations. However, autonomous teams cannot be created simply by tearing down organizational hierarchies, or by instituting one-person-one-vote decision-making processes. Challenges implementing autonomous teams are communication problems, social loafing and group thinking. Further, the agile team is becoming more diverse with the introduction of DevOps and BizDevOps. While heterogenous agile teams create solutions with the highest value, the lowest value is also produced by such teams. Additionally, in large-scale there is a conflict between the need for alignment and team autonomy. Furthermore, they have to take into consideration the degree of change and uncertainty, and that there is no one-size-fits-all autonomy approach. The process of forming and implementing agile teams with high autonomy, as well as the effective functioning of such teams, are not yet adequately addressed and understood in the context of software development organizations.

Thus, there is a need for new knowledge on how organizations shall organize for the right level of team autonomy, and utilize autonomous agile teams, in order to attain better performance, productivity, innovation and value creation, and thus increase competitiveness. We seek to facilitate knowledge sharing about the current practice of autonomous software teams in agile development and also deepen the knowledge of principles of how these teams can succeed. We seek contributions in the form of position papers with experience reports, empirical studies, reviews of relevant literature, and papers arguing for research needs or describing planned research.

The goal of the workshop is to facilitate knowledge sharing about the current practice of autonomous agile teams and deepen the knowledge about practices and strategies that enable autonomous teams. There will be an invited keynote, short talks (lightning talks) followed by a highly interactive session using workshop techniques.

We invite researchers and practitioners to this second international workshop to discuss how to succeed with teamwork in agile projects. One emerging question is “How can organizations give cross-functional agile teams the authority to set directions for new products so that organizations can deliver software more rapidly"?


Speakers
avatar for Nils Brede Moe

Nils Brede Moe

Research Manager, SINTEF
I work with software process improvement, agile software develop- ment and global software development as a senior scientist at SINTEF Digital. My research interests are related to organizational, socio-technical, and global/distributed aspects. I wrote my thesis for the degree of... Read More →
avatar for Viktoria Stray

Viktoria Stray

Associate Professor, Department of Informatics, University of Oslo
Associate Professor in Software Engineering (University of Oslo), Research Scientist (SINTEF Digital). MSc in Computer Science (Norwegian University of Science and Technology and University of California, Santa Barbara), PhD (University of Oslo and University of New South Wales... Read More →


Saturday May 25, 2019 3:30pm - 5:00pm EDT
E-2024 (2nd Floor)

3:30pm EDT

Domain-Driven Design with User Story Mapping (Part II) (Dion Stewart)
Abstract:

In his book User Story Mapping: Discover the Whole Story, Build the Right Product, Jeff Patton explains how to write better stories by creating story maps. Story maps foster better collaboration within and across teams, leading to shared understanding about the product.

Dion Stewart learned story mapping from Jeff Patton and David Hussman six years ago. After using story mapping on a product as a developer, he was hooked. As a coach, Dion has taught story mapping to dozens of organizations. Along the way, story mapping has evolved.

Dion explores how teams are using annotated journeys with story maps to drive modeling discussions around testing, ensuring outcomes and key results can be met, and how annotated journeys have most recently been used in applying domain driven design.

Topics include:
• Story mapping basics
• User journeys
• Annotations for testing
• Ensuring outcomes/key results
• Using user journeys to drive collaboration around DDD concepts (ubiquitous language, defining the domain, evolving the model, and establishing context)
• Defining bounded contexts
• Identifying core and extended data attributes
• Understanding the rate at which data changes over time

Learning Outcomes:
  • How to link application architecture to user experience design
  • Story Mapping (basics and newer, advanced concepts)
  • Domain-Driven Design Concepts (Bounded Contexts, Aggregates, Entities, Domain Events, Commands)
  • Collaboration Techniques
  • How to Build Shared Understanding
  • Cloud/Distributed Systems Architecture


Speakers
DS

Dion Stewart

Consultant/Founder, Dojo and Co


Saturday May 25, 2019 3:30pm - 5:00pm EDT
E-4025 (4th Floor)

3:30pm EDT

Sensemaking in organizations (Part IV): How to create a practical Cynefin and sensemaking process (Ken Power, Tony Quinlan)
Abstract:
The Cynefin sensemaking framework has grown in popularity in the agile community in recent years. Used to its full potential, sensemaking and the Cynefin framework are powerful and effective approaches to informing action in complex, dynamic, and uncertain situations. Ken and Tony will introduce a practical, effective approach based on their work applying complexity techniques in large global technology organisations. This workshop, based on years of experience with dozens of sensemaking projects, will teach you the fundamentals of using micronarrative-based sensemaking and the Cynefin framework to foster transformation, resilience and agility.

This session will focus on use of sensemkaing to support transformations. You will learn about sensemaking in organizaitons, the Cynefin framework, how to determine appropriate action in a given context, how to design experiments for navigating complex situations, how to tailor a sensemaking framework for a particular purpose, and how to integrate sensemaking into your organizaiton.

Learning Outcomes:
Learning outcomes from this workshop include:
  • An understanding of the Cynefin framework, or a refresher for those who have already come across it
  •  Understanding of sensemaking and where it is useful and appropriate in organisations
  •  Tips for designing a sensemaking framework
  • Feedback and action process - elements of cadence and timing - how often do we have action-focused workshops
  •  How to integrate sensemaking into the cadence of the organization
  • Ensuring different parts of the organisation are represented in the sensemaking and experiment design
  • Getting people to pay attention to the results and take action informed by those results


Speakers
avatar for Ken Power

Ken Power

Software Engineering Leader, https://kenpower.dev/
Ken Power has held multiple positions in large technology organizations. His current responsibilities include leading global, large-scale engineering organization transformations. He has been working with agile and lean methods since 1999. He holds patents in virtualization and network... Read More →
avatar for Tony Quinlan

Tony Quinlan

CEO & Chief Storyteller, Narrate
Complexity, Cynefin and sense-making. Understanding the cultural landscape and making enough sense to take action. Running workshops for organisations to co-create interventions and strategies for transformation. Using SenseMaker to measure the impact of change programmes.


Saturday May 25, 2019 3:30pm - 5:00pm EDT
E-2023 (2nd Floor)

3:30pm EDT

Threat Modelling (Part II) - Build security into your project from the ground up. (Kelsey Haaster, Robin Doherty)
Abstract:
When a group of stakeholders and team members come together to plan a new product or feature, they often focus on identifying stories that deliver end user value through solving a business problem, delighting the customer or disrupting a competitor. While these are critical stories, they are not the whole picture.

Every product has non-functional or cross-functional stories which must be played.
Security stories are an important part of these but are often not considered at all. When they are considered, they are often an afterthought or are assumed to be part of the project infrastructure. Trying to bolt on security as an afterthought in this way is a mistake that can lead to disaster at one extreme, and compromises to reduce product usability, or don't support good end-user security practices at the other.
The challenge, of course, is that from the stakeholder perspective, security is not seen as a priority. This workshop is for software delivery teams who want to learn how to change this perspective and work with their stakeholders to help them to understand more about the importance of security. The goal is to help technical and non-technical stakeholders understand security and why it should be given priority and built into their product from the ground up. We show participants how to facilitate a structured meeting or workshop with their stakeholders where they use a simplified threat modelling technique to identify risks.

The outcome is the identification of user stories (or evil user stories) which when played will mitigate identified risks.

Learning Outcomes:
  • How to facilitate a threat modelling workshop.
  • How to identify the most important security risks, especially the not-so-obvious ones.
  • How to identify mitigations for security risks and turn them into playable user stories.


Speakers
avatar for Robin Doherty

Robin Doherty

Security Lead, ThoughtWorks


Saturday May 25, 2019 3:30pm - 5:00pm EDT
E-2025 (2nd Floor)
 
Filter sessions
Apply filters to sessions.