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

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

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

Outline/Structure of the Talk

1. Getting Started

  • Introductions: speakers & learning objectives
  • Warm Up: product backlog pop quiz!
    • Used to gauge the current state of your product backlog

2. Why Tidy Up?

  • Simplicity is a key principle behind the Agile Manifesto
  • Costs associated when operating without simplicity
    • Mental overhead/load
    • Can't distinguish between what is and is not important
    • Makes prioritization and decision-making more difficult
  • Simplicity supports self-organization
  • Clutter creeps up, so teams should make a mindset shift now

3. How does this work for a Product Backlog? How Do I Start?

Note: We will share real examples of doing this with a team or in our personal lives throughout each of these steps.

  • Step 1: Use your product vision as a guide (create one, if you don't already have it)
  • Step 2: Find all PBIs and put them in one place (uncover any "unofficial backlogs" or separate lists)
  • Step 3: Sort by category (sort to help make sense of what you have)
  • Step 4: Start simply (practice with easier items first to build up tidying skills)
  • Step 5: Keep what "sparks joy" (similar to "delight the customer", ok to let go of some "good" ideas)
  • Some practical tips...
    • Decide to keep or discard first - then worry about refining
    • Be respectful when discarding PBIs
    • Really let things go - don't pass PBIs off on to other teams

4. Some Thoughts on Storage…

  • The goal of any product backlog "storage" system should be to increase visibility in order to empower self-organization and facilitate decision-making
  • Similarities between Marie Kondo's "vertical folding" technique and story mapping
  • Decluttering Sprint/Kanban board and user story detail views
  • Use INVEST as a guide for the backlog items you decide to keep
  • Don't become a storage expert (the tool isn't important, keep it simple)

5. Next Steps & Wrapping Up

  • Discussion / call to action: What can you apply from today to improve your team's score on the product backlog quiz?
  • Additional resources
  • Recap key points and learning objectives

Learning Outcome

1. Describe the costs of maintaining a large, cluttered product backlog
2. Explain the benefits of simplicity and how it relates to the product backlog
3. Understand how to apply the KonMari tidying up method in the context of a product backlog and the steps to take to get started
4. Describe how to “store” product backlog items to increase visibility, empower self-organization, and facilitate decision-making

Target Audience

Any team member or stakeholder, but especially Product Owners, Business Analysts, and Scrum Masters

Prerequisites for Attendees

No advanced knowledge required, but a high-level familiarity with the concept of a Product Backlog will be useful.

schedule Submitted 3 weeks ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Mathias Eifert
    keyboard_arrow_down

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

    45 Mins
    Talk
    Intermediate

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

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

  • 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 Zack Ayers
    keyboard_arrow_down

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

    45 Mins
    Talk
    Beginner

    Summary

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

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

  • Liked Thomas Stiehm
    keyboard_arrow_down

    Thomas Stiehm - Shifting Security Left - The Innovation of DevSecOps

    Thomas Stiehm
    Thomas Stiehm
    CTO
    Coveros, Inc.
    schedule 3 weeks ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    DevSecOps uses application security practices that have been around for a while. The innovation of DevSecOps is incorporating security into the daily workflow of the team rather than leaving them to the end of a release like many legacy processes do. Shifting security left is made possible by the ability to automate many aspects of security testing and verification. DevSecOps leverages DevOps practices to make application security a first-class citizen in the practices of modern software product development. DevSecOps starts with a culture change mindset of cross-functional teams creating software through collaboration and fast feedback cycles.

    The security in DevSecOps starts before the code is written by using techniques like threat modeling and risk analysis to help figure out who might want to attack you and how they might do that. This often ignored security practice can be enabled by following the DevSecOps practices of having a cross-functional team involved in the process from the beginning, including security professionals.

    Next, DevSecOps maps application security practices into the build pipeline for a project in order to provide quick feedback about the security posture for any change made to the software. By using automation to allow the team to move quickly while maintaining confidence in the health of the code base, DevSecOps extends that health check to include application security checks. While automation can be used to make security data collection easier it is important to understand what security practices still require a human being.

    This talk focuses on how, when, and where practices should be incorporated into a build pipeline to get the most value out of your security practices through automation. It explores what manual security work still needs to be done by a person and how to maximize value while minimizing the effort of human beings.

  • Liked Dave Rooney
    keyboard_arrow_down

    Dave Rooney - #NoProcesses - Getting More Done By Doing Less!

    45 Mins
    Tutorial
    Intermediate

    You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those concepts challenge the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban or XP - let alone SAFe, LESS, NEXUS, DAD - in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?

    This session examines the two key principles common to all successful software delivery approaches and builds out based on the experience of the participants. Like #NoEstimates and #NoProjects, the name doesn’t really mean to eliminate process altogether, but rather to build a process that works for your team, in your business domain, with your technology stack.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Agile Leadership 201: Enriching Management

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 weeks ago
    Sold Out!
    45 Mins
    Tutorial
    Executive

    The Agile Manifesto doesn't explicitly talk about what changes in management should happen and neither do the approaches. In fact, sometimes we hear the exact opposite from teams - "What do we need managers for..?" or perhaps "Can't they just get rid of all the impediments we have?"

    As a former manager and now as a coach, I find the words Servant Leadership sometimes doesn't resonate. It actually only paints part of the picture anyway. What we want are ways to enrich management so that they can do more for the organization and its teams. Let's discover what some of this enrichment might be.

  • Liked Nicole Ward
    keyboard_arrow_down

    Nicole Ward / Brandon Raines - Self Care Tips and Practices for the Agile Mind: From a Therapist and Coach

    45 Mins
    Workshop/Game
    Beginner

    In order to be an effective coach, it is important to maintain and sharpen your core tool, you.This means attending to every aspect of you including mental health. Practicing good mental hygiene through self-care is one way to maintain an agile mind.There are no set rules for practicing self-care but it is important to establish some markers for how you continue to nurture your relationship with self. Unfortunately, many of us don’t recognize this need.We simply jump from event to event or engagement to engagement without ensuring we are whole, present and charged.This despite one of the essential values of Agility being, ‘maintaining a sustainable pace’.It doesn’t just apply to the teams we are coaching, but for the coach as well.

    Come hear self care techniques from a practicing Agile coach and a practicing therapist?Join us as we explore practical self care practices applied to the Agile principles and typical stressors that show up while we partner with organizations to grow.Our hope is the workshop will provide an experiential space for participants to gain tools to kick start or add to their mental and emotional wellness regimen.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos / George Paci - DevOps Your Organizational Change

    45 Mins
    Workshop/Game
    Intermediate

    DevOps has become all the rage from a technical change perspective; it really has changed the game. And while it provides numerous benefits, only after you also embrace the human side of change within the organization, can you really get to full Agility.

    What if we could take advantage of a continuous delivery of change just like we do in our development pipelines? As executives, managers, Scrum masters, coaches, or anyone else in a leadership role, we should desire to make each change focused, easy, and small to contain risk. Once this is done, changes can mimic a development pipeline that delivers towards a business outcome. This workshop will help you learn how to keep the number and size of changes in check and consider how to manage the risks of deploying change.

  • Liked Anita Sagar
    keyboard_arrow_down

    Anita Sagar - Making Sense of Agile with the Cynefin Framework

    45 Mins
    Talk
    Beginner

    “We are going agile!” This seems to be a statement often used in an effort to streamline existing business practices in favor of more efficient and customer-focused processes. However, before we make a paradigm shift in our day to day business activities, it is important to recognize the context in which we currently situate ourselves, and make the right decisions based on that context. Dave Snowden’s Cynefin Framework helps us visualize and understand that not all situations and/or challenges are created equally. Using this framework can help us make sense of the context we are in so that we can not only make better decisions, but also avoid the problems that arise when our preferred management style causes us to make mistakes.

  • Liked Alan Deffenderfer
    keyboard_arrow_down

    Alan Deffenderfer - 10 BFCs (Big Freaking Charts) You Can't Live Without

    45 Mins
    Experience Report
    Beginner

    Are you a Scrum Master struggling to get your organization to change?

    Do your teams work in technically challenging environments where waiting and delays are common?

    Are your teams highly matrixed, highly distributed and/or use email as primary form of communication?

    Are your teams constantly faced with unrealistic, fixed-scope deadlines?

    Do you have unplanned work coming into every one of your sprints?

    This session will give Scrum Masters 10+ BFCs to address common challenges (above) in implementing Agile in the Enterprise.

    The BFCs propose ways of putting a monetary cost to organizational (or team) waste to highlight the importance and urgency of eliminating the waste.

    With each BFC, I will poll attendees for questions, improvements and/or alternatives.

  • Liked Alan Deffenderfer
    keyboard_arrow_down

    Alan Deffenderfer - Detecting Agile BS in the Department of Defense

    45 Mins
    Experience Report
    Intermediate

    I am currently a contractor and Scrum Master at the Software Engineering Center (SEC) of the U.S. Army. Since 2013, I have helped the Army Research Lab (ARL) and am now helping SEC implement Agile/Scrum at Aberdeen Proving Ground (APG). Our SEC contract is currently up for re-compete. This session will give participants a window into real world Agile contracting in the Department of Defense (DoD) using language from the current Request for Proposal (RFP) for our contract.

    If you work in a "highly matrixed," command and control organization driven by deadlines where contract language matters, then this session is for you.

    I can't promise you the "secret sauce" of making Agile work in the DoD, but I will share the challenges we face and the patterns we are using to nudge the organization toward Agile.