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.

 
3 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • In the Beginning: Cards and a Wall

  • The Rise of Software Planning Tools

  • Swiss-Army Hammers

  • Illusory Efficiencies

  • Breaking Bad Habits

  • Bringing Physical and Virtual Together

     

Learning Outcome

Attendees will recognize the limitations of popular software planning tools in some situations, have a clear idea how to use cards and walls where they offer a better solution, and know how to combine cards and software to maximize effectiveness.

Target Audience

ScrumMasters, Product Owners, Managers, Tool Vendors

schedule Submitted 2 years ago

Comments Subscribe to Comments

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

    Good afternoon Geroge,

    We have not yet received a response from you with respect to the invitation to present at AgileDC next month.  Please RSVP to the invitation sent on August 29th, or, alternately, via email that “I AM IN” to SPEAKERS@AGILEDC.ORG , by 11:59PM Sunday, September  7th, 2014 .  If we do not hear from you, we will have to forfeit your spot.

    Have a great weekend!  

    Best,

     

    George Dinwiddie and Phillip Manketo

     

    for the AgileDC organizing committee


  • Liked David Bulkin
    keyboard_arrow_down

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

    David Bulkin
    David Bulkin
    schedule 2 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
    schedule 2 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.

  • Paul Boos
    Paul Boos
    schedule 2 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
    schedule 2 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 Kane
    keyboard_arrow_down

    Making Movies and Software at the Speed of Thought!

    David Kane
    David Kane
    schedule 2 years ago
    Sold Out!
    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

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

    Philip Rogers
    Philip Rogers
    schedule 2 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 Alexei Zheglov
    keyboard_arrow_down

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

    Alexei Zheglov
    Alexei Zheglov
    schedule 2 years ago
    Sold Out!
    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?

  • Liked Shannon Ewan
    keyboard_arrow_down

    The Art of Facilitating Agility

    Shannon Ewan
    Shannon Ewan
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    From an agile implementation perspective, emphasizing the art of facilitation is an incredibly powerful tool for creating a culture of collaboration, and then leveraging that culture as a springboard to organizational transformation.  With strong facilitators at the gateway between business and IT, within IT delivery teams, and at key intersection points within an organization, the challenges to achieving organizational agility diminish. Strong facilitators bring forth the wisdom of teams and provide a container for self-organization. Facilitation is the cornerstone of servant leadership. 

  • Liked Derek Huether
    keyboard_arrow_down

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

    Derek Huether
    Derek Huether
    schedule 2 years ago
    Sold Out!
    3 mins
    Workshop
    Beginner

    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.

  • Liked shentonfreude
    keyboard_arrow_down

    Making a Better Salad: Behavior-Driven Development with Lettuce

    shentonfreude
    shentonfreude
    Paul Boos
    Paul Boos
    schedule 2 years ago
    Sold Out!
    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
    schedule 2 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 Mark Grove
    keyboard_arrow_down

    Four Easy To Adopt Agile Metrics for Teams Just Getting Started

    Mark Grove
    Mark Grove
    Julie Wyman
    Julie Wyman
    Jolly Rajan
    Jolly Rajan
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Using metrics to track agile team performance can be an important tool to reinforce the need for continuous improvement. Metrics can serve as valuable input during retrospectives, the daily standup, and sprint planning allowing teams to continuously adapt their practices and performance based on the observed patterns the metrics reveal. In our experience, many new agile leads and teams are not sure which agile metrics would be the best metrics to begin using. Some teams may be tracking various data points, but lack the skill and understanding of what the metrics are actually revealing and how the teams can use this information to self-improve.

    Our presentation/workshop introduces four "light-weight" agile metrics any team can easily adopt and begin using immediately. They are: Velocity, Comitted vs. Done, Sprint Build-up (Burn-up), & Cycle Time.

    We introduce each of these metrics and explain what each one measures, how to obtain the data, and when it should be updated. But most importantly, our presentation provides a workshop component where we provide sample scenarios for each metric. These scenarios represent possible real-life data patterns teams could experience. In the workshop, we ask the audience to work in small groups to consider what each scenario may be representing and what they would do, in the spirit of continuous improvement, to respond to these patterns. We also discuss with the audience how to use the metrics in tandem to help provide a more robust interpretation of team performance.

    We realize there are many agile metrics teams can adopt. However, for teams just starting out we recommend these easy to use yet powerful metrics to help teams monitor and assess team performance.

  • Liked Paul Boos
    keyboard_arrow_down

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

    Paul Boos
    Paul Boos
    Dante Vilardi
    Dante Vilardi
    schedule 2 years ago
    Sold Out!
    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

    Lean Software Development: Principles and Tools

    George Paci
    George Paci
    schedule 2 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 George Paci
    keyboard_arrow_down

    Running a Five Whys

    George Paci
    George Paci
    schedule 2 years ago
    Sold Out!
    30 mins
    Tutorial
    Beginner

    You're hit with a problem, possibly repeatedly, and it's not clear what to do about it.  You know that Root Cause Analysis can help, and you know a Five Whys exercise is a good way to do that.  But how do you run a Five Whys?  There's more to it than putting everyone in a room and saying "Why?" five times, isn't there?

    This session will prepare you to run your own Five Whys exercises, and to answer important questions like who to include, how to introduce the exercise, what to do when the group stumbles, how to deal with prematurely-offered solutions, and how to prepare for the exercise.

  • David Kane
    David Kane
    Kumar Dattatreyan
    Kumar Dattatreyan
    schedule 2 years ago
    Sold Out!
    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.

  • Liked Mishta A Brooks
    keyboard_arrow_down

    5 Moving Trains all Trying to Merge on the Same Track

    Mishta A Brooks
    Mishta A Brooks
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    United States Citizenship and Immigration Services (USCIS) decided to shift thier agencies current Transformation to include changing the entire development process all at one time. This included utilizing multiple contractors, shifting to a DEV/OPS structure, using a new cloud enviroment, transitioning from COTS to open source software all while introducing Agile concepts to the development team. This complete overhaul of "business as usual" was a complete culture shock to the enviroment and required close colloboration and consistent communication in order to create change and progress. As the Release Manager during this transition I will speak the lessons learned and how the team was able to progress after the introduction of so much change at one time, all while ensuring Government requirements were still met.

  • Joshua Seckel
    Joshua Seckel
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Advanced

    Retrospectives are great! They result in great process changes for a team to adopt to become more efficient.

    But how do you determine when the process change adopted by one team should become part of the overall recommended practice for the organization?  What worked in one team very well might not be helpful or effective on another team, and at the same time, the organization needs to take advantage of the innovation happening at individual team levels and adopt the best ones as recommendations.

     

    This talk will look at a more formal method of tracking the effectiveness of specific retrospective improvements and how to decide when to make team process changes into organizational recommendations. This will show how to us Bayesian Statistics to track the effectiveness of specific process improvements and setting threshholds for organizational wide recommendations can lead to a good process for organizational process improvement based on team successes.

     

    Specifically, we will look at how to set up the process at the organziational level and the team level:

          What processes need to be agreed to?

          What changes in governance need to be agreed to?

          How to decide when to make recommendations?

          What changes should be made at the team retrospective level?

    I will also discuss how this experiment is working and what we have learned from trying to adopt this methodology.

     

    This method should be very helpful within organzations with high oversight and governance, such as the government, to allow for continuous process innovation while still maintaining concurrence from those bodies.

  • Liked Cindy Shelton
    keyboard_arrow_down

    Organizational Agility

    Cindy Shelton
    Cindy Shelton
    schedule 2 years ago
    Sold Out!
    60 mins
    Tutorial
    Intermediate

     

    We inherently know that organizational agility is a critical necessity for effective government operations if we are to respond to the ebb and flow of political issues. Our creative managers adjust and adapt to accomplish these unforeseen work if they are to be successful and learn to force agility to execute pet projects. Ironically, this type of agility eventually results in functional redundancy and inefficient workflow as large organizations simply cannot stop to adapt and adjust their internal infrastructure to the rapidly changing demands of business. Their business processes, structures, and systems act as barriers to efficiency and common-sense decision making. These internal barriers can trap capable people who eventually become cynical and disheartened by their inability to change or influence obvious gaps, inconsistencies, or burdensome constraints within the organization. In this situation, it is prudent for the organization to re-think its organizational design and evaluate work to realign appropriately to the needs of the organization. Consultants, frameworks and models are easy to throw money at, but rarely result in the return on investment anticipated by the effort and expenditures. A better method is to use internal resources (retain intellectual capital) and implement work practices that provide visibility into work being accomplished so they may be valued against other work for better decision making and effective use of available funds. This session provides an operational framework for that method using existing organizational frameworks and applying structured processes that can be incrementalized.