What happens when 25 product owners, developers, and quality engineers reflect on their previous sprint through the eyes of a child?

Playdoh took my teams, remote and collocated, from showing up to an obligatory meeting on their calendar to intentional interpersonal and intrapersonal dialogue.

Between the carpet and the sticky fingers, adults are usually cleaning up more Playdoh than playing with it themselves. Even to my own surprise, in this “Play Retro,” our team members connected, not only on a professional, but also on a personal level in ways they had not done before.

This session will give an overview of our experience using a “Play Retro” and leave you with tips and things to consider planning a retrospective.

 
4 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Lightning Talk

  • 00:00–00:02 - Intro – Who am I?
  • 00:02–00:08 – Play Retro method and Experience
  • 00:08-00:09 – Things to Consider when planning a Play Retro
  • 00:09-00:10 – Conclusion

Learning Outcome

  • Learn at least one example of "Play Retro"

  • Tips/Things to consider when setting up a "Play retro."

  • Reminder of the purpose of a retro.

Target Audience

Anyone planning a retrospective

Prerequisites for Attendees

Attendees should have basic knowledge of what a Retrospective is.

schedule Submitted 1 month ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Jeff Dalton
    keyboard_arrow_down

    Jeff Dalton - Big Agile is Coming: Will Technology Leaders Blow it?

    Jeff Dalton
    Jeff Dalton
    Chief Evangelist
    Agile CxO
    schedule 1 month ago
    Sold Out!
    45 Mins
    Keynote
    Executive

    2019 will be the year of Big Agile, where large adopters like General Motors, the Department of Defense, the State of Michigan, Lockheed Martin, and others, who have combined IT budgets exceeding 100 Billion dollars, have all announced their desire to “go agile” at a scale not yet seen in our community. Are technology leaders who cut their teeth in a low-trust, command-and-control, high-documentation environment prepared to make a successful transformation? What will Big Agile look like, and how will it affect the rest of the community?

    This will be our industry’s biggest challenge, and I've been studying it for years. As the large adopters in the federal government and corporate sector begin to adopt agile, they’ll bring their habits, culture, and bureaucracies with them, and they need to get in front of the wave.

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

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

    45 Mins
    Talk
    Beginner

    Government Agile transformations can feel like overwhelming efforts – but do not abandon hope! This interactive, audience-driven presentation reviews how government and large organizations ESCAPE common Agile adoption challenges.
    You - the audience - will prioritize your pain points; we’ll focus on the five Agile hells most highly prioritized. We will discuss real examples of “escaping” out of each Agile hell, with pro tips and success patterns you can apply.
    The Agile hells we've escaped include:

    • No Transformation hell - A federal program or department wants to change but can’t start or can’t finish
    • Too Fast hell - Newly Agile federal programs sometimes respond TOO rapidly, too often changing priorities.
    • Technical hell - Programs can become bogged down in technical debt and manual processes.
    • No Trust hell - Government delivery can be slowed by lack of trust between contractors and feds, between business and IT, or between compliance and delivery groups.
    • Product Owners hell - Government Product Owners can be unavailable, think they are managers, aren’t empowered to provide vision, or struggle with prioritization
    • Too Big hell- A frequent pattern in federal Agile! Large batches produce slow progress, low visibility and high complexity, seen in big programs, big deployments, and big contracts.
    • Collaboration hell - Government teams can struggle with collaboration within the same organization across roles and across the fed-contractor divide.
    • Stove-piped hell - Government organizations can struggle to collaborate across contractual or organizational boundaries within the same enterprise
    • Leadership hell - An organization can only be as agile as its leadership. In the government, how can you work with leaders who aren't ready to be agile?

    For each Agile hell, we focus on successful techniques to escape from these common dynamics. Unlike other presentations, we won't be doing a deep dive, but we will cover the most important challenges our audience face.

  • 45 Mins
    Talk
    Beginner

    On average Agile transformations get into trouble at about 14 months from the time they start. Have you ever wondered why?

    Is it because you started from 'the bottom up?" Or is it because you spend time, money, resources and people creating great teams and didn't pay attention to having a professional, empowered Product Owner organization?

    Agile transformations that target department level and not the organization have a very low success rate and you end up with an agile department enveloped by a traditional organization. That leads to dark work, decision delay and dysfunction.

    So, what can you do?

    Come and learn some of what I learned the "hard way" over 7 transformations.

  • Liked Glenn Buckholz
    keyboard_arrow_down

    Glenn Buckholz - Moving Your Pipeline to Kubernetes, Things I Wish People Had Told Me

    Glenn Buckholz
    Glenn Buckholz
    Technical Manager
    Coveros
    schedule 1 month ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    Kubernetes married with a cloud provider elastic, highly available infrastructure. Many CI engines today (Jenkins, Bamboo, Gitlab, CircleCI), provide native integration with kubernetes so that your build and deploy workload can be elastically executed. This allows your pipeline to meet the needs of your schedule, be it the 4pm pile on to commit code before going home, the mad rush to get a hot fix to production, or the surge of an unexpected customer ask. Gone are the days of the build queue growing and you CI engine collapsing under the weight of a hundred build requests. In order for a pipeline to leverage this capacity changes must be made to the pipeline architecture. Tools must be dockerized, the ephemeral nature of running docker must be considered, kubernetes specifications or helm charts must be generated for the application, automated testing must be adapted to work in the new architecture, and then there is the database. Each one of these issues, plus many others I’ve missed contained unfortunate, unforeseen pitfalls that translated in schedule delays. Join Glenn as he helps you short circuit the pitfalls of migrating to kubernetes off of your static in-elastic virtual infrastructure.

  • 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 6 days 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 David W Kane
    keyboard_arrow_down

    David W Kane - Hang Out with the DevOps Folks!

    10 Mins
    Lightning Talk
    Intermediate

    One of the things I like about AgileDC is that I see a lot of familiar faces. Not just familiar from previous AgileDC events, but from other Agile events in town, other conferences, Meetups and such. I also go to local DevOps events, and I see familiar faces there too, but I don't observe much overlap between the two. In this talk I will discuss whether this division is real, or perhaps just a figment of my imagination, whether we as an Agile community should care, and what we should do about it.

  • Liked Brian Segel
    keyboard_arrow_down

    Brian Segel - Common Organizational Impediments to Enterprise Agility

    10 Mins
    Lightning Talk
    Intermediate

    As Agile coaches engage in enterprise transformations, there is a common theme among the organizational barriers and impediments we see across most clients. While each client has a unique piece to it, the approach to these common issues can be somewhat standardized. The approach and consistency helps show how we as coaches provide value and help organizations move past these impediments.

  • Liked Derek Huether
    keyboard_arrow_down

    Derek Huether - 10 Steps to Better Outcomes by Using Metrics

    45 Mins
    Talk
    Beginner

    This session is not intended to offer an exhaustible list of metrics or instructions on how to improve all systems. Rather, the intent is to provide a framework on how to ensure the quantitative and qualitative metrics you use are measuring the right things and how to apply them to a system of continuous improvement. Attendees will have a repeatable framework they can apply after leaving the session.

    The session is broken into two main parts.

    • Part 1: Identify the right (quantitative and qualitative) metrics that will help people and teams meet outcomes or goals.
    • Part 2: Create a cycle of learning and improvement that aligns people and teams to the outcomes or goals.
  • Liked Megan Windle
    keyboard_arrow_down

    Megan Windle - The Art of Agile: The Art of War Interpreted with an Agile Lens

    45 Mins
    Talk
    Beginner

    What do Agile and War have in common? More than you might think. When you think of war, think of it as a problem to be solved. Now, think about Agile. Agile is a way of working and thinking to collaboratively solve problems and figure things out you go.

    Sun Tzu’s “The Art of War” is a book of wisdom and strategy for warriors. But don’t be fooled. The book contains lessons that go far beyond the battlefield. Lessons for Agilists can be found within the text, when interpreting the words with an Agile mindset. The importance of planning, self-governance, and just-in-time information are a few examples of lessons that apply to both War and Agile.

    If you want to discover the golden nuggets of Agile wisdom found in this ancient text, bring your agile mindset and join me to interpret “The Art of War” through an agile lens.

  • Liked Tyler Grant
    keyboard_arrow_down

    Tyler Grant - Words Matter: Building Trust and Dropping Jargon to Create Stronger Teams

    Tyler Grant
    Tyler Grant
    Scrum Master
    Capital One
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Within the Agile and technology communities, it can be easy to assume that the language we use every day is common knowledge and shared throughout our professional spaces. Certainly when we interact with other professionals and hear them using the same terms, this just reinforces our assumptions. Especially when we leave the boundaries of technically specific language and enter the realm of jargon or “buzzwords” it can be easy to find validation through other people’s language preferences.

    However, using this type of language can not only create divisions within our teams, it can obfuscate meaning, delay action, and create misunderstandings that can inhibit a team's ability to deliver. By examining the differences between jargon and technical language, we will look at how this use of language can create in- and out- groups and break down trust within an organization.

    By committing to using broadly understood language and being direct in the way we interact with each other, we can improve our ability to perform at a high level in the fast paced technology space.

  • Liked John Tanner
    keyboard_arrow_down

    John Tanner - Using Metrics for Good not Evil or: How I learned to Stop Worrying and Love the KPIs

    45 Mins
    Workshop/Game
    Beginner

    Using metrics for punitive reasons is a problem as old as time. In software, this is further complicated by the fact that people rarely agree on why we are collecting metrics in the first place. In this session we will explore how we can use metrics for good instead of evil.

    By focusing on the goal of system improvement, rather than individual performance, we can begin leveraging data to make a positive difference in how we work while also delving into why we work the way we do.

    This session will include real-world examples of problems that organizations create for themselves by using metrics for the wrong intent. We will also discuss examples of good metrics and how they can be used to make our lives better.

  • Liked Ben Morris
    keyboard_arrow_down

    Ben Morris - Agile Isn't Enough for Government Transformation

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 1 month 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 Itopa Sulé
    keyboard_arrow_down

    Itopa Sulé - What NOT to do when prioritization fails

    45 Mins
    Workshop/Game
    Intermediate

    One common mistake by new Agilists is to think that the product backlog is a linear list with the highest priority item on the top. As it's often the case, the reality is different. Prioritization is neither binary nor linear. Your team will be asked to work on several competing priorities, like meeting the new regulation while working on the next product milestone (the product is the company lifeline) - and your product owner will insist these are both top priority!!

    In this workshop we are going to explore different tools, to ensure that our teams are working on the highest value backlog items: from Eisenhower Method to Cost of Delay, CD3 and modified Weighted Shortest Job First (WSJF).

  • Liked Ben Morris
    keyboard_arrow_down

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

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 1 month ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    Most government agencies are becoming 'agile'. A few are actually diving in to focus on frequent delivery of software that creates business value. This is not about 'agile' the easy way - implementing a few ceremonies, titles, and buying a software package, then declaring victory. This is about agile the hard way - the stubbed toes and small victories that open the door to lasting change.

    The talk walks through lessons learned from a specific government project, jumping head-first into agile, open source, and (oh dear) the cloud.