Pixar Pitch and ways to bring story into your retrospectives

“What went well? What could be improved? What change will we make for out next sprint?” Does every retrospective just answer these three questions and get to done? Many teams go through the motions for retrospectives and have a focus on efficiency over effectiveness.

Stories are a primary method of conveying information and cultural norms. Stories are also a good way to enliven retrospectives and make them more effective at process improvements. Josh shares his experiences using different story techniques for improving retrospectives. Josh guides the room through the Pixar Pitch technique for retrospectives. This technique is based on the Pixar Pitch that every Pixar movie follows. You experience these six simple prompts and how to transform this into a retrospective, then take it back to make retrospectives more exciting and engaging with your teams. Additionally, Josh shares other techniques and ideas that can be used for use of story in retrospectives.

 
 

Outline/Structure of the Workshop

Intro of me and stories (one intro factual and one story oriented to provide immediate impact of story - 5 minutes)

Pixar Pitch walk through (5 minutes)

1. Once upon a time there was …
2. Every day …
3. One day …
4. Because of that …
5. Because of that …
6. Until finally …

Group work on creating a Pixar Pitch based on a common activity (15 minutes) - I will already have flip charts with the basic phrases created and ready to use. Also I will have a helper to walk and help if people are stuck in addition to myself to keep time

Debrief pitches (5 minutes)

Walk through of how to complete this as a retrospective activity (7 minutes) - where to focus for ideas for improvement or continuation, how to get to what is changing

Depending on actual time - introduce some other story frameworks that can be used, Q&A.

Handout with the Pixar pitch and other frameworks will be provided

Learning Outcome

Understanding of importance of stories in work

Ability to execute Pixar pitch technique for performing retrospective

Knowledge of other story frameworks

Target Audience

Retrospective facilitators, retrospective participants

Prerequisites for Attendees

Have been to a retro before - or at least heard of one.

schedule Submitted 1 year ago

Public Feedback

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

    Does this activity review the groups past shared experience together?

    I agree with David that a 5-minute debrief for multiple stories seems VERY short.

  • David Fogel
    By David Fogel  ~  1 year ago
    reply Reply

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

    • As seen in the videos, Josh has a great sense of humor weaved with practicality. This presentation seems like a great way to empower other folks to have a fun - yet practical - way to facilitate a retrospective

    I think the submission could be improved by:

    • It seems like five minutes is insufficient for the debrief pitches section

  • Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 1 year ago
    Sold Out!
    10 Mins
    Lightning Talk
    Intermediate

    In this lightning talk, we explore the 5 attributes to look for in a ScrumMaster:

    • Knowledge - Deep knowledge in Agile and Scrum
    • Experience - Deep experience with Scrum teams and in Agile environments
    • Coaching - Deep understanding of Coaching concepts and techniques
    • Facilitation - Deep understanding of Facilitation concepts and techniques
    • Servant Leadership - Deep understanding and desire to enable success for the teams and the organization

    From there we look at the ScrumMaster's progression for removing impediments and addressing issues:

    • Did we talk about it in the Retrospective?
    • Did we discuss the impact?
    • Did we identify root causes?
    • Did we come up with solutions?
    • Have we tried the solutions?
    • What were the initial results?
    • What are next steps from here?

    We use the steps above to ensure:

    • Our teams are not making the same mistakes time time after time
    • Our teams are not having the same issues arise time and time again
    • Our teams are not stagnating but rather are getting better over time

    This session will arm session attendees with what to look for in a ScrumMaster and discuss how the SM uses the impediment progression to ensure we have a continuously improving team.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Building the Pipeline of My Dreams

    45 Mins
    Case Study
    Beginner

    I often suggest to teams that they should be using all sorts of tools in their pipelines- from simple static analysis checks and automated builds to security scans and performance testing. I've done presentations and talks at conferences. I've lobbied to clients. I've commiserated with my colleagues. But I've never put together my dream pipeline in one of my own projects.

    There are always reasons that some tests and tools get left out- our policies won't allow them, they will take too long to get approved, we don't have time, we have bigger problems to deal with, it just isn't what the client is looking for right now. And I usually think, if only I were in charge, I'd make sure we were using those...

    In late 2017 I took over maintenance on an open-source project. Now I have no restrictions. The sky's the limit. No one is around to tell me what I can't do. So why don't I have my dream pipeline in place yet?

    I'll talk about the trade-offs and compromises I made when building out the pipeline. Why I decided to focus on some tools and tests but skipped others, and what I need to do or change to make this delivery process the pipeline I've always dreamed about, now that I have no one else to blame.

  • Liked John Hughes
    keyboard_arrow_down

    John Hughes - Agile FTW: Competitive Advantage and Happiness Through Business Agility

    45 Mins
    Talk
    Intermediate

    We all know the story of how the Agile ‘Software Development’ Manifesto emerged out of Snowbird in February of 2001. And we all know that Agile is still the current best practice for software development. What remains to be fully realized is that Agile has evolved to a best practice for business in general; a way of life for that matter.

    I had the privilege of bringing Agile into business over the last couple years. In that time, I introduced my executive leadership team to Business Agility. After getting executive participation in the inaugural Business Agility conference in Feb 2017, we partnered together to seek the benefits of a comprehensive Business Agility adoption.

    Using our corporation’s strategic planning and execution effort to exemplify, I will share with you how the Agile mindset and practices apply to business and drive the highest impact possible towards the most valuable goals and initiatives. Modern leadership and business practices such as those under the Business Agility umbrella bring a value-driven, data-driven, efficient focus on impactful delivery.

    • Revenue and growth accelerate as we focus the company’s resources on delivering in the most valuable way
    • Corporate processes lean out as we remove wasteful bottlenecks, saving money, time, and providing competitive advantage
    • Employees are more capable as corporate practices are more meaningful and less taxing
    • Back-office tools and data are integrated into a unified experience allowing real-time awareness and predictive analytics, increasing effective decision-making and enabling empowerment at lower levels
    • Employees are happier. Customers are happier. The corporate bottom-line reflects this happiness.

    I am enthusiastic about the spread of Agile beyond IT. And as such, I am excited to illustrate the brilliance of Business Agility to session participants, adding examples from my most recent corporate transformation effort to exemplify the mindset and practices presented. It is my interest that participants come away with an understanding of how Agile mindset and practices benefit the corporate back office as much as they do software delivery, and how their companies can begin to benefit too by applying what they learn from this presentation.

  • Liked William Strydom
    keyboard_arrow_down

    William Strydom / Kevin Callahan - Reading the Undercurrents of Team Interactions

    45 Mins
    Workshop
    Intermediate

    Are you involved with teams? Want to be able to shape team dynamics toward more productive outcomes?

    Come dive below the surface of personalities and words to discover the perspectives that shape them.

    We’ll learn together and from each other through facilitated hands-on experiences.

    You will be able to apply what you learn immediately and directly to improving the quality of interactions.

    The efforts of teams is widely regarded to be a competitive differentiator. Being a member of a high-performing team is often reported as a life high point by those who experience it. All around us there is a growing emphasis on teams and teamwork.

    Yet effective teams remain elusive. More often groups of people who come together simply cooperate rather than collaborate. They avoid productive conflict, instead engaging in counterproductive discourse.

    We can do better. As coaches, we can learn how to read the underlying dynamics that drive team behavior. To enable them to understand what drives their interactions (hint, it’s not the individuals!).

    Facilitators will guide the group through a series of experiential activities to teach David Kantor’s Four Player Model and David Kolb’s Experiential Learning Model. Both models are robust and have been thoroughly researched and widely applied.

    This may very well be the answer to getting your stuck teams to move beyond their perceived issues toward collaboration and creativity!

  • Liked Cheryl Chamberlain Duwe
    keyboard_arrow_down

    Cheryl Chamberlain Duwe - A Holistic View of Agile and Quality: or, How I Survived My First Three ISO Audits

    Cheryl Chamberlain Duwe
    Cheryl Chamberlain Duwe
    Agile Coach
    Sevatec
    schedule 1 year ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Agile Quality Management (AQM) at Sevatec was born out of a need for the quality department to add value to our organization. Sevatec is a contractor to the Federal Government with specialties in Agile, DevSecOps, Cloud Solutions, Data Storage and Cyber Security. The hypothesis was that we could meet and exceed all of our industry standard quality objectives through adopting an agile mindset tied to modern leadership practices.

    Prior to the creation of the AQM office, Quality was driven by a single person behind a desk. There was no collaboration and the focus was on checking the box for the sake of maintaining quality designations. Data showed that there was little to no improvement as a result.

    Our new approach to quality derived from implementing business agility practices, with the belief that our ISO and CMMI requirements will be met and exceeded through the holistic application of agile principles. This provided an added value to the company, in that quality is baked in to every aspect rather than being led by someone sitting behind a desk churning out excessive documentation. Typically, discussions of quality in the agile environment are tied to code, but in our experiment, quality was embedded into all aspects of the organization, not just service delivery.

    Ultimately, our auditors spent more time asking us about our AQM approach than actually auditing us and were very impressed with the people, processes and tools we adopted. We believe that our holistic view of business agility will set us apart in the marketplace and drive our organization to its next level of excellent quality, in which all aspects of the business are operating in a lean, agile manner. Our focus on experimentation and continuous improvement lends itself to a fun, collaborative environment in which learning is expected, play is encouraged and quality is an outflow of our working culture.

  • 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 Scott Showalter
    keyboard_arrow_down

    Scott Showalter / Rachel Whitt - F.A.I.L.— Fearless Adventures In Learning: 4 Games to Explore the Value Behind Failure

    45 Mins
    Workshop
    Intermediate

    This session looks at four team-based improv & collaboration games that help teams embrace "failing successfully." Rather than glorify failure, we should understand that its power is not in failing alone, but rather the learning that emerges from it and the power that such learning has to unlock otherwise unforeseen opportunities. Our goal is to relinquish our fears of failure, break us out of our comfort zone and accept the prospect of failure with the ultimate goal of using it to better understand what success looks like, and how the struggle and pain of failure, and the learning that accompanies it, opens our mind to new possibilities we wouldn't have otherwise seen. These games create comfort with failure and build up our actionable learning muscle (insight synthesis, etc) that should accompany every unsuccessful attempt at success. Failure and learning for the win!

  • Liked Beth Wong
    keyboard_arrow_down

    Beth Wong / Jen Honermann - We're all in this together: How to be an ally in creating an inclusive work environment

    45 Mins
    Workshop
    Beginner

    Are you someone who values everyone's contributions in your work environment? Have you ever struggled with how to be an ally for a peer? Do you sometime feel like your perspective is undervalued or underrepresented?

    Industry research highlights teams achieve better outcomes when they are diverse and inclusive. This workshop will share what we see happening in the industry, and help participants develop learning strategies and leverages tools that they can bring back into their local environment. Attend this session and you’ll leave with the skills to grow as an ally and ways to foster a more inclusive culture within your organization.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Build a Better, Faster Pipeline for Software Delivery

    45 Mins
    Workshop
    Beginner

    The software delivery pipeline is the process of taking features from developers and getting them delivered to customers. The earliest tests should be the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing should increase confidence that the code is a viable candidate for production and that more expensive tests—be it time, effort, cost—are justified. Manual testing should be performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to problems progressing down the pipeline.

    In this interactive workshop, we will discuss how to arrange your pipeline, automated or not, and so each round of tests provides just enough testing to give you confidence that the next set of tests is worth the investment. We'll explore how to get the right types of testing into your pipeline at the right points so that you can determine which builds are viable candidates for production.

  • Liked Yogita dhond
    keyboard_arrow_down

    Yogita dhond - Dynamic Reteaming and Agile

    Yogita dhond
    Yogita dhond
    Agile Coach
    Accenture
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    As an agilist I strive to build great teams and then keep them together as they set on their Agile journeys. However, when you are in an environment where teams change all the time, it makes me wonder if the idea of dynamic teaming can be used to inspire teams to grow in a different way. A couple of years ago, Heidi Helfand, did an experience report about dynamic re-teaming (https://www.agilealliance.org/resources/experience-reports/dynamic-reteaming-how-we-thrive-by-rebuilding-teams/). I have used a lot of material from her research to implement dynamic re-teaming on my program.

    The idea of dynamic re-teaming has been working for us for over 18 months now. We have seen several interesting outcomes from this implementation. For one, the developers, testers and Scrum Masters are constantly on their toes - no one gets too comfortable with their team. But since we are all part of a large 16 team program, we still have managed to build camaraderie, owing in part to team members being reassigned across teams. In supporting a large IT organizations, most of our teams work on small applications for a period of 3-6 sprints. At the end of each such application, the team starts work with a new product owner. This forces the team to do a "reset" and allows them to examine the good, the bad and the ugly from their previous experience. It almost gives the team a chance to wipe the slate clean and start over. This alone has been a great source of inspiration for the teams to continue to grow. Another example of re-teaming is when someone from the development team rotates into a production support team. This idea was initially put in place to ensure that every developer has the experience of fielding user calls for the application that they put out. Being on the receiving end of these calls allows the developers to grow understanding the problems, first hand, from a users perspective. After their rotation, the developer goes back into a team with a renewed motivation to write better code.

    Dynamic re-teaming is core to what we do and I would love to share some experiences in this talk.

  • Liked David Bujard
    keyboard_arrow_down

    David Bujard / Chris Meaker / David Fogel - Impossible deadlines? Fail safely, learn rapidly with Spaceteam

    45 Mins
    Workshop
    Beginner

    Communication chaos under looming deadlines - sound familiar? We'll level up our teamwork, practice rapid learning, and identify ways to calm the chaos and focus on getting to done, all using Spaceteam, a chaotic and collaborative card game.

    You'll work with your teammates to repair a failing spaceship before it falls into a black hole. in order to escape, you'll communicate problems, request help, assist colleagues and respond to constant change -- all in five minutes!

    You'll learn from your failures, improve as a team, and gain insights into what helps organizations and teams collaborate effectively and achieve flow.

  • 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 David Bujard
    keyboard_arrow_down

    David Bujard / David Fogel - Nine levels of Agile Hell... and how to get out!

    45 Mins
    Talk
    Intermediate

    Our Agile transformations can feel like Sisyphean efforts – but do not abandon hope! In this talk we will discuss nine circles of Agile Hell. Each hell is an example of a common problem programs encounter.

    We'll ask the audience to prioritize their pain points, and focus on the six Agile hells closest to their experience. We will discuss real examples for “escaping” out of each Agile Hell - from Agile Coaches that the Dave(s) know.

    By attending this event, Agilists will expand their toolbox of techniques to help their organizations.

  • Liked Chris Ruch
    keyboard_arrow_down

    Chris Ruch - Putting the Customer First

    45 Mins
    Talk
    Intermediate

    Where has the customer gone in large scale enterprise agile frameworks? Customer Collaboration is one of the main tenants of the Agile Manifesto, but it seems that have we lost touch with this concept as we have scaled agile into large organizations. If we look at the SAFe Big Picture, the customer is represented, but only at the end of the process consuming the solution. This talk explores how and why it is important to pull the customer to the beginning and middle of the process and not just the end. This isn't to pick on SAFe -- the customer doesn't appear at all on the graphics for Disciplined Agile, LeSS, and Nexus at all! The concepts and principles explored in this presentation are universal in any large enterprise and can, and should, be applied to to any framework.
    Each of the main enterprise agile frameworks today (Disciplined Agile, SAFe, LeSS, Nexus, etc) have a graphic representation of their model, which present an inside-out view of how an enterprise is organized to delivery in an agile fashion. But what do our agile enterprises look like from the outside, from our customers' view point? As agile becomes widely adopted as the way of developing products, there is a growing gap with where new product development ideas are generated and how customer input is integrated into the agile process. Increasingly we are seeing organizations struggling because of a lack of an effective and experienced product management group and even experienced agile coaches not knowing how to effectively engage customers in their process.

  • Liked Yogita dhond
    keyboard_arrow_down

    Yogita dhond / David Bujard - Where's my UAT?

    45 Mins
    Talk
    Intermediate

    Agile adoptions hit a speed bump when big, complicated organizations expect User Acceptance Testing, and don't see an Agile equivalent. We'll demystify UAT, and show the multiple places in where it can be found in Agile delivery.

    Big and complicated organizations -- particularly government! -- conflate two different ideas in UAT: final sign-off of satisfactory delivery, and (badly delayed) user feedback.We'll explain how getting that user feedback early and often dramatically reduces delivery risk and increases user satisfaction. We'll review tips and ideas to change the approach and walk from the term "UAT" safely.

  • Liked David Bujard
    keyboard_arrow_down

    David Bujard - Lightning in a Bottle: Federal DevOps Lessons

    10 Mins
    Lightning Talk
    Intermediate

    The resistance is real in federal programs. We often hold back the power of DevOps by blocking access to production. We’ll see how DevOps leaders bridge the gap in federal delivery, with leadership lessons from lightning.

    Lightning overcomes air’s enormous resistance in short bursts. Government DevOps proceeds in the same way, with significant cultural and policy barriers forming resistance – but also with local champions and moments of alignment that allow DevOps programs to begin to cross that resistance in abrupt, sometimes jagged progression. We'll discuss what helps reduce that local resistance to rapid deployment in federal programs:

    • Breaking governance silos
    • Changing the culture of “No”
    • Decoupling release authorization from deployment authorization
    • Team managed deployments
    • Ongoing security authorization
  • Liked David Fogel
    keyboard_arrow_down

    David Fogel / David Bujard - Four Retrospectives and a Funeral

    45 Mins
    Talk
    Beginner

    Retrospectives are sometimes viewed as stressful and about complaining. Retrospectives should be rewarding and fun! We'll introduce four "games" in a somewhat narrative romantic story (break up, self worth, honeymoon planning, fixing a home). These four games cover internal and external concerns as well as individual and collective (it, I, we, its). We will explain the value of picking a retrospective that fits a team's need. Finally - we will have a funeral for the old ways of doing retrospectives.

  • Liked David Fogel
    keyboard_arrow_down

    David Fogel / David Bujard - Dude, where’s my transformation?? (9 months into a 6 month adoption)

    45 Mins
    Case Study
    Beginner

    Specific organizational patterns are the villains of agile adoption, setting unreasonable expectations and sabotaging progress. We’ll explore these villains, and give real examples how federal organizations overcame them.

    Participants will see the power of metaphor first embraced by Extreme Programming: a system metaphor or (for transformations) a cultural metaphor to name and avoid common anti-patterns in Agile adoptions.

    Leaders in government programs or large organizations will recognize common challenges patterns: setting schedules by fiat, limiting the availability of product owners, balancing responding to emergencies with focusing on consistent prioritizes, just to name a few. Coaches and champions supporting Agile adoptions will be equipped with counter-examples to avoid these challenges.

  • Liked William Strydom
    keyboard_arrow_down

    William Strydom - The intersection of Professional Coaching and Agile – And how it changed me

    45 Mins
    Workshop
    Intermediate

    Are you curious about professional coaching and how it relates to agile?

    What is Professional Coaching? What is Agile Coaching? Come discover how these two disciplines come together to complement each other!

    How well do you listen? Did you know that listening is a coaching skill?

    What is powerful questions and how to use them in Agile facilitation and coaching?

    Learn more about how to become a professional coach, if that is what you want to do, after learning what it is and how it will elevate your agile coaching career.