Icebox Zero: Agile UX and the Lean Backlog
One of the most disregarded principles of the Agile Manifesto is one of the most important: Simplicity—the art of maximizing the amount of work not done. Simplicity seems simple enough, but in reality it’s as complicated as the work we are so often asked to deliver on—work that we may ultimately find was not worth doing. This session explores the complexities of this sort of counter-intuitive workstream optimization, with low-effort tactical approaches to preventing such waste in software and product development. The session attempts to codify the things teams need to do to truly execute on simplicity, and as a bonus, fulfill what is likely the most important principle of the Agile Manifesto: satisfying the customer.
Outline/Structure of the Talk
Session Flow & Timings
This session is the outcome of a year of collaboration and exploration between Justin & Scott on the topic, which was birthed at Agile 2018.
After numerous encounters with teams that produced countless hours of wasteful development work, often resulting in bloated product functionality the bulk of which has gone over gold plated and underused, we decided it was time someone take a stand to remind everyone that it doesn’t have to be this way!
===== Introductions: 2 Minutes =====
- Who is Scott
- Who is Justin
- Topic origination - Agile 2018
===== Optimizing for Work Not Done (Long Lost Agile Manifesto Principle): 2 Minutes =====
- Manifesto origins
===== What is an Icebox - Value of Icebox Zero: 3 Minutes ====
- Pivotal Icebox - unprioritized backlog items - Backlog is not a dumping ground for ideas
- Icebox Zero
- Optimize Work Not Done
- Determine Customer
- Value of Edge Cases
- Prioritizing Work
===== Beautiful Airplane: 5 Minutes ====
- Activity they can take back to work, to prove the likelihood that most ideas will fail
===== Prevention & Practice: 2 Minutes ====
- Why afraid to lose ideas?
- Margin to Fail
- Local Maximum Trap
===== Delete Something: 5 Minutes ====
- Ask audience to delete something off their phone or computer
- An app
- A photo
- A reminder
- An alarm
- A tab
- An Email
- Live Menti Survey / Word Map of Items Deleted
===== Cost of a Backlog: 2 Minutes ====
- Queue of work adequately scoped - inventory
- Value of Information
- Cost of Definition of Ready
- Last Responsible Moment
- Finite Tasks
====Alternatives: 2 Minutes ====
- What to do if we cannot plan our work months in advance?
- Whole Team
===== Write Stale Feature: 5 Minutes ====
- Prime audience for elimination of waste backlog items / features by asking each one to write down at least one item to be thrown away
===== UX Experiment: 3 Minutes ====
- Form a hypothesis
- Build / Measure / Learn
- 3 Days
- Evolving Landscape
- Currencies of Genuine Product Validation
- Determine Extreme Pain Around the Problem
===== Prototyping: 2 Minutes ====
- Action Effect Loop
- Throw It Away
===== Rapid Prototyping: 5 Minutes ====
- Low fidelity prototype creativity exercise
===== Meet Del: 2 Minutes ====
- Collect stale backlog items
- Place into the backlog dumpster, Del
===== Debrief: 5 Minutes ====
- One Question: “What learnings will you take with you back to work?”
- Generate value by embracing Lean UX in an Agile environment—practicing the art of maximizing the amount of work not done.
- Judge the overall systems cost of unhealthy backlogs.
- Use experiment patterns to invalidate the wrong ideas.
- Instill a true sense of purpose and passion in our team members through customer-centered empathy & team autonomy techniques.
Beginner to Intermediate Agilists, Anyone Struggling With Big, Complicated Backlogs Filled With Questionable Items
Prerequisites for Attendees
schedule Submitted 3 months ago
People who liked this proposal, also liked:
Colleen Esposito - Beyond Prioritization: How to Make an Impact for your CustomersColleen EspositoAgile CoachAssurant
schedule 4 months agoSold Out!
If you’ve been exploring agile methods, you probably want to deliver the most value in the least amount of time possible. But what if the best prioritization and planning just isn’t enough to keep your organization at the top of your market?
Enter Impact Mapping, an approach that reveals the hidden assumptions that keep you from reaching your goal. This technique helps when you're looking for innovative solutions to tough business problems because you'll bring in strategic thinking skills as you identify the ones most likely to reach your goal. Even better, you'll know upfront how to measure the impact of those solutions, so you won't invest more than you need.
This workshop is hands-on, so get ready to learn while you’re working!
John Hughes - Improve Your Agile Transformation Success by Applying the Lens of Spiral Dynamics Integral (SDi) and AQALJohn HughesSenior Director, Agile PracticeSevatec
schedule 3 months agoSold Out!
Changing the practices, behaviors, and beliefs of people and teams is hard; and organizations are many multiples harder. As agilest, we are educated to seek and deliver value. But that is one of the first big issues. What are the chances that we can know what is truly valuable for the people within the team or organization, both individually and collectively?
Another big issue is that most agilists are well-educated in frameworks, practices, and tools, but our training doesn’t generally prepare us for the other aspects imperative to implementing lasting agility and change. There is little focus in our standard training on the impact of systems and structures, and even less on internal aspects such as morals/ethics, ego, psychology, and culture.
I would like to present to you two models which opened my eyes over the past 6 years to a much larger awareness and understanding of how to approach agile transformation for impactful lasting change, and show you how to apply them to your work efforts. Seeing people, teams, and organizations through the lens of these models has greatly changed my understanding and approach and I believe has strongly benefited the outcomes of my efforts.
Spiral Dynamics Integral (SDi) is a bio-psycho-social developmental model showing itself through color bands representing levels of increasing inclusive evolution. AQAL – All Quadrants, All Levels [All Lines] – models a set of quadrants depicting our internal and external, individual and collective attributes and aspects. Woah! Don’t be thrown by that crazy-sounding stuff. Stick with me.
While those models might not sound very applicable to decreasing your cycle time to deliver your latest microservices through your fully-automated DevSecOps pipeline, without awareness of these models, you may never actually lead your team(s) to the point of decreasing cycle times, much less get your organization to the point of benefiting from DevSecOps practices.
Please join us for this session as we explore how these models allow us to be more successful in our work as Scrum Masters, Coaches, and/or Leaders. Benefit from learning new ways to see your system, avoiding and removing challenges and impediments you face in your sluggish, stuck, or failing agile journeys. Begin to see the world in a whole new way, not just at work, but in all aspects of life.