schedule Oct 15th 02:00 PM - 02:45 PM place Ballroom A people 12 Interested

Ever struggled to define what is minimally necessary? Whether it is defining a Minimally Viable Product or what is minimally necessary for a project or team, you need a way to not only brainstorm ideas, but also a way to cut the unnecessary waste out.

Pass to Perfection is a game for getting a solution, product, or project started with what is minimally necessary; in development terms, this is your Minimal Viable Product (MVP). It mashes up ‘Yes and’ thinking for co-creation, and the essence of The Perfection Game (from the Core Protocols) for negotiation and prioritization in a collaborative round-robin game format. Create ideas until you can’t think of anything else and you pass, remove ideas until you have what is essential and you pass. This workshop will have you try out the game and learn how easy it is to get people started.

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

Outline/structure of the Session

Our session will consist almost entirely workshop; there will be no slides. Here is the flow that has worked so far...

Welcome people and introduce how this was created as a collaboration at the US Agile Coach Camp 2016 (~2 min)

Warm-up Exercise: 101 uses - this allows people freeform creativity around Yes, and... thinking an essential element in the ideation round of the Pass on Perfection game (~5 min)

Describe the arc of Pass on Perfection (~5 min)

  • mash-up of yes and ..., brainstorming, negotiation, a boardgame play or pass mechanic, and the perfection game from Core Protocols
  • describe how it is broken into two rounds - Ideation Round and Perfection Round
  • Run through an example

Break into effective groups if attendees are not set-up that way (~2 min)

[ The details for the rounds can be found at http://tastycupcakes.org/2018/04/pass-the-perfection/ ]

Set-Up Round One: Ideation Round - explain the Yes, and.. concept and the mechanics of adding to the idea or passing (~1 min)

Execute Ideation Round- allow people to round robin add to the idea or pass, normally this isn't timeboxed, so we'll explain in the debrief that this is normally done until everyone passes (7 min - Timeboxed)

Set-Up Round Two: Perfection Round - explain the removal aspect with negotiation or pass (~1 min)

Execute Perfection Round 7 min allow people to round robin propose to remove an idea or pass - negotiating for consensus to actually remove it, normally this isn't timeboxed, so we'll explain in the debrief that this is normally done until everyone passes (Timeboxed)

Debrief (10 min)

  • Share results from 1-2 teams

Ask:

  • What did you learn?
  • How would this help you get the result you want?
  • What effect does this have on helping people get 'heard'?
  • How does this increase a group's psychological safety?
  • What other uses could this be applied to other than an MVP for a product?

Describe other uses the facilitators have had, variations, and point to Tasty Cupcakes site for more info... (2 min)

Q&A (remaining time)

Note to the evaluation team: this session has been presented in 2018 at Path to Agility, Agile Games, Heart of Agile and several meet-ups in the DC and Detroit areas.

Learning Outcome

  • Learn an easy to use activity for defining a minimally valuable product (or any other thing where minimally viable can apply).
  • Learn pointers and tips to facilitate the session through doing.
  • If you have struggled to understand what minimally viable is, we've found this helps people understand the concept better.

Target Audience

Managers, Scrum Masters, Product Owners, Team Members

Prerequisite

It is good, but unnecessary, to understand the concept of 'minimally viable'.

schedule Submitted 5 months ago

Comments Subscribe to Comments

comment Comment on this Submission

  • 45 Mins
    Workshop
    Intermediate

    In our follow-up session to last year’s Kanban in Action: Thoughtfully Observing Flow, we are excited to bring our newest installment of the series: Kanban in Action: Thoughtfully Creating and Discussing Flow.

    This session puts the attendee in the driver’s seat to create their own Kanban board configurations. We provide seven business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique constraints of each scenario. Each team/table in the room will spend a few minutes discussing how they would configure their board using the provided flip charts, markers, and stickies. A debrief with the entire room follows as each team shares its concepts. The instructors will also share their own board configurations and ideas.

    These exercises will increase your understanding of Kanban systems, give you practice interpreting and creating board configurations, present multiple implementable ideas for any given scenario, and provide you with approaches for meaningful engagement. They are great for aspiring coaches, managers, and leaders who want to have more valuable conversations with their teams and improve Kanban implementations.

  • 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 Julie Wyman
    keyboard_arrow_down

    Julie Wyman - Responding to Change over Following a Plan: Agile Lessons from Antarctica

    Julie Wyman
    Julie Wyman
    Agile Coach
    Excella Consulting
    schedule 5 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    I spent January in Antarctica hanging out with penguins, whales, and seals. It was about as different from my day-to-day work as can be. And yet, on my long flight home, I couldn’t help but reflect on how well my trip aligned with one specific value of the Agile Manifesto: “Responding to change over following a plan.”

    Antarctica is a place that truly drives home why we need both planning AND, even more importantly, the ability to respond to change. This trip helped me fully appreciate how true this value is - and not just in software development. And after being stuck in Antarctica six days longer than planned, it also built up my empathy for team members struggling with dynamic situations!

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Please Stop Modernizing!

    Dane Weber
    Dane Weber
    Sr. Consultant
    Excella
    schedule 5 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Executive

    The federal government loves modernizing software systems and it isn't wrong: stale, decaying software leads to major headaches and eventual catastrophe. Modernization efforts, however, have big risks and big failures.

    There is an alternative: software renovation. That is improving, updating, and upgrading the software system one piece at a time while it continues to operate.

    Dane has participated deeply in three US government modernization projects. Each project followed a pattern of pitfalls, scary "go-live" transitions, and unpleasant trade-offs.

    Renovating legacy software is frequently a better option. The software system continues to gain functionality at the same time that its design and performance are improved.

  • Trent Hone
    Trent Hone
    Managing Consultant
    Excella Consulting
    schedule 6 months 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.

  • Trent Hone
    Trent Hone
    Managing Consultant
    Excella Consulting
    schedule 6 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Customers weren’t satisfied! The process took too long! The end product didn’t perform to specifications! Does this sound familiar?

    A century ago, the U.S. Navy’s ship design process had serious problems, ones we would recognize and understand today. Come learn how these problems were solved in a large, real-world, organization through minor changes in structure and process. These changes illustrate the importance of:

    • Gathering early feedback
    • Rapidly iterating to expose unknowns
    • Using multi-disciplinary problem-solving
    • Employing Agile techniques outside of IT
  • Trent Hone
    Trent Hone
    Managing Consultant
    Excella Consulting
    schedule 6 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Are you excited by the idea of Business Agility, but unsure how to create it? Learn new techniques by looking back. In the early 20th century, the U.S. Navy successfully leveraged Agile approaches to harness new technologies, encourage organizational learning, and develop a sustained pace of innovation, all key aspects of Business Agility. Find out how!

    I’ll describe what the Navy achieved, explain why it worked, and illustrate how similar approaches can be used today to create greater Agility in our businesses and organizations. Some specifics include:

    • Fostering innovation by the use of regular feedback.
    • Employing safe-to-fail experimentation.
    • Promoting evolvability through loose coupling and bounded autonomy.
    • Balancing exploration and exploitation to identify and harness new ideas.
  • 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 6 months 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 5 months 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 Allison Pollard
    keyboard_arrow_down

    Allison Pollard / Barry Forrest - Brewing Great Agile Team Dynamics--No More Bitter Beer Face Communications

    45 Mins
    Workshop
    Beginner
    ›Ever find yourself making a sour face after talking to a coworker? Wishing your team meetings felt more like an engaging social hour? There is hope. Those everyday conflicts where something seems “off” after a conversation are often related to differences in communication styles. When team members understand themselves and others, there’s less conflict, more collaboration, and better working relationships. The DiSC model can help you understand why your team behaves the way it does and how to build trust for a more agile team.
    In this interactive session, agile coaches Allison Pollard and Barry Forrest will introduce the DiSC model to explain the four behavior types that are the ingredients in any team, then explore the characteristics of these ingredients and how they react with one another. Join them to learn about the behavior styles of you and your team using DiSC, how to communicate better together, and increase trust in the team. You'll leave with a common language that your team can use to better understand themselves and adapt their behaviors with others.
  • Liked Colleen Esposito
    keyboard_arrow_down

    Colleen Esposito - Simple Agile Design for YOUR Architecture

    Colleen Esposito
    Colleen Esposito
    schedule 3 months ago
    Sold Out!
    45 Mins
    Workshop
    Beginner

    Agile encourages us to eliminate activities that don’t add value and find the simplest solution possible to solve our business needs. For many teams, that can lead to a state where collaborative design no longer happens or is discussed on a whiteboard that gets erased after the conversation.

    How then, can you share the knowledge with team members who don’t work on that feature, or join the team after the feature is built? What about distributed teams, are they unable to have collaborative design because they don't have a whiteboard?

    I had those same questions in 2012, when Ron Garton of the Agile Coaching Network showed me a lightweight solution and we stopped creating traditional design documents. Ron provided me permission to bring that solution to the agile community through sessions like these.

    This solution helps everyone on the team understand what they will create or change in the current systems before it’s built, which can also be retained to increase the domain knowledge for that system later. Though the template itself can be helpful, like many agile tools, it’s the conversation that it starts that’s truly powerful.

  • 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 Wm. Hunter Tammaro
    keyboard_arrow_down

    Wm. Hunter Tammaro - Benjamin Franklin Invented Scrum

    Wm. Hunter Tammaro
    Wm. Hunter Tammaro
    Lead Consultant
    Excella
    schedule 5 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    It’s hard to overstate Benjamin Franklin’s contributions to the world. A true polymath, Franklin is best known for his statesmanship and diplomacy, his scientific insight, and his creation of the Scrum software development methodology.

    Wait, what?

    Okay, Franklin was ahead of his time, but he wasn’t telling us how to build software more than 200 years ago. Yet like the founders of Scrum, Franklin was obsessed with finding better ways to work and shared his productivity strategy in his autobiography. His to-do list is one of the first in the historical record, but the way he used it anticipates Scrum – and Agile principles in general – in many ways.

  • Liked Wm. Hunter Tammaro
    keyboard_arrow_down

    Wm. Hunter Tammaro / Julie Wyman - Limiting WIP: Doing Less to Do More

    45 Mins
    Talk
    Intermediate

    Limiting work-in-progress, or WIP, is a core principle of Kanban, and is a common recommendation to teams using Scrum or other frameworks as well. Yet the idea that working on less can lead you to get more done seems to defy common sense. Even those who understand the reasons for limiting WIP can struggle with resistance from team members or leaders when putting the theory to practice. This talk will review the concept of WIP and explore in depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Attendees will also participate in a short simulation that will illustrate the concepts in practice, and that attendees can use on their own projects to help overcome skepticism of WIP limits in their organizations.

  • Liked Sean Killeen
    keyboard_arrow_down

    Sean Killeen - (fr)Agile: How Agile Falls Apart, and What you can do to Hold it all Together

    45 Mins
    Talk
    Intermediate

    Attempting to deliver a project and maintain an agile mindset at the same time can feel fraught with peril. Unforeseen circumstances, the challenges of working in team of actual human beings, and organizational inertia act like riptide currents, pulling you away from your delivery, your team's commitment to agile principles, or both.

    All is not lost! In this talk, I'll describe some symptoms of agile dysfunction and their antidotes. We'll explore some lessons I've learned as a technical lead working with agile and "agile" teams, holding it together with duct tape and a little help from my friends.