At home and work, how to get more stuff done. An introduction to Personal Kanban

With a world of constant distraction, it feels like it’s getting harder and harder to get stuff done, regardless if it’s on a personal or organizational level. At some point, we’ve been sold the lie that multitasking is great and maximum utilization is even better. If we all agree with that, why are we doing more and getting less done? If there were a relatively simple way for you to get more stuff done, wouldn’t you want to know what it was? If there were a way for you to measure and improve your processes over time, wouldn’t you want to know how to do that as well? When getting stuff done is a primary measure for success, we need to introduce people to concepts that are simple but can be leveraged at scale.

In this session, participants will be introduced to the principles of Lean and the application of Kanban to visualize their personal work, limit distraction and waste, and get stuff done. I’ll cover the core concepts outlined in Jim Benson and Tonianne DeMaria Barry's book, Personal Kanban, to get you started. I’ll talk about how Kanban can be applied to everyday work and why you should do it. 

Through my years of struggling with ADD/ADHD and my years of management, leadership, and coaching, I have learned and applied Personal Kanban techniques in my everyday life and Lean Kanban at both government and private organizations. This is your opportunity to learn a few simple strategies that you can start using before you even leave AgileDC. This workshop can help you map your work and navigate your life.

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

Outline/structure of the Session

  • Introduction [20 minutes] (20 minutes elapsed)
  • Practice Board 1 [10 minutes] (30 minutes elapsed) Round 1 / Our first board
  • Retrospective 1 [5 minutes] (35 minutes elapsed) What worked and what didn’t?
  • Practice board 2 [10 minutes] (45 minutes elapsed) Round 2 / Our second board design
  • Retrospective 2 [5 minutes] (50 minutes elapsed) What worked and what didn’t?
  • Conclusion and Questions [10 minutes] (60 minutes elapsed) What are the next steps?

Learning Outcome

  • Understand key definitions and terms of Lean and Kanban
  • Understand how to apply Kanban to your personal and professional life
  • Understand how you can measure and improve your processes

Target Audience

Everyone

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  3 years ago
    reply Reply

    I like this except for the "drinking Kool-Aid" reference.

    • Derek Huether
      By Derek Huether  ~  3 years ago
      reply Reply

      Duly noted. I toned it down, replacing the phase with "If we all agree with that".  


  • Liked David Bulkin
    keyboard_arrow_down

    David Bulkin - Build Righter Stuff with HDD (Hypothesis Driven Development), a.k.a., HDD is TDD for the Business Case

    David Bulkin
    David Bulkin
    Managing Director
    Grow-Lean LLC
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    With TDD (Test Driven Development) a coder writes a small test, and then just enough code to make the test pass, cleaning up the code along the way.  Imagine applying the same concepts to the business case.  Now stop imagining and use HDD (Hypothesis Driven Development) to test your business case and refactor it for success.

    Our hands on session will cover the basics of ATDD (Acceptance Test Driven Development) and BDD (Behavior Driven Development) to specify by example, so all stakeholders get on the same conceptual page, developers build what the business really wants, and testers can prove it. 

    But building what we want it not enough, so we will go further and use HDD to validate, or invalidate, business outcomes, focusing us on value instead of on adherence to specification.

    This is a hands on session, so come with pen, paper and a readiness to learn by doing!

  • Andrea
    Andrea
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Project success =  f (listening, feedback, intentionality, practices) 

    To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

    Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

    This is a hands-on, try it out, concrete practice session.

  • Liked John Hughes
    keyboard_arrow_down

    John Hughes - Testing Inside Your Timebox: Death to the Hardening Sprint

    John Hughes
    John Hughes
    Director and Agile Coach
    Sevatec
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    Testing sprints? Hardening sprints? Why do so many of us have these and other ways to get around completing all our required testing inside our defined timeboxes? Isn’t our goal to produce deployable features at the end of every Sprint?

    During our session, we will examine why it’s so hard to accomplish all necessary testing inside the iteration and show how to complete these tests within your timebox. Through interactive discussion and real world examples, we will provide insights on foreseeing, overcoming, and avoiding your hurdles and send you home with both long term methods and short term actions that will yield tangible results in achieving your goal.

    Our session will:
    • Illustrate the value of completing all of your testing inside your timebox
    • Identify the challenges in completing all these tests in such as seemingly short period of time
    • Discuss ideas and options to successfully overcome these challenges
    • Explore how to enable your organization and environment for efficient, rapid testing
    • Discuss real world examples of enablement and how we navigated the pain points of enabling testing processes that allow complete testing within an iteration
    • Explore DevOpsSec and how achieving testing within your timebox is a precursor to DevOpsSec
    • Provide short term tactics and actions to immediately improve your ability to complete your testing
    • Allow you to voice your concerns and challenges and discuss potential solutions to these impediments

    Most of us implement agile to reduce the time to deliver valuable working software and to increase the frequency of delivery with high quality through increased and earlier collaboration, shorter feedback loops, and reduced risk. While you can show improvement over Waterfall by performing typical agile methods, you cannot really live the dream without optimizing your agile execution.

    You will leave this session armed with the right knowledge to improve delivery on your current project or start your new projects properly so that you or your clients can reap the benefits of efficient process and high-quality software capable of achieving continuous deployment of fully-tested code at the end of each iteration.

  • Liked Dan Neumann
    keyboard_arrow_down

    Dan Neumann - Principle-Centered Agility: Your Path to Better Options

    Dan Neumann
    Dan Neumann
    Agile Coach
    AgileThought
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Do you want to have a high functioning Agile team? If so, this session is for you! We're going beyond the rules of agile frameworks and learning to apply those principles to improve our teams and companies! The 12 principles of the Agile Manifesto capture the reasons we are able to deliver better software. This is the "why" for some of the rules behind Scrum and Kanban. The principles ought guide our decisions about practices, scaling, and solving tricky problems!

    In this session, we will use the 12 Principles of the Agile Manifesto as our foundation. Then, we will  apply techniques such as Force Field Analysis to apply the principles to your challenges at work. Lastly, we will use principles of change management to make the change more likely to stick.

    The outline for the session is:

    1. Explore the principles; which ones are present or absent in your environment?
    2. Introduce Force Field Analysis
    3. Use Force Field Analysis to explore what drives a specific behavior
    4. Use the Agile Principles to generate new options for tackling your team's challenges
    5. Explore effective change management techniques

    With these five activities, you will leave with a framework for change to apply when you return to work and continue on your agile journey.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    So what does Collaboration really mean?  It's just ensuring people understand what each other is doing right?

    The Power of 13 Collaboration Game illustrates what true collaboration means.  We'll do work by rolling dice over a 3 week Sprint. We'll then explore the results and start our next Sprint. In each Sprint, we're going to increase the participation across players and see what the effect is on productivity.  Prepare to be surprised!

    Should there be enough time remaining in the hour; we'll then specifically apply true collaboration to better understand the effects of pair programming by playing Pair Poetry.  This simulates the power of pair programming and demonstrates why the one screen, one keyboard concept works.

  • Jason Tice
    Jason Tice
    Agile Coach
    Asynchrony
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Agile and Lean principles call for teams to delay decisions and activities until the “last responsible moment” so as to minimize rework and waste.  While this sounds good in concept, sometimes teams fall victim to waiting until it is “too late” to make a decision or get started on a needed activity resulting in missed opportunities and/or down-to-the-wire heroic efforts to meet a deadline.  This workshop entails a competitive LEGO simulation where participants will divide into small teams, each team will be given the same simple LEGO build challenge, and then each team will be able to conduct their own experiments as to when the “last responsible moment” really is.  Following the LEGO build challenge, participants will engage in a debrief to discuss the outcome of the challenge, identify factors that helped to successfully identify the last responsible moment, establish linkages between the LEGO simulation and agile software development activities, and of course congratulate the winners of the challenge.  During the debrief, participants will complete a debrief worksheet to reinforce key learnings and takeaways from the simulation that they will be able to take with them from the session.  Best of all, this is a LEGO session, so you will get to play with LEGO and fun will be had by all!

  • Liked David W Kane
    keyboard_arrow_down

    David W Kane - Making Movies and Software at the Speed of Thought!

    60 mins
    Workshop
    Beginner

    Director Robert Rodriguez (Spy Kids, El Mariachi, Sin City) is an Agile Director. He enjoys making highly creative movies quickly and cheaply. His ambition is to make movies at the speed of thought. To achieve this goal, he works in small teams to develop the ideas, visualize them quickly, shoot the movie fast, and build the movie in layers. This workshop will introduce Rodriguez's approach to film making by screening several of his 10 minute flick school featurettes and we will explore how these techniques translate to Agile software development in a lively group discussion.

  • Liked Philip Rogers
    keyboard_arrow_down

    Philip Rogers - Lean Coffee: Creative Uses of this Technique to Rapidly Surface Ideas and Encourage Team Collaboration

    Philip Rogers
    Philip Rogers
    Scrum Master
    NPR
    schedule 3 years ago
    Sold Out!
    30 mins
    Workshop
    Intermediate

    Lean Coffee is frequently used in meetup and conference settings. The beauty of Lean Coffee is its simplicity, and it is this very simplicity which makes it an appealing choice in various Agile team contexts. Specifically, Lean Coffee is particularly good for ad hoc training sessions and for retrospectives. The focus of this workshop will be on the use of Lean Coffee in these two types of settings, where we will split up into small groups and practice using Lean Coffee to cover ad hoc training topics and to do a mini-retrospective.

     

  • Liked Matt Badgley
    keyboard_arrow_down

    Matt Badgley - Yes, Words Really Do Mean Things - Establishing a Shared Language

    60 mins
    Workshop
    Intermediate

    During this conference, within the books we read, in our day-to-day lives -- we use words as a means to negotiate, interact, express, and do. Words, whether written or spoken can play differently based on the people that exchange them. In the world we are living today, words are bantered so freely that they cause a war or unite a community or save a marriage or demoralize a team.

    As we see today, the concepts of agile are permeating the enterprise and scaling out from the team to the program management office to the executing chambers. Words are often mis-used, mis-understood, and lead to bad behaviors.

    In this session, we'll discuss the general challenges of communications and the overwhelming vocalbulary that we have embedded in our craniums.  We'll explore words -- in particular, the words we use everyday around software development. We look at how some of the basic words we use like Velocity, Sprint, and Team have clear meanings and plenty of baggage. 

    To help solidify the learning of this workshop, we'll use a couple brainstorming games -- so come prepared to get engaged. We'll wrap-up by using our collective experiences to either find better ways to explain our words or establish brand new ones. Our ultimate goal is to establish a way an organization can establish an ubiquitous language around the work they do and ultimately improve communication which will lead to better agile transformations and hopefully better solutions.

  • Liked Valerie B Santillo
    keyboard_arrow_down

    Valerie B Santillo - The Role of a Leader in an Agile Organization

    Valerie B Santillo
    Valerie B Santillo
    Agile Coach
    Blue Agility
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    We hear a lot about leaders who don't "get" Agile and the impact they have on Agile adoption but, what is the role of a leader in an Agile Organization? Agile requires a great deal of change in the way we approach, manage and execute delivery. And, while a great deal has been put in place to educate and support team members, Scrum Masters and Product Owners, there isn’t a great deal available to those outside of teams – especially leaders.  This discussion will present a description of an Agile leader for consideration and the results from two organizations:  One who applied the learning, and one who did not.

  • Liked Alexei Zheglov
    keyboard_arrow_down

    Alexei Zheglov - Lead Time: What We Know About It and How It Can Help Forecast Your Projects

    60 mins
    Tutorial
    Intermediate

    The session is about just one metric, but a very important one - lead time.  Simply put, lead time is the time between the start of work and delivery.  And there is a catch: if the work has to wait in a queue or if we switch from it to work on something else, the clock keeps ticking until we deliver.  Lead time has proven to be a difficult metric to game.  Even when people try, they often end up delivering faster, with less delay - win-win.

    We will look at examples of real-world lead time data for several different types of work from different companies.  We will discuss the very recent new insights into lead time distirbutions.  Those will then lead us to building useful probabilistic delivery forecast models for your process.  Building such models is surprisingly easy and takes surprisingly few data points.  The models, in turn, enable better decisions.

    Are your ready to embrace the probabilistic approach?

  • George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    30 mins
    Talk
    Intermediate

    Agile planning tools started simple: index cards, markers, and a table or wall. On many projects, for many reasons, these old stalwarts have been supplemented (or even replaced) by software solutions: Rally, VersionOne, Jira Agile, Trello, Trac, Scrumy, and literally dozens more, even BaseCamp. These tools have undeniable advantages over cardboard and ink in some aspects, but they're not superior in every situation.

    This session will highlight the pitfalls of centering planning meetings around software tools—even the best ones, like [your ad here]—and make a badly-needed sales pitch for index cards on a wall (compensating for Oxford's oddly anemic marketing effort). You'll see how cards can make better use of your team's time and brainpower, promote parallelism in meetings, and increase engagement by all participants.

  • Steve Elliott
    Steve Elliott
    CEO
    AgileCraft
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    We would all agree that Agile is mainstream, agile is the future and that Agile DOES work.  So why then do we see so many failed or moderately successful large scale transformations?  The answer is complex but there are many things that can be done to improve your odds of success.

    In this talk we will explore 7 proven methods to help you see bottlenecks, clear land mines and drive better results.  The seven points we will explore include:

    1. Methods to scale up collaboration (above the team level) using agile principals
    2. New methods to scale up estimation by combining standard methods like WSJF, Points, T-Shirts, Team Weeks with Monte Carlo what-if simulations.
    3. Objectives as work packages
    4. Value streams in a three tier model with a RACI twist
    5. Agile Ghantt-ification and other scaled-up visualizations
    6. The effects of WIP discipline at the portfolio level
    7. How calculate capitalization regardless of team methods (cycle time, points, hours) 
  • Liked Susan Parente
    keyboard_arrow_down

    Susan Parente - The Art of Agile Risk Management

    60 mins
    Talk
    Intermediate

    In today’s world of fast paced technology and continually changing requirements and project scope, the need for Agile Project Management has greatly increased. Responding to this demand, the PMI® (Project Management Institute) launched a new certification, the PMI Agile Certified Practitioner (PMI-ACP)SM. The result of this fast growing certification is the creation of a new space where Project Management and Agile Practices for Software Development meet. This calls us to ask where do standard critical project management methodologies like Risk Management fit into Agile Practices.

    This presentation details the methodology of Risk Management as it applies to Agile Project Management. It engages in the steps of Risk Management including: identifying, assessing and managing risks, while mapping these to Agile Practices. Most Project Managers are familiar with Risk Management and Agile, but how do these methodologies relate, and how can we use them to manage resources and do more with less on our projects?    

    What is Agile Project Management and when does it make sense to use it? How Risk Management relates to Agile and how it is incorporated into Agile Practices will be evaluated. Recommendations for implementing Agile Risk Management will be provided along with best practices and how organizations are putting this into practice.

    Risk Management is not only a practice and discipline, it is an Art. Knowing the tools of techniques is not sufficient for success. The nuances of how Risk management is incorporated into agile practices are what generate project success. When requirements and environmental conditions are in flux, our ability to anticipate Risk and plan for it is critical to managing projects with agility.

  • Liked bchaplin1
    keyboard_arrow_down

    bchaplin1 - Minimizing Technical Debt Via Agile Metrics and Techniques

    bchaplin1
    bchaplin1
    Metrics Architect
    Chaplin Solutions
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Automate and mine those code quality statistics from Sonar and use Agile techniques to transform your team and codebase!

    Studies show that poor code quality can cut your velocity in half as early as the second release.  But there's hope.  Yes, you can make your deadlines and still have little or no technical debt.  

    Using proper metrics 50% of the 100 committing developers had no tech debt and 100% test coverage for all their code submitted in 2013.  

    Use key code quality metrics to manage your team's quality and ensure your second release is just as productive as the first.    

  • Liked shentonfreude
    keyboard_arrow_down

    shentonfreude - Making a Better Salad: Behavior-Driven Development with Lettuce

    30 mins
    Tutorial
    Intermediate

    Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format.  This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.

     

    This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce.  You will gain a deeper understanding of how you can apply this to writing your applications.

     

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 years ago
    Sold Out!
    3 mins
    Talk
    Intermediate

    Creating an approach for change is difficult. There is a fine line between imposing an Agile adoption and creating a Transformation where people are collaboratively working together for the change. Based on my experience and in large US Federal Government organizations where imposed adoptions seem the norm, I’ve been working on combining many concepts into a transformation model that can work for large organizations that have ingrained cultures. This starts by helping the organization’s people take ownership and personalize what Agile means to them. Believe it or not, this can work.

    Intended for senior executives and their immediate staff (and the coaches that help them), the Taking Flight approach presents the importance of culture and how creating an organizational aspiration will help guide people. For large organizations, culture has been built up over decades and changing this is of the utmost importance to have an Agile Adoption stick. There are 3 main points I’ll address:
    - how to get people ‘onboard’ with a cohesive direction that they accept by collaboratively building their aspiration
    - how to develop and select strategies for incremental improvement towards the aspiration
    - how to realize changing from old routines into new ones aligned with the aspiration

    To help establish cohesive direction, I use an Aspirational model (your Guiding Star) to help organizations develop the direction they want to go. I show how the differences between an Aspirational model and an End-State. I explain that aspirations are inspiring and allow for a mindset change by not expressing the final state in terms of structure our expected metrics. From there, I discuss different techniques for assessing the current state of the organization and its people and developing strategies and actions for the necessary change management to move towards the organizational Aspiration; this is where the concrete steps come into play. Throughout this portion, I have the group try out various techniques for building an aspirational model and how to build the backlog of work to undertake the transformation. I introduce the Power of Habit as a means to help the organization undergo the necessary behavior changes. I close with a discussion to help the audience think around limiting change-in-progress and how to grow capacity to become more responsive to change.

    In this, you’ll get exposed to a few of many hands-on techniques that can be used to develop your Aspiration and execute on it. These are:

    • KrisMap
    • Business Model Canvas
    • Habit Loops
  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Understanding the Relationship of Optimization, Prioritization, Throughput, Impediments, M├ętier, Utilization, and Sizing

    90 mins
    Workshop
    Intermediate

    Some of the key aspects of successful Agility are slicing our work into small chunks, prioritizing this work, and having our people pull the work at a rate they can sustain.  How do we do that? What does limiting work in progress mean? Is it more beneficial to have people working across stories individually or swarming on stories? What is the effect when specialists have to work on specific stories due to their unique skill sets? Why do we slice stories? When we choose to not have people remove impediments, what impact can that have?

    This session will immerse you in a simulation of what a team goes through when pulling work in an iterative approach such as XP or Scrum.  It was created in response to seeing teams make poor choices in what they optimizing; often choosing to optimize the utilization of resources as opposed to maximizing the effectiveness of the people.  This team also had chosen an architecture where specialized talent was hard to come by, limiting the overall effectiveness.  

    We'll explore what prioritization does for us; how limiting work in progress and slicing stories helps in getting us to done. We'll introduce impediments and make choices whether to work on something else or work to remove them.  We'll introduce a specialist and see what the impact of that is. 

  • Liked George Paci
    keyboard_arrow_down

    George Paci - Lean Software Development: Principles and Tools

    George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Lean Software Development, largely created and popularized by Mary and Tom Poppendieck, is a set of principles and tools for approaching software with a value-focused mindset.  Heavily influenced by Lean Product Design, itself the result of porting Lean Manufacturing insights over into the design realm, it can change the way you think about what you're doing and why.  Lean emphasizes the performance of the entire software-development system, and strongly cautions against optimizing pieces at the expense of the whole.


    This session will be a whirlwind tour through seven principles of Lean Software Development, and one thinking tool associated with each principle.  The common thread of focusing on value, instead of on requirements or process or utilization, ties the concepts together.

  • Liked David W Kane
    keyboard_arrow_down

    David W Kane - DevOps: The Play

    30 mins
    Others
    Intermediate

    Many organizations are using DevOps to speed the ability of organizations to gain value from the software investments.  Too many organizations attempt to reduce DevOps to just a series of technical tools and practices. Organizations to address organizational and cultural issues in order to effectively bring development and operations groups together.  In this section we will present a play to illustrate how DevOps requires communication and understanding to be successful.