schedule Sep 23rd 01:00 - 01:45 PM place Room 6 people 10 Interested

People don't like being told what to do, especially knowledge workers. Yet in many work settings we give feedback that is directive in nature. What would it be like to receive feedback that, instead of making us ashamed of our failures, helped us to learn and grow? What would it be like to give feedback that enabled deep and sustained learning and growth in another person, while still being perfectly honest?

During this talk you will learn about Developmental Feedback, which enables the giver of the feedback to be clear and speak truth, and enables the receiver of the feedback to absorb it without defensiveness, and with a sense of invitation to learn and grow. You will learn about a variety of feedback types, how to have a "shared sensemaking conversation," what Impact Feedback and "The Story I Tell Myself" feedback actually are, and review sample dialogues. We will explore the conditions necessary for effective developmental feedback conversations, such as psychological safety and timeliness. You will emerge with a practical tool you can use with anyone (not just at work) to speak your truth while respecting the other person’s humanity, leading to lasting change and deeper relationships.

 
 

Outline/Structure of the Talk

Timing

Content

0-2 min

Introduce myself, introduce the topic, present learning objectives

3-4 min

Explain four of the most common types of feedback and make a clear distinction between three of them and the one we will focus on today, Developmental Feedback

5-6 min

Solicit definitions of health and unhealthy feedback from the audience; provide any definitions that do not emerge from this

7-10 min

Define psychological safety. Call out the aspects of psychological safety that are most relevant to the context of a Developmental Feedback conversation

11-15 min

Define a shared sensemaking conversation, using the animated slides. Explain a bit about the “illusion of understanding” cognitive bias, that leads us to always believe that the story we are telling ourselves is the “true story.”

16-19 min

Define “growth edge” and emphasize that developmental feedback needs to work at a person’s growth edge. (if a person is in the Panic Zone, Developmental Feedback will not really work)

20-24 min

Refer back to the concepts covered earlier in both unhealthy versus healthy feedback, and psychological safety, and explain that it is important to consider the MEDIUM of providing developmental feedback. Talk about the nuances of the tradeoff between timeliness and being face to face.

25-28 min

Explain the principles supporting developmental feedback

29-34 min

Explain Impact Feedback, using the sample dialogs on the slides

35-39 min

Explain “The Story I Tell Myself” feedback using the sample dialogs on the slides

40-41 min

Explain that it is possible to combine these two types of feedback, once you have mastered each separately. Explain that the GIVER of this type of feedback has to do a lot of thinking before offering the feedback; this isn’t easy, it requires practice, but it is a skill that can be learned.

42-43 min

Summarize the key differences between typical, common feedback and Developmental Feedback, as listed on Slide 22.

44-45 min

Brief Q&A

Learning Outcome

  • List the common types of feedback
  • Describe the difference between healthy and unhealthy feedback
  • Explain psychological safety and why it matters
  • Define developmental feedback
  • List the principles behind giving developmental feedback
  • Explain the concept of shared sensemaking
  • Explain “Impact Feedback” and “The Story I Tell Myself” feedback

Target Audience

Those willing to explore the deeper human side of fast feedback loops

Prerequisites for Attendees

No prerequisites.

schedule Submitted 4 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • 45 Mins
    Talk
    Beginner

    Have you tidied up your personal life with Marie Kondo and are now wondering how to achieve the same effect in your work life? Do you have the feeling that the most valuable product backlog items (PBIs) are getting lost under a mountain of old stories, bugs, and tasks? Maybe you know a change is needed, but feel completely overwhelmed about where to start? If so, join us to learn how to make your product better through the life changing magic of tidying up your backlog.

    We’ll start by exploring the costs of a large, cluttered product backlog and share a short quiz you can use to gauge the current state of your own backlog. Next, we’ll cover how we’ve adapted the KonMari method and introduce five easy steps you can take to get started in your tidying process. We'll share real-life examples along the way, calling out potential pitfalls to avoid (don’t become a storage expert!), and illustrating how story mapping may be the magical backlog equivalent to Kondo’s “vertical folding” technique. By the end of the session, you’ll know the specific next steps to take so that you too can realize the many benefits of a tidied-up product backlog: improved visibility, increased self-organization, and easier decision-making.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Complexity is the Enemy! How Agile Practices Allow Us to Operate in a VUCA World

    45 Mins
    Talk
    Intermediate

    One of the key advantages of Agile over plan-driven approaches is that an Agile mindset acknowledges our ever-diminishing ability to usefully predict the future and focuses our efforts on managing change instead of trying to suppress it. This “new reality” has become pervasive enough to drive its own buzz word – VUCA, which stands for Volatility, Uncertainty, Complexity, Ambiguity. But beyond the hype lies a truth that Agile leaders need to understand and embrace – that certain problems really do respond differently to our attempts to manage and solve them. Why does this matter? Because problem contexts that defy straightforward cause-and-effect expectations significantly impact productivity while simultaneously presenting much higher risks to success. Even worse, applying leadership approaches that aren’t matched to the problem context dramatically increases the danger of catastrophic failure.

    In this session, we’ll examine how the Cynefin framework helps us make sense of what kinds of problems we’re dealing with and how we should approach them. We will then look at ten ways in which Agile frameworks, approaches and technical practices help us manage or even reduce complexity and one where they fall short. You will walk away with a deeper understanding of how - and why - the things we do as agilists increase stability and reduce risks for our teams.

  • Liked John Hughes
    keyboard_arrow_down

    John Hughes / Tara Lemieux - Value-driven CMMI: An Agile Approach to CMMI for Agile Companies

    45 Mins
    Talk
    Beginner

    CMMI and agile haven't shared many beers at the bar over the years. But there is no reason they shouldn’t be best of friends. They both long for continuous improvement, creating learning organizations that strive to reduce risk and increase quality. I believe that a major cause of dissonance is the lack of perceived value in the way the CMMI models have been applied and appraisals performed in the past.

    So, what would it look like to implement CMMI and prepare for an appraisal focusing all of our effort into creating value and removing waste, instead of adding it? That was the question we tackled this past year and are seeing a completely different practice and outcome given our approach, including enthusiasm and appreciation from the project teams for this approach as opposed to the more typical dread.

    Participants in this presentation will hear from both a CMMI Lead Appraiser and an agilest who lead this value-driven approach to CMMI. They will learn how agile mindset, practices, and tools can be used to apply the CMMI model to our delivery, with intentional focus on creating an ever-maturing practice that reduces risk and increases quality. Participants will also hear how agile was used in the appraisal preparation, enabling continuous improvement across the organization and even reducing the amount of time and effort needed for the SCAMPI A appraisal.

  • Liked Mindy Bohannon
    keyboard_arrow_down

    Mindy Bohannon - I’m a BA Girl in an Agile World

    Mindy Bohannon
    Mindy Bohannon
    Agile Business Analyst
    Excella
    schedule 4 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Have you ever worked with a Business Analyst (BA)? Is what a BA does on an agile project much different from what is done on a waterfall project? All analysts bring excellent communication, collaboration, and trust to their work on project teams. During this session we’ll review the roles a BA can play, a BA's responsibility on the development team, and the skills a good BA possesses. For fun, lets also talk about why an Analyst is part of the 3 Amigos and the complexity of communication channels. Generally speaking, let’s discuss how BAs participate in an agile project’s success and I’ll share some stories about my experience going from waterfall to agile, how I’ve interacted with the PO, and important things I think an Analyst should be involved in.

  • Liked Katrina L. C. Tanner
    keyboard_arrow_down

    Katrina L. C. Tanner - Journey from Analyst to Product Owner to Scrum Master in less than a year

    Katrina L. C. Tanner
    Katrina L. C. Tanner
    Scrum Master
    Cvent
    schedule 4 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    Not many people can say they have performed as an Analyst, Product Owner, and Scrum Master, much less in the same year, and sometimes at the same time.That has been my journey throughout 2018 and into 2019 thus far, as I made intentional decisions in pursuing my next best step, exploring where I really fit, and experiencing quite a few surprises along the way.

    As a CSM and CSPO, I navigated each role taking what I learned in the classroom and implementing it as a practitioner. Being very team AND operations oriented, I have always thrived when one of these were included in my job description. 3 companies, 3 roles, and 2 organizational restructures later, I have found a career that involves both. I learned what works and doesn't work for me and my teams, as well as, what I like and dislike compared to my strengths and weaknesses, especially among changes in organizational needs and structure.

    This short and sweet talk will be an overview of my journey and leave attendees with characteristics of each role to help them decide where they might fit in this agile world and tips on how to talk to your boss about your next step.

  • 45 Mins
    Workshop/Game
    Beginner

    How do you get people to agree on priorities when they may have different objectives? You may be facing an issue now where stakeholders are pushing against each other in order to get their work done first. What would happen if we could create an open dialog among stakeholders and have them understand different perspectives and focus on the goals of the greater good instead of just their own? Let’s face it, proper prioritization is the difference between writing code and developing valuable solutions.

    In this simulation style workshop, you’ll learn practical methods for bringing stakeholders together and openly discuss their different priorities to agree on what’s most important overall. You will see first hand how a combining group discussion with proven prioritization methods such as Weighted-Shortest Job First and (WSJF) and Must Have, Should Have, Could Have and Won’t Have (MoSCoW) work.

  • Liked Nicole Spence-Goon
    keyboard_arrow_down

    Nicole Spence-Goon - Peaks or Valleys? The power of Scaling Agility in the alphabet soup of Government agencies

    Nicole Spence-Goon
    Nicole Spence-Goon
    Agile Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Do you feel like Agile Scaling has become a goal rather than the means to an end for your organization? To determine where you stand on the Scaling spectrum, ask yourself a few soul-searching questions: Why do we need to scale? Is this the right time for us to scale? If you’ve checked these boxes, you may wonder “where do I go from here?”

    This talk will focus on 3 areas that emerged as common themes throughout my experience working on government Agile Scaling projects and ultimately influenced the trajectory of each agency's scaling journey:

    • Communicate vision consistently
    • Focus on your people genuinely
    • Create your own path intentionally

    I've seen successes and some struggles with Agile Scaling efforts in government agencies. Regardless of the agency acronym or the frameworks used, these key elements shaped their scaling outcomes.

  • Liked JeffreyMFarley
    keyboard_arrow_down

    JeffreyMFarley - Bring a Scarecrow: Harnessing the Wisdom of Crowds

    JeffreyMFarley
    JeffreyMFarley
    Solution Architect
    STSI Inc.
    schedule 4 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    Many times, meetings are called to figure out what to do.

    Many times, these meetings fail to do just that

    On my current project, we use "scarecrows" to make sure that we focus on getting a solution and getting everyone's input

  • Liked Zack Ayers
    keyboard_arrow_down

    Zack Ayers / Joshua Cohen - Andon Cords in Development Teams: Our Experience of Driving Continuous Learning through a Culture of Experimentation

    45 Mins
    Talk
    Beginner

    Summary

    In this session, you’ll learn about one team’s struggle to improve collaboration and how they sought to shorten cycle time by carefully crafting an experiment with an Andon Cord. The Andon Cord is a Toyota innovation designed to empower front-line employees to recognize issues, initiate a stoppage of work, and work together as a team to quickly identify a path forward. The emergency cable strung above assembly lines became a symbol of the Toyota Way, and has widely been copied throughout the auto industry and beyond.

    You’ll be introduced to metrics that show a surprising correlation between collaboration through Andon Cord pulls and Cycle Time!

  • Liked Ben Morris
    keyboard_arrow_down

    Ben Morris - Agile the Hard Way - Lessons from a Government Project

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 4 months ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    "Agile OSS" jet on the ground, with an arrow leading to "the cloud"

    The talk walks through lessons learned from a specific government project, jumping head-first into agile, open source, and (oh dear) the cloud. In the jet plane metaphor, it's not about the theory of why a plane should fly (as a physicist), but about the big and little forces that will act on it in practice (as a test pilot).

  • Liked Dave Witkin
    keyboard_arrow_down

    Dave Witkin - Go Big Without Blowing It: How Does Scrum@Scale Help?

    Dave Witkin
    Dave Witkin
    Principal
    Packaged Agile
    schedule 4 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Do you work on programs requiring collaboration of 30 people or more? Have you heard of Scrum@Scale? While many people have heard of SAFe, far fewer are familiar with Scrum@Scale. Did you know Scrum@Scale was built by Jeff Sutherland, the co-creator of Scrum? And that the very first scaled Scrum project began in 1983?

    Come learn about Scrum@Scale, where it is being used, and why it may be a better fit for your organization than other scaling methodologies. I am both a SAFe and Scrum@Scale practitioner and trainer, and will provide a balanced comparison with pros / cons.

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Undercover Scrum Master

    Dane Weber
    Dane Weber
    Lead Consultant
    Excella
    schedule 4 months ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.

    The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - The Velocity Trap: Learning to Value Enterprise Outcomes over Team Output

    45 Mins
    Tutorial
    Beginner

    Behind the creation of every Agile Framework was the intention to improve the Return on Investment for creative work, primarily through faster and richer feedback. But as team-level frameworks like Scrum are internalized by large organizations, that message gets mistranslated. Instead of, “Get better outcomes, sooner,” the drive instead becomes, “Just do more, faster.”

    A common expression of this problem is the confusion of Velocity for Value, where teams are directly managed based on their Output, but the connection between Output and Outcome is lost or ignored. This plays out in all kinds of ways that distract from achieving tangible results, and often incentivizes internal competition over collaboration. This problem can be especially tenacious in organizations with significant institutional ‘status-ing’ behaviors, where leadership struggles to translate common Agile methods like Relative Estimating into existing artifacts like Executive Dashboards or Earned-Value Management.

    In this tutorial, participants will explore the 'Velocity Trap', and will be shown how to setup a results-driven framework that prioritizes 'Maximizing Outcomes while Minimizing Output.'

  • Joshua Seckel
    Joshua Seckel
    Specialist Leader
    Deloitte
    schedule 4 months ago
    Sold Out!
    45 Mins
    Case Study
    Advanced

    Many agile talks are about the benefits of cross-functional teams and integrating them with your business and changing their structure to better align to the value delivery. And amazing things happen with you get all of this stuff working together. There are industries and organizations that can't do this. Not because they don't want to or that they are not interested in the modern ways of working, but because they don't have the skills in-house and the cost of bringing all of those skills into the organization are inhibited by constraints of one sort or another.

    The use of contractors and outsourcing of IT development was a major push for many years as businesses focused on their core capabilities. Industries like government couldn't compete with the marketplace for IT skills and so turned to contractors to fill the needs in many organizations. Now, these same organizations feel they need to bring the modern agile ways of working to their organizations. So how do they actually get the benefits of modern agile ways of working and delivering products while continuing to use contractors for most of the work?

    This talk will focus on 3 areas of achieving most of the benefits of modern agile work while continuing to use contracted work. First, how to decide what to outsource. The decision of which pieces or work to use contractors for is the most important. Second, how to actually hire contractors. The procurement process can be evolved to be more agile and to encourage finding contractors that will drive toward the desired collaboration. Finally, how to manage and work with contractors. The day to day grind of working where real delivery will be accomplished.

    Getting benefits from an agile framework and delivery is important and can still be achieved when some of the work is outsourced and the importance of defining and finding the right contractor are vital to achieving the desired success.

  • Liked M. Scott Ford
    keyboard_arrow_down

    M. Scott Ford - Building a Bridge to a Legacy Application - How Hard Can that Be?

    45 Mins
    Experience Report
    Beginner

    My team was asked to build an integration with an old legacy application which had no programming API whatsoever, and we were so excited. How did we tackle that challenge? Did we succeed? What happened next? Come and listen to find out. And I promise the ending will surprise and/or depress you.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Overcoming Your Biases: Putting the GROW and Satir Interaction Models to Work

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 4 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Intermediate

    If you hold any form of leadership position, whether as a manager, scrum master, or coach, you will find that you will be at times offering guidance or advice. What unfortunately happens though is that your observation of the need and conversation to help fill that need can get tangled with your biases. Want to improve your coaching conversations? Then this workshop is for you.

    To help you work through the arc of your conversation and understand how these biases come into play, we're going to discuss the GROW conversation model and the Satir interaction model. This workshop will open with an anchoring activity. We'll then use an exercise and focused discussion to review each model and see how these played into the coaching received.

  • Liked Brandon Raines
    keyboard_arrow_down

    Brandon Raines - Are there any responsibly Agile Ways to Perform Long Term Planning?

    Brandon Raines
    Brandon Raines
    Agile Coach
    Shokunin LLC
    schedule 5 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Intermediate

    Sometimes, a good debate is what’s needed. Conventional wisdom is boring. Agile is old enough now to inject some alternative thoughts. This session seeks to use the idea of the French Salon. A salon is a gathering of people under the roof of an inspiring host, held partly to amuse one another and partly to refine the taste and increase the knowledge of the participants through conversation. The intent is to combine learning, good manners, and conversational skill. Salonnières provided a place to gather, a topic, a structure or starting point for the gathering, and ensured that there would be a good mix of opinions among the guest list. “Salonnières therefore had to perform a difficult balancing act, cultivating individual merit without letting one guest overshadow the others.” Therefore, the goal is to facilitate the topic of Long Term Planning in Agile and whether there are any responsible ways to perform and execute it. Participants will bring their ideas along with an open mind to developing new possibilities.

  • Liked Ben Morris
    keyboard_arrow_down

    Ben Morris - Agile Isn't Enough for Government Transformation

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 4 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Executive

    The federal government, and many local governments, have embraced agile. This has been helpful in terms of incremental progress for the "how" of building software.

    However, it's not enough.

    The next big shift is when government agencies lift their focus from IT project delivery to digital product management - focusing on the "what" should be built and "why" it should be built. Such a shift will move agencies from incremental progress in delivering mission value to a ground-breaking shift in how missions are supported via technology.

  • Liked Jason Glisson
    keyboard_arrow_down

    Jason Glisson - Farmers.gov - Interactive Tool Design (UX/UI) and Development (Drupal)

    Jason Glisson
    Jason Glisson
    Drupal Developer
    MetroStarSystems
    schedule 6 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Farmers.gov is an award winning USDA sponsored government project site.

    When Metro Star Systems won the contract for Farmers.gov, there was one developer and one UX/UI Designer. We were tasked with creating a new site that was easy to navigate, simple to use, and eventually, we would need to create interactive tools for farmers and producers to use in various places throughout the site.

    We'll discuss our method for building out the site, the design system that we're currently working on, some of the challenges that we've encountered, and how we worked with government release trains.

    Attendees will learn about our site, how we plan things, how we scope our development tasks, how we deploy, and how we design the site with our end users in mind. We'll discuss analytics and how they are used to make UX/UI decisions.

    Lastly, we'll touch on the tools that we've build for Farmers.gov and how they were build with our users in mind. We'll also talk about how we built our most recent tool for Farm Loan Discovery.

  • Liked Saya Sone
    keyboard_arrow_down

    Saya Sone - Collaborate SAFe & Design For Better Product Performance

    Saya Sone
    Saya Sone
    Agile Coach
    OCTO Consulting
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    While our program has grown up to have 16 teams, our Design Systems team still has the same amount of resources. We ran into a question - should we add more resources or find a better way to integrate SAFe (Scaling Agile Framework) along with the design process? Another concern is that the Design Systems team receives many ad hoc requests from different teams that are asking for the same prototype with a slightly different flavor. Our architects and designers are also not usually in sync of the UI/UX dynamics.


    This workshop will present a 4-D (Discover, Define, Design, and Deliver) model to help the Design Systems team integrate with all development teams to plan wisely to avoid duplicates or last-minute requests. The 4-D model aims to follow Agile and Lean principles to promote increased collaboration and interaction among individuals and teams. The model uses Design Thinking and Lean Startup concepts to design the right systems to gain customer values. Most importantly, our Design Systems team can improve their stakeholder engagement with shorter planning of iteration where our development team can produce software faster. The 4-D model proves a better product performance that requires more collaborative and shared design work with frequent agile delivery of customer-valued products. We anticipate UI/UX designers, architects, portfolio managers, product owners, project managers, scrum masters, and agile coaches who want to learn how to collaborate SAFe and design for better product performance join this workshop and take away the technique to improve their enterprise level of design processes.