Retrospective Jedi Mind Tricks

Retrospectives are a key component in assisting you teams to improve. Most Jedi, er, Scrum Masters know how to facilitate a retrospective. However, many do not consider how to SELECT a retrospective based on the needs of their teams. Different types of retrospectives will be considered, such as the 6 Thinking Hats, Appreciation, Sailboat, and in addition, two Custom retrospectives. Have you considered which retrospectives you would facilitate for your team based upon their needs? For example, if you are with a new team, what would retrospective would you select? If your team seems to have trouble working together or communicating, which retro? How could you customize a retrospective to address the needs of your team?

 
 

Outline/Structure of the Talk

The structure will be a slide presentation with audience discussion that will cover the following:

Retrospective Jedi Mind Tricks

  1. Brief review of Retrospectives
  2. Discussion of different types of retrospectives
  3. Why should I use different types of retrospectives for different team needs
  4. How do I determine my team needs
  5. Where can I find more information on retrospectives

Learning Outcome

Learning Objectives:

  • What are the different types of retrospectives available?
  • Where can I find different types?
  • When should I use certain types of retrospectives?
  • How can I adapt them to the needs of my team?

Target Audience

Scrum Masters and anyone interested in learning about Retrospective ideas

Prerequisites for Attendees

What is a Retrospective and what is its purpose

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  1 year ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • the need to select a retrospective format to meet the current context

    I think the submission could be improved by:

    • providing reviewers with more detail of your content.
      • What different types of retrospectives are you considering?
      • What needs are you considering?

    Retrospectives are important to me, but I've found that different people mean very different things by them. As a reviewer, I need to know what retros mean to you.

    • Ken Horton
      By Ken Horton  ~  1 year ago
      reply Reply
      Hi George, 

      Thanks for your feedback. I revised the Abstract section a little. Please let me know if this is clearer, or what you were looking for. This is my first time, so I apologize if it was completed properly.

      Just in case there is an issue with the submission, I have included what I revised.

      Abstract: Retrospectives are a key component in assisting you teams to improve. Most Jedi, er, Scrum Masters know how to facilitate a retrospective. However, many do not consider how to SELECT a retrospective based on the needs of their teams. Different types of retrospectives will be considered, such as the 6 Thinking Hats, Appreciation, Sailboat, and in addition, two Custom retrospectives. Have you considered which retrospectives you would facilitate for your team based upon their needs? For example, if you are with a new team, what would retrospective would you select? If you team seems to have trouble working together or communicating, which retro? How could you customize a retrospective to address the needs of your team?


      I am interested in your feedback. Thanks again.

       

      Thanks...

      C. Ken Horton



      On Saturday, July 7, 2018, 12:19:04 PM EDT, AgileDC 2018 <info@confengine.com> wrote:


      Dear Ken Horton,

      Please note that the proposal: Retrospective Jedi Mind Tricks has received a new comment from George Dinwiddie

      I like these aspects of the submission, and they should be retained:

      • the need to select a retrospective format to meet the current context

      I think the submission could be improved by:

      • providing reviewers with more detail of your content.
        • What different types of retrospectives are you considering?
        • What needs are you considering?

      Retrospectives are important to me, but I've found that different people mean very different things by them. As a reviewer, I need to know what retros mean to you.


      Visit https://confengine.com/agiledc-2018/proposal/6903#comments to respond to the comment OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

      Regards,
      AgileDC 2018 Team
      comment-9360@reply.confengine.com
      You have received this important update from ConfEngine on behalf of AgileDC 2018.
      Download ConfEngine's Mobile App to totally personalise your conference experience.
      If you are 100% sure, that this email was sent to you by mistake, please click here to unsubscribe from all future email updates from ConfEngine.
      ------=_Part_3631172_1975312308.1531436074360--
    • Ken Horton
      By Ken Horton  ~  1 year ago
      reply Reply

      Title: Retrospective Jedi Mind Tricks

      Abstract: Retrospectives are a key component in assisting you teams to improve. Most Jedi, er, Scrum Masters know how to facilitate a retrospective. However, many do not consider how to SELECT a retrospective based on the needs of their teams. Different types of retrospectives will be considered, such as the 6 Thinking Hats, Appreciation, Sailboat, and in addition, two Custom retrospectives. Have you considered which retrospectives you would facilitate for your team based upon their needs? For example, if you are with a new team, what would retrospective would you select? If your team seems to have trouble working together or communicating, which retro? How could you customize a retrospective to address the needs of your team?

      Learning Objectives:

      • What are the different types of retrospectives available?
      • Where can I find different types?
      • When should I use certain types of retrospectives?
      • How can I adapt them to the needs of my team?

      Audience: Scrum Masters and anyone desiring to learn how to improve in their retrospective techniques.

      Time: 40 – 50 minutes.


  • 45 Mins
    Talk
    Intermediate

    Despite thinking that organizations are slow to innovate, innovation actually abounds at many companies. Kodak, DEC, and Xerox did not fail due to lack of new, cutting-edge innovation; they failed because their organizations were tuned to their traditional markets, and a failure to change their business models and organizations led to their eventual disruption.

    The key to achieving business agility lies in leadership that transforms organizations. Transformational leaders succeed by changing the system, leading with purpose, and steering from the edges. They own their responsibility and boldly lead their organizations into the future. As leaders, we can accelerate this evolution by enabling true self-management and team-based governance.

    Join Bob and Sanjiv to learn how leaders can transform organizations with a flatter organization structure, work anywhere flexibility, participatory profit sharing, and delegated hiring and firing. Explore the agile leadership journey needed for true business agility.

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman / Wm. Hunter Tammaro - Breaking Up is Hard to Do: How to Split a Team (Without Breaking It)

    45 Mins
    Experience Report
    Beginner

    Struggling to fit your Agile team into one room for ceremonies? Daily stand-up meetings dragging on? Finding it harder to keep the whole team informed? It might be time to split into the three- to nine-person teams the Scrum Guide recommends for better communication, collaboration and decision making. But abruptly changing the team structure can disrupt the larger group's dynamic and culture, and by breaking existing lines of collaboration, hurt the sense of team and organizational unity that already exists. By sharing our experience working with a large team at a non-profit client, we will illustrate the challenges that can face an Agile transformation when a team already has a culture of collaboration worth preserving. The lessons learned from our story will highlight not just the principles for nurturing Agility in a team's culture, but also specific strategies we used to overcome challenges and ensure the journey was one all our teams could embark on together.

  • Liked Lisa Cooney
    keyboard_arrow_down

    Lisa Cooney - Brain Agility: Overcoming Cognitive Bias

    Lisa Cooney
    Lisa Cooney
    Principal Agile Coach
    Axios
    schedule 1 year ago
    Sold Out!
    45 Mins
    Workshop
    Intermediate

    Did you know that your brain tells you stories all day long, and that if they are good stories, you believe them? Come to this entertaining interactive session to experience some "cognitive illusions" for yourself, and learn what they demonstrate about how our brains' work. Cognitive science and behavioral psychology offer important insights for agilists, insights that can help us work more effectively with our co-workers and clients. You will learn how awareness of our brains' tendencies is a powerful tool to overcome our own innate cognitive bias, and the cognitive bias of others. This newfound awareness can open you to more varied perspectives in order to tell yourself a story that is both richer and more nuanced -- and closer to being "a true story."

  • Liked Salah Elleithy
    keyboard_arrow_down

    Salah Elleithy / Ganesh Murugan - Mobbing for learning!

    45 Mins
    Talk
    Intermediate
    “We don’t have time for learning but we want to deliver value fast. And by the way, we need to develop new skills and attract talent but we have limited to no budget!” Huh!
    Does that sound familiar? If it does, you are not alone! This is one of the most prevalent patterns we have seen in organizations. We see this almost everywhere. Leaders and Managers demand that teams deliver value fast with no time to learn new skills. It's an oxymoron or may be a paradox!
    It's difficult (dare I say impossible) to attract talent if your organization keeps doing what it has always done. And if your organization needs to develop new skills internally, how will it be able to do that without dedicating time for deliberate learning?! A vicious cycle to say the least not to mention the impact on morale.
    I am not a mind reader but I could imagine you looking at us with a puzzled look and a thought that goes like, "Ya think!" It would be a valid response, I say, as I am sure you have seen or experienced this vicious cycle in many places. You may be even experiencing it right now!
    In this session, Salah and Ganesh can help you explore concrete ideas for experimentation on balancing speed and learning using concepts from Mob Programming. We can't promise any silver bullets however we do believe in experimenting and learning fast!
    Questions to explore:
    1. What is Mob Programming (or Mobbing)?
    2. Where to find talent/skills currently in your organization?
    3. How to introduce Mobbing to accelerate the learning?
    4. What does it take to amplify the good? (or as Woody Zuill puts it "turn up the good!")
    5. What is mobbing for learning and how does it help solve this problem?
    At the end of this session, you will be able to introduce Mobbing to your organization (perhaps even with a demo), attract developers who really want to shake things up and start finding places to "turn up the good!".
  • Liked Chris Li
    keyboard_arrow_down

    Chris Li - Power Windows and Prioritization - a different approach to ordering your Product Backlog

    Chris Li
    Chris Li
    Founder
    SparkPlug Agility
    schedule 1 year ago
    Sold Out!
    45 Mins
    Workshop
    Intermediate

    Product Owners have the challenging task of choosing which items their teams should focus on next. By combining their experience, conversations, and intuition, they often have to make decisions based on a set of imperfect data, which is hard to do. Adding to this, that they may have to justify their reasoning, making the task of prioritizing even more difficult.

    In this workshop, participants will explore the Kano Model, an approach that takes into account satisfaction, functionality, and categorization to best identify the most important things based on customer response. This model gives Product Owners real data and insights to aid their decision making process, vastly improving on "this is important because I said so!"

  • Liked Joshua Seckel
    keyboard_arrow_down

    Joshua Seckel - Modern Agile 101 for Government

    Joshua Seckel
    Joshua Seckel
    Specialist Leader
    Deloitte
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    In 2001, a group of software developers got together in Snowbird, UT, and created the Agile Manifesto. The Manifesto was a statement of core value and principles. The core values are:

    • Individuals and interactions over processes and tools
    • Working software over comprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan

    These four values are supplemented by 12 principles of agile software. The original 17 signatories were joined by thousands of additional people with the ability to sign cut off in 2016.

    These principles are the foundation of much of the work in agile that has occurred in agile development, but have been mostly frozen as practices and agile has evolved.

    Modern Agile has been created recently to update the underlying foundational values and to provide a focus beyond software delivery. Those four values are:

    • Make People Awesome
    • Deliver Value Continuously
    • Make Safety a Prerequisite
    • Experience and Learn Rapidly

    This talk will walk through this reimagining of the agile values and what they mean for delivery within a government context. We will take each value and look at government cultural and technical challenges and opportunities to advance modern development practices.

  • Liked Clare Stankwitz
    keyboard_arrow_down

    Clare Stankwitz / Mathias Eifert - Making Agile Work for Data Teams: Writing Effective PBIs for Data Products

    45 Mins
    Talk
    Intermediate

    Want to help your data and analytics teams embrace Agile but don’t know where to start? Wondering why your data team seems to struggle with creating manageable yet valuable stories? Curious why we think Agile for data teams is a distinct challenge?

    Data work is often structured more like a pyramid than the familiar “layer cake” metaphor due to the state of data infrastructure technology, common industry practices, and the heavy lift to integrate data before it can be analyzed and visualized. Prevailing Agile wisdom of cutting work into “vertical slices” thus presents significant challenges for Agilists working on data teams! Typical full-stack vertical stories in this environment can easily become too complex, interdependent, and unwieldy to fit into fixed-length sprints. Technical stories can encapsulate smaller work increments but risk becoming too abstracted from the customer’s core problems and trap the team in infrastructure work for too long. An additional impediment to traditional user stories is the highly exploratory nature of advanced analytics and data science projects where in many cases end users lack awareness of what kind of problems can even be solved and technical experts can’t initially predict which solutions will actually be possible.


    This session presents successes and lessons learned from applying alternative story decomposition and writing techniques on several data products across multiple teams. Returning to one of the fundamentals of what makes Agile valuable, namely to obtain feedback on feasibility and end user value as quickly and systematically as possible, our approaches strive to ensure teams have small, independent stories while still maintaining a value focus. We discuss ways to decouple the technical stack through stubbing and gradual tightening of the Definition of Done. This technique accommodates the necessary foundational work in the background while also obtaining early feedback about the value of the eventual product delivery options. A second approach incorporates Lean Startup concepts and centers on replacing traditional user stories with testable hypothesis statements that allow for explicit experimentation and risk trade-offs towards relevant milestones such as model quality, performance, predictive reliability, etc. in the context of extreme uncertainty.


    Join us as we discuss some of the friction Agilists can encounter on data teams, as well as some validated ideas for meaningful solutions.

  • Trent Hone
    Trent Hone
    Excella
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Agile at the team level fosters self-organization by leveraging constraints. Timeboxes, Work in Progress (WIP) Limits, and clear operational definitions are excellent examples of the kinds of constraints teams regularly employ to deliver reliably. Are you familiar and comfortable with these ideas, but uncertain how to apply them at larger scales? Are you looking for techniques that will allow you to harness the creativity of your teams to enable self-organization at scale? If so, this session is for you.

    I’m passionate about applying concepts from Complex Systems Theory (as developed by Dave Snowden, Alicia Juarrero, Bob Artigiani, etc.) to the work of software teams. My colleagues and I at Excella have been exploiting these ideas by using a variety of patterns borrowed from different theories and frameworks to allow our teams to grow like healthy plants in a garden. From Large-Scale Scrum (LeSS) we leverage the concepts of a single product backlog and a shared cadence. Kanban principles of visualizing the work and limiting WIP help align the teams and foster greater collaboration. Dave Snowden’s emphasis on Homo Narrans—the human as storyteller—has provided a framework for clarifying and promulgating common values, which are essential for decentralized decision-making. Collectively, these mental models created an environment that helped us scale one of our engagements from three teams to eight over the course of a single year.

  • Liked Doguhan Uluca
    keyboard_arrow_down

    Doguhan Uluca - Ship It or It Never Happened: The Power of Docker, Heroku & CircleCI

    45 Mins
    Talk
    Intermediate

    Shipping code is hard and it is rough! It doesn't have to be. Using Docker, Heroku and CircleCI you can set up a world-class Continuous Integration and Continuous Deployment pipeline in an hour with advanced functionality like Heroku preview apps, provisioning servers on-demand for to scale and containers that leverage layering to enforce Enterprise requirements, while giving developers access, flexibility and speed to get their work done. With duluca/minimal-node-web-server docker image and how you can tailor it to build your micro-services or web servers in a matter of minutes using Docker and deploy your web app on the cloud.

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman / Wm. Hunter Tammaro - Measuring Flow: Metrics That Matter

    45 Mins
    Talk
    Intermediate

    Does your Scrum team start all its stories on Day 1 of the Sprint? Do stories sometime carry over into the next Sprint? Or perhaps testing always gets crammed in on the last day of the Sprint? If any of these sound familiar, your team may benefit from improving its flow.

    Flow metrics are common with Kanban, but can provide tremendous value to any team, including those using Scrum. In this session, we’ll start by exploring the value of achieving a smooth flow of work (versus simply achieving maximum utilization) and give simple ways for your team to measure its flow. We’ll look at examples of metrics including lead and cycle time, throughput, and the cumulative flow diagram (CFD), reviewing what each represents, easy ways to collect them, and how they can be used in both a Kanban and Scrum context. You’ll leave the session knowing how to interpret and capture all these valuable metrics, so your agile team can measure and improve its flow.

  • Liked Jaap Dekkinga,
    keyboard_arrow_down

    Jaap Dekkinga, - Story point cost. How to calculate it and how to use it.

    Jaap Dekkinga,
    Jaap Dekkinga,
    Agile coach
    Excella
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Story point is an arbitrary relative measure used by Scrum/agile teams to define the effort required to implement a story or feature. This is a metric to measure the cost related to the implementation of story points. This metric is called Story Point Cost. It should allow to track development costs and also make the Scrum team aware about the budget issues of their project and for product owners to easier compare cost to gained value.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Iterative vs. Incremental – What’s the Difference and Why Should You Care?

    45 Mins
    Talk
    Beginner

    Agile is an incremental and iterative approach to delivering value to our customers. But too often we assume it’s really all about ways to slice work into smaller batch sizes and that both approaches are fundamentally equivalent. However, there is a crucial difference and this lack of awareness is a major contributor to projects and teams that are AINO (Agile In Name Only)!

    In this session, we will discuss how to differentiate between incremental and iterative approaches, their strengths and weaknesses, and why you really need both. We will explore the many ways in which iteration shapes the core of Agile practices, how it supports and enables the benefits of agility, and how understanding its awesome power is a key step in moving from “doing” Agile to truly being agile. In addition, we will take a close look at the practical implications of when to use each approach by discussing real world scenarios, highlighting common Agile anti-patterns and (re)examining familiar story slicing patterns.

    You will walk away with both a better understanding of one of the most important underlying principles of agility and immediately applicable insights for your daily work!

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 1 year ago
    Sold Out!
    45 Mins
    Tutorial
    Intermediate

    Losing good people during your transformation? Getting more resistance than you expected? You may be producing unwanted reactions in the way you are leading your people through change.

    If you want your Agile transformation firing on all cylinders without the harmful side-effects, managers at all levels should focus on becoming Catalysts. Much like a chemical catalyst, your job is to help boost organizational performance by creating a healthy environment and providing the needed support.

    In this interactive presentation-tutorial, we’ll explore how you can do that through some simple techniques that anyone can do; extracted from Fearless Change and Liberating Structures. We'll relate these techniques to how trust works and give you some powerful ways to improve your organizational trust.

  • Liked Donald Patti
    keyboard_arrow_down

    Donald Patti / Lisa Brown / Meghana Ekbote / Yogita dhond - Scrum in a Snap: Using Snap Circuits to Excite & Educate Scrum Newcomers

    45 Mins
    Workshop
    Intermediate

    The best way to learn Scrum is by doing, but it can be difficult to simulate Scrum and see how well Scrum helps team overcome technical hurdles without actually building something technically challenging. Lego's have always been a fun option for introducing Scrum, but it's difficult to recreate technical impediments, the need for spikes and managing technical debt with our tried and true friend, the box of Lego's.

    Arguably, a better alternative might be Snap Circuits, a toy designed to introduce children to electronics in a fun and easy-to-understand format. Like Lego's, adults gravitate toward Snap Circuits because they are colorful, quickly understood and snap together with ease.

    But, Snap Circuits have the added advantage of requiring a small amount of technical learning during the simulation that make it a closer match to the technical obstacles faced by a typical Scrum team.

    In this workshop, you'll learn one "Scrum in a Snap" simulation exercise. In addition, we'll provide you with a few other "Scrum in a Snap" ideas and encourage you to experiment on your own. Four lucky attendees will also win their own Snap Circuits kit so they can develop their own Scrum games.

    Past participants in "Scrum in a Snap" have said "The best Scrum exercise I've ever done", "I can't believe how much it's like coding - without actually coding", "What a blast - I'll never forget this activity!" and "Where can I buy one?"

    Attend this workshop to see why.

  • Steve Moubray
    Steve Moubray
    Agile Coach
    cPrime, Inc.
    schedule 1 year ago
    Sold Out!
    45 Mins
    Workshop
    Intermediate

    How do you promote mastery of practice areas? Danial H. Pink tells us people are motivated by autonomy, mastery and purpose. Small Agile teams promote autonomy while value streams and corporate missions promote purpose. Communities of Practice can be a great way to promote mastery, if formed correctly.

    Communities of Practice are more important today then they’ve ever been before. We’ve learned cross-functional teams are the best way to produce customer focused products but as we put people into value streams and product teams, are we creating silos where practice domains don’t communicate as often and knowledge gaps are widening? There’s a reason why most Agile Frameworks recommend forming Communities of Practice.

    In this workshop we’ll talk about forming masterful communities and you’ll create a handy pocket guide to take with you.

    Come learn how to form Masterful Communities of Practice and lead your organization going forward.

  • Liked Sean Killeen
    keyboard_arrow_down

    Sean Killeen - Level Up Your Team's Agility with Better Technical Interviews

    45 Mins
    Talk
    Intermediate

    Have you ever been in a technical interview, stuck at a whiteboard or solving a brainteaser, and thought “there must be a better way”? Good news: there very much is.

    Agility and adaptability are crucial for a development team's success, but how often do we target for agility when considering who to bring into our team? And how do we set expectations for agility from the first time this potential new hire begins evaluating our team?

    In this talk, I walk through my philosophy & provide practical tips for running technical interviews that are primed for success.

  • Liked Sharyn Horowitz
    keyboard_arrow_down

    Sharyn Horowitz - Unraveling Red Tape – Being Agile in a Bureaucracy

    10 Mins
    Lightning Talk
    Intermediate

    Sure, we would like everyone to have an agile mindset and focus on continuous improvement, but sometimes as Agilists we need to work with stakeholders who don’t agree with our priorities or our methods. When you need to get something done in a bureaucracy, how do you adapt? Every place you operate has a unique combination of people, processes, and problems. We'll discuss general principles that will help you navigate successfully.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - 5 Myths Killing Agile for Government

    45 Mins
    Talk
    Executive

    Over the last 5 years, Agile approaches have seen widespread adoption across the US Federal Government. Where real commitment is given to proven Agile frameworks and techniques, programs do see significant improvement in value delivery and speed. But unfortunately often, ‘Agile’ nomenclature is used while perpetuating behaviors that make real improvement impossible, and may actually make the lived experience worse for participants or stakeholders. And where Agile approaches fail, they add to a narrative that real methods won’t work in this environment. Many of the anti-patterns I’ve seen working as a Coach in the Public Sector are rooted in decision-makers clinging to 5 myths about Agile in Government. This talk will explore these 5 myths, where they come from, and some ways out of them.

  • Liked Donald Patti
    keyboard_arrow_down

    Donald Patti - Sure, Delegate...But How?

    45 Mins
    Workshop
    Beginner

    As agile practitioners, we are well aware that we need to delegate decision-making and responsibility to members of the team, but it's often easier in principle than it is in practice. Frequently, delegating triggers some angst in most of us, usually revolving around our biggest fear: "What if they fail miserably?"

    Fortunately, there are better questions to ask before we delegate, including:

    • How can I determine whether the person is capable of handling the responsibility delegated?
    • If they're not ready, how do I help them to acquire that ability?

    In this combination tutorial and workshop, we'll answer both these questions so you can be more successful when you delegate. We'll also give you an opportunity to apply your newly acquired knowledge via in-class simulation and provide information to help you coach others in effective delegation.

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Undercover Scrum Master

    Dane Weber
    Dane Weber
    Lead Consultant
    Excella
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    What can an experienced Scrum Master learn by going undercover, passing himself off as a software developer?

    • Why developers complain about meetings!
    • Why they always want to "pay off technical debt!"
    • Whether TDD & Pair Programming are worth it!

    For the last year, Dane has served as a Ruby developer on a Scrum team, while all of his prior experience on Agile teams was as a Scrum Master or Product Owner. Dane will share his experience and insights from life on both sides.