AgileDC 2017 Day 1

Mon, Oct 16
Timezone: America/New_York (EST)
07:30

    Registration - 60 mins

08:30

    Opening Remarks AgileDC 2017 Organizing Board Members - 20 mins

08:50
09:35

    Coffee Break & Networking - 25 mins

10:00
10:15
10:30
10:45

    Coffee Break & Networking - 15 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Julie Bright

    Julie Bright - Powerful Tools for Effecting Change: Personal and Social Identity

    schedule  11:00 - 11:45 AM place Auditorium people 27 Interested star_halfRate

    Scrum Masters and Agile Coaches wear many hats, but one of the most important is that of the Change Artist. Understanding what people need in order to move through a change curve is critical to success, but often overlooked in the toolkit is the role of Identity. Our self-perception, both as individuals and within the context of a group, is foundational to our psychology, and can be leveraged to affect and nurture powerful, long-lasting change.

  • schedule  11:00 - 11:10 AM place Ballroom D people 12 Interested star_halfRate

    For a long time multitasking has been considered a must-have skill when, in fact, it makes us less productive and more prone to error. But even with plenty of studies and papers supporting that idea, it can be hard to convince managers and stakeholders that we should be taking on less at a time. In this lightning talk, we'll run through one very quick, lightweight simulation (Multitasking is Evil) you can use to help make that case and show that lowering work in progress is the way to go!

  • Added to My Schedule
    keyboard_arrow_down
    Sanjiv Augustine

    Sanjiv Augustine - 5 Steps to Disruptive Innovation with Hyper-Performing Teams

    schedule  11:00 - 11:45 AM place Ballroom C people 19 Interested star_halfRate

    For too many organizations, Agile is primarily seen as merely an IT delivery system. Within this archaic and limited mindset, New Product Development is so manageable with Scrum. We amble along with 30-day Sprints, a single product owner, a neat product backlog, and a collocated Scrum team. But, today’s business environment is a tsunami of global hyper competition, with companies entering and being forced off the S&P 500 every 15 years. The classic Innovator's Dilemma is now even more pressing, and quite candidly, archaic Agile is of limited use.

     To be competitive now, organizations need to look at the gestalt ... the entire value-stream of activities that are required to bring solutions to market. In this session, we will show concrete examples of how major organizations have innovated along the full path from product ideation to requirements to budgeting to delivery and to operations. Each part of a typical value-stream will be explored to show how agility has impacted these traditionally silo'ed functions and how forward-thinking organizations have reached the next level of performance through tight integration and agile thinking.

    Learn the essential steps to conquer the entire value-stream from the “fuzzy front end” of innovation, product discovery, lean experimentation, and modern requirements discovery, to pipeline management, to agile budgeting and incremental funding, to high-performance product-centric teams, and enabling agile engineering techniques.

    The result is the architecture of an entire organizational system that is designed to rapidly and effectively discover what customers want and delivery with utmost efficiency.

  • Added to My Schedule
    keyboard_arrow_down
    Rachel Whitt

    Rachel Whitt / John Hughes - Impact Mapping Workshop: Deliver Business Outcomes, Don't Just Ship Software

    schedule  11:00 - 11:45 AM place Ballroom B people 42 Interested star_halfRate

    Our roadmaps and backlogs are usually littered with pet projects, squeaky wheels, and recent ad hoc items that gain priority simply because they are the latest shot across our bow. Impact mapping is a powerful practice that helps us identify and align our work to the most valuable business goals and mission objectives and avoid many of the common challenges that arise from an unfocused set of work priorities.

    Impact maps help us visualize quantifiable benefits that deliverables should produce towards our business objectives. They allow us to focus our work on those deliverables that move the needle the most, not just deliver features. The practice is a great way to communicate assumptions, create plans, and align stakeholders as well as aid in strategic planning, roadmap management, and defining measures of success and quality.

    This workshop will provide an appreciation for the power of impact mapping by walking you through building your own impact maps and the facilitation process for doing so in your own organization. You will leave the workshop having participated in a tangible example of the technique, and having gained an understanding of best-practices for facilitation with a focus on an impact map’s outputs and how they lead into the creation of actionable user stories when completed. Hands-on collaboration with your fellow attendees will help encourage your own application of this technique in your real world road-mapping and backlog refinement activities.

  • Added to My Schedule
    keyboard_arrow_down
    Pete Oliver-Krueger

    Pete Oliver-Krueger - Double Aces: Using Positive Psychology to Resolve Disputes and Take Constructive Action

    schedule  11:00 - 11:45 AM place Ballroom A people 36 Interested star_halfRate

    Learn about the latest developments in brain research, and the practical exercises they’ve produced for facilitating conversations (even the most-difficult ones) and turning them into concrete action plans.

    Have you experienced any of the following?

    • Witnessed two people arguing the same side of an issue, at each other?
    • Reached the end of a meeting with no decisions made?
    • Been told, “That’s not what I thought I was getting.”?
    • Had a great idea, but couldn’t get anyone to listen?
    • Had anyone shout in your meetings?

    Even if your teams aren’t necessarily in conflict, the techniques discussed in this session will deliver an repeatable way to discuss complex, multi-sided issues, in an organized way that respects all participants, makes sure everyone feels heard, and produces tangible results that everyone can be proud of.

  • Added to My Schedule
    keyboard_arrow_down
    Melinda Solomon

    Melinda Solomon - From Pandemonium to Predictable: Managing the Chaos of Success

    schedule  11:00 - 11:45 AM place Room 4 people 7 Interested star_halfRate

    We often aim for success and welcome it with open arms.  But, sometimes success comes more quickly than you anticipate, and demand for services exceeds your capacity to deliver.  The result can be missed commitments, high stress, and inability to forecast with clarity.  As quickly as your brand shines, it can tarnish with your inability to keep up.  Basically your dreams become your nightmare.

     This is the story of a small little training program for a transforming enterprise that consisted of a single class and an instructor.  Within 3 years it had grown to 12 courses and 6 instructors with a waiting list for seats.  People wanted more courses and more offerings of the existing courses.  People were asking for us to attend events and summits and briefings. As demand surged we began to fall into a pattern of unreliable service and delivery with a completely unsustainable work/life balance. 

     In the midst of the chaos we became inspired by the IT software development model of Kanban.  While we're engaged in non-IT knowledge work, we became convinced an implementation of a proto-kanban management system could save our reputation.  The Kanban management method saved our business when the chaos of success was drowning us.  And it can help you too!

  • Added to My Schedule
    keyboard_arrow_down
    Peter Wilding

    Peter Wilding - From Scrum to Kanban and Back

    schedule  11:00 - 11:45 AM place Room 5 people 23 Interested star_halfRate

    After two years of doing Scrum for one of our teams, we needed to be very fluid for the two months leading up to a major event.  The answer? Run using Kanban for those two months.  In this talk, we'll describe why we decided to make this change, and then why we decided to go back to Scrum afterward.

  • Added to My Schedule
    keyboard_arrow_down
    Roland Cuellar

    Roland Cuellar - Accelerating Business Side Agility - An Enterprise Experience Report from Nationwide Insurance

    schedule  11:00 - 11:45 AM place Room 6 people 18 Interested star_halfRate

    While the IT side of this F500 financial services client has been practicing agile development for years, the business side is still, in some cases, more waterfall and traditional in its approach to requirements and releases.  In this experience report, we will hear from Associate Vice President Charlie Kennedy of Nationwide Insurance on how we have accelerated business-side agility by:

    • Re-organizing from functional silos to Product-Based Value-Stream Teams
    • Redesigning the business requirements process to achieve a continuous flow of MMPs into the teams
    • Utilization of Big-Room-Planning techniques to create alignment across a wide set of stakeholders and dependencies
    • Design of a Product-Manager-to-Product-Owner fan-out concept to achieve omni-channel digital delivery
    • Design of a portfolio-level visitation system to track the flow of MMPs across multiple investments simultaneously

     

  • Added to My Schedule
    keyboard_arrow_down
    Max Saperstone

    Max Saperstone - Exploring Automation Strategies and Frameworks What Should Your Team Be Using?

    schedule  11:00 - 11:45 AM place Tiered Classroom people 21 Interested star_halfRate

    Agile practices have done a magnificent job of speeding up the software development process. Unfortunately, simply applying agile practices to testing isn't enough to keep testers at the same pace. Test automation is necessary to support agile delivery. Max Saperstone explores popular test automation frameworks and shares the benefits of applying these frameworks, their implementation strategies, and best usage practices. Focusing on the pros and cons of each type of framework, Max discusses data-driven, keyword-driven, and action-driven approaches. Find out which framework and automation strategy are most beneficial for specific situations.

    Other than using specific frameworks as examples, the presentation is framework agnostic, really focusing on capabilities of different types of framework, and how those might or might-not fit your company's/software's needs. In the talk, 5 different types of frameworks will be discussed: Record/Playback (Linear), Modular/Structured, Data Driven, Keyword Driven, Action Based, and of course the combination of these as Hybrids.

    At the end of the talk, depending on questions, and how much time we have left, a slide with a long list of specific testing frameworks is displayed, and an open discussion of who has used what, and what has/hasn't worked for them is had.

    If you are new to test automation or trying to optimize your current automation strategy, this session is for you.

     

  • Added to My Schedule
    keyboard_arrow_down
    Tommie Adams Jr.

    Tommie Adams Jr. - The Zombie Retrospective

    schedule  11:00 - 11:45 AM place Executive Boardroom people 3 Interested star_halfRate

    So they say the retrospective is one of the strongest and most powerful tools in the agile scrum methodology tool kit, and is often overlooked or skipped. So how does a scrum master find ways to creatively explain and express the importance of this agile scrum ceremony, or even the basics of agile scrum in general. How does the scrum master explain the importance of banding together as a team in this brave new agile scrum world. In many organizations, nowadays, the teams are even made up of outside vendors as well as in house associates. So how do you even start to pique the interest and the importance of team collaboration to a bunch of folks who are strangers to one another on a agile scrum team? Even more specifically, how do you explain how the retrospective ceremony will help improve the way they work with one another over time?

    My answer: ZOMBIES!!! Everyone loves zombies, right? So come, take a bite!

  • Added to My Schedule
    keyboard_arrow_down

    Impromptu Topics

    schedule  11:00 - 11:45 AM place Break Lounge star_halfRate
11:15
11:30
11:45

    Lunch Break & Networking - 75 mins

13:00
  • schedule  01:00 - 01:45 PM place Auditorium people 32 Interested star_halfRate

    Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change.
    Agile transformation necessitates a fundamental rethinking of how your company organizes for delivery, how it delivers value to its customers, and how it plans and measures outcomes. Agile transformation is about building enabling structures, aligning the flow of work, and measuring for outcomes based progress. It's about breaking dependencies. The reality is that this kind of change can only be led from the top. This talk will explore how executives can define an idealized end-state for the transformation, build a fiscally responsible iterative and incremental plan to realize that end-state, as well as techniques for tracking progress and managing change.

  • Added to My Schedule
    keyboard_arrow_down
    John Le Drew

    John Le Drew - Swearing, Nudity and Other Vulnerable Positions

    schedule  01:00 - 01:45 PM place Ballroom D people 12 Interested star_halfRate

    Over 3 months John recorded over 75 hours of interviews and spoke to some of the most respected people in the industry to produce an audio documentary that attempts to answer the question “What is safety? And why is it important anyway?”

    This highly interactive talk will present the findings and guide and challenge you through a journey to understanding safety. Including short interactive sessions and role play exercises to cover the following topics:

    • What is safety?
    • What are the elements that make a team effective?
    • Is psychological safety the foundation to team performance?
    • What can we all do to help foster psychological safety in our teams?
    • What is the relationship between safety, stress and engagement?
    • What is the profound impact of a lack of safety and engagement on society?

    This talk has grown as John created the new podcast The Agile Path. The first season on this podcast is about safety in teams. John has interviewed world renowned specialists in the field; Christopher Avery, David Marquet, Jerry Weinberg, Esther Derby, Johanna Rothman, Woody Zuill and many more in over 75 hours of audio. This has been a fascinating deep dive learning experience for John and he hopes to explore these insights with the audience.

  • Added to My Schedule
    keyboard_arrow_down
    Dan Neumann

    Dan Neumann - Experience a Red/Green/Refactor Coding Kata

    schedule  01:00 - 01:45 PM place Ballroom C people 8 Interested star_halfRate

    Have you heard people talking about Test Driven Development (TDD) but never tried it? Now is the time to try! This session will lead its participants through a programming challenge. Don't worry, it's safe. We're going to do a technical version of "follow the leader," where you will do the programming by following along with the session's facilitator. We'll debrief the exercise at the end. Please do bring a laptop or be willing to pair up with someone who does.

    We will use the Python programming language, and PythonAnywhere web-based environment to avoid setup and configuration activities. You do NOT need to know Python (or any programming) to participate.

  • Added to My Schedule
    keyboard_arrow_down
    Chris Murman

    Chris Murman - Brainwriting: The Team Hack To Generating Better Ideas

    schedule  01:00 - 01:45 PM place Ballroom B people 23 Interested star_halfRate
    Brainstorming has long been held as the best way to get ideas from teams for decades, but what if we are wrong? Can we take the successful aspects of collaboration and create a better environment for quality concepts? Come learn about brainwriting and get more from your team today!
     
    Description:
    If you work in an office, your boss has probably forced you into a brainstorming session or two (or 12). Invented in the 1940s by an advertising executive, the purpose was to solicit a large amount of ideas in a short period of time. By putting a collective of creative people in the same room, better concepts should come. Sounds very agile. 
     
    However, science has shown several times that brainstorming is a terrible technique. It’s cumbersome due to all of the interdependent activities happening at once. When spending time generating ideas as a group, you often spend more time thinking of others ideas than your own. 
     
    Fortunately, a relatively unknown technique is starting to gain popularity called brainwriting. Incorporating it into your team events can produce more diverse ideas and provide a friendlier environment for collaboration. In this session, we will workshop them and leave the audience with all of the tools to bring the technique back to their offices.
     
    What Makes It Compelling:
    I was skeptical when I first read an article on the technique, mainly because I had always believed brainstorming produced quality ideas. As a “stickies and sharpies” type of coach, I’d seen so many teams collectively throw out ideas during planning and retrospective sessions. But in the ensuing weeks, I started seeing where the article was on point in terms of producing quality ideas.
     
    After contrasting the ideas generated after using brainwriting for a few weeks, my mind was changed forever. Even better was the events themselves didn’t seem that different to teams. 
  • Added to My Schedule
    keyboard_arrow_down
    Steve Mayner

    Steve Mayner - Leadership: Beating the odds of OCM failure in Agile/DevOps initiatives

    schedule  01:00 - 01:45 PM place Ballroom A people 22 Interested star_halfRate

    Adopting Agile and DevOps principles and practices frequently leads enterprises down a path to significant cultural and organizational change. This creates a real barrier for leaders, coaches, and change agents to overcome. Many researchers, sparked by John Kotter’s claim of a 70% failure rate for organizational change have confirmed through scientific study that these types of transformative efforts are more likely to fail than to succeed. Fortunately, all is not lost! Scholar practitioners have also uncovered a powerful tool that consistently increases the success rate of significant organizational change. The secret weapon is leadership… but not just any style of leadership…

    In this session, Dr. Steve Mayner will share the potential power of transformational leadership behaviors to drive successful organizational change. His primary research was the first to explore the correlation between this specific leadership style and positive response to change in Agile/DevOps implementations. How enterprise leaders cast vision, encourage individual growth, demonstrate authenticity, and challenge followers to maximize their creative potential can have a greater influence on the success of an Agile/DevOps implementation than any change management method, methodology, or toolset. Steve will also share examples from his own experiences observing transformational leadership in action, and the results that followed.

  • schedule  01:00 - 01:45 PM place Room 4 people 21 Interested star_halfRate

    So you are considering getting a coach to help you in your transition to Agile. Or perhaps you are an Agile practitioner considering becoming an Agile coach. What do these Agile coaches do? What makes them different?

    This session will enter the foyer of the house that describes what coaches do and considerations one can have when they think about coaching (including hiring one). Prepare to be challenged and to learn a bit of what it takes to be or work with a coach; it has little to do with courses or certifications, though they may help. In covering what coaches do, one can now begin to think along the lines of what the skills one may need to improve.

  • Added to My Schedule
    keyboard_arrow_down
    Jason Cusack

    Jason Cusack - Facebook Agile: From Green to Greener, plus other lies and bull$#!t

    schedule  01:00 - 01:45 PM place Room 5 people 14 Interested star_halfRate

    All companies tell lies. All executives endorse lies. And all employees live lies.

    We must pretend we are amazing, and brag to our peers about how much farther ahead we are, than they are. We change the narrative to suit our lies. We have reports to prove our lies.

    This happens at EVERY company.

    When you look at Facebook feeds – all you see is pictures of vacations. Smiling kids. BBQs. Clean pools. You never see the miserable couple, the dirty laundry, or the crying kids.

    Enter Facebook Agile.

    We are conditioned to hide the bad $#!t that is going on around us. There’s no reason anyone has to know what’s really going on (even though most people know what’s going on).

    Our leaders are afraid of what other peers might think. Or worse, what other “senior management” might perceive or judge. So they choose not to be leaders, despite the obvious need for leadership.

    This session will provide an experience report on what leaders can do to embrace transparency, trust, and courage. Building a culture of continuous improvement starts with embracing the things that aren't working, instead of hiding them to avoid overhead.

  • Added to My Schedule
    keyboard_arrow_down
    Beth Hatter

    Beth Hatter - Who am I now? - Exploring the Role of Managers in an Agile World

    schedule  01:00 - 01:45 PM place Room 6 people 33 Interested star_halfRate

    In the latest "State of Agile" report lack of management support was still near the top of the list in what stalls or even derails successful agile adoptions. Managers are often confused on exactly what their role should be and how to transition from a 'project management' mindset to 'agile support' mindset. In my experience - as a former project manager turned agile support leader and now training/coaching agile teams - I have found managers need, but often don't receive, support and guidance on how to avoid being a roadblock or burden to a highly functional agile team. I'll discuss the importance of switching focus from projects to people, and on developing- their people and modeling Lean culture while still performing important and necessary corporate or compliance functions.

    This talk will explore the myths surrounding managers for agile teams and team members, show why we still need them and highlight what I have called the "4G's of being a great manager" supporting agile teams.

    If you are a leader or manager and are working with agile teams, or a scrum master trying to support the team interactions with their larger organization, or anyone interested in the role of managers and how it changes in an agile enterprise then this talk will provide guidance and tips for what a manager should (and shouldn't!) do.

  • Added to My Schedule
    keyboard_arrow_down
    Fadi Stephan

    Fadi Stephan - Agile Testing - Testing From Day 1

    schedule  01:00 - 01:45 PM place Tiered Classroom people 28 Interested star_halfRate

    Many teams struggle with fitting in testing activities inside of a Sprint. They end up doing primarily development activities in a Sprint and push testing activities to run in dedicated testing Sprints following the coding Sprints or have a coding and testing Sprint running in parallel. However, in Scrum, the output of every Sprint is a potentially shippable product increment. This means the product increment should be well tested within the Sprint and ready to be delivered. Come to this presentation to learn how to tackle testing on an Agile team, what kind of tests to execute, what to automate and what not to automate, the different testing responsibilities, and when to run which tests. Leave with a testing strategy that you can start applying the next day to gradually get a team to start testing from day 1 of the Sprint and deliver a true product increment at the end of each Sprint.

  • schedule  01:00 - 01:45 PM place Executive Boardroom people 23 Interested star_halfRate
    We often look to our engineering teams first to drive efficiency and speed to deliver but as we optimize the flow of our development processes we quickly create pressure in the organizational workflow with the activities that feed into and out of product delivery.  Product definition struggles to keep pace and establish a queue of viable options to pull from.  Marketing efforts begin to pile up as features release faster than we can share the news.  All of this stems from optimizing only one part of the overall system.  In this talk we will look at how to scale Kanban practices to the entire organization to provide the visibility, flexibility and predictability to make every part of the business truly agile.  
  • schedule  01:00 - 01:45 PM place Break Lounge people 3 Interested star_halfRate

    I will be hosting two 45-minute Lean Coffee collaborative conversations at AgileDC this year. One session will take place in the morning; the other in the afternoon.

    What is Lean Coffee?

    Lean Coffee is a type of discussion for the people, by the people. Participants gather, build an agenda together, and begin talking. It is sometimes called a structured, but agenda-less meeting.

    1. We will identify what we want to talk about
    2. We will vote & discuss
    3. We will identify key findings/ideas/takeaways

    Why do it?

    It's a great technique to learn when you want to spark some engaged -- yet casual, collaborative conversations around topics that are of interest to the group. You can use the Lean Coffee format within your department, across departments, as a brainstorming platform or for team retrospectives. There are many different possible applications.

    What will we discuss?

    For the AgileDC sessions, our conversation topics will be determined by you! Our theme will be pretty broad. You've probably guessed it...Agile!

    When you come to Lean Coffee, please be prepared to write down at least 1-2 topics in the form of a question.

    Examples:

    • "My organization struggles with ____. How do we take some steps to get better at this?"
    • "Here's what we're doing in regards to ____, what are you doing?
    • "What metrics do you actually use?"
    • "How big are your agile teams?"
    • "We've got some basic processes in place, but what's next?"

    When you take Lean Coffee back to your organization, the theme of each session could be a real democratic set of agile topics making for truly spontaneous networking/collaborative/experiential learning and participation opportunities, or you can announce a theme in advance and attendees will be asked to focus their topic ideas around that specific theme.

    I hope you will join me at AgileDC for a Lean Coffee conversation!

  • schedule  01:00 - 02:45 PM place Pre-Function Area people 12 Interested star_halfRate

    Why do we talk? How useful is it?
    Let's work together in small teams to make products in complete silence, experiencing how talking both benefits and stifles collaboration.
    What does collaboration really mean? How can this experience improve your collaboration?

    In this experience, which is modeled after experiments run by Dr. Sallyann Freudenberg and Katherine Kirk, participants will experience a
    * 90 minute period of complete silence while working together to build prosthetic hands for charity, noting down each time they have the urge to speak
    * 45 minute review period where our facilitators will help us look at what we wanted to say and what happened instead, along with summarizing the outcomes we experienced through silent collaboration so that participants can take back with them these enlightenments.

    We will pay particular attention to re-evaluating our model of collaboration and deep diving on the things people still felt like they wanted to say -- Did they really need to? What happened when they couldn't? How did that affect the outcome? We were moved by this experience when we participated in it at Agile2017, and are excited to provide the same experiential learning and awareness of silent collaboration to our community back in DC.

13:45

    Coffee Break & Networking - 15 mins

14:00
14:15
14:30
14:45

    Coffee Break & Networking - 30 mins

15:15
  • Added to My Schedule
    keyboard_arrow_down
    Phillip Manketo

    Phillip Manketo / Dave McMunn - Building Strong Foundations…. Underwriting Fannie Mae’s Agile Transformation

    schedule  03:15 - 04:00 PM place Auditorium people 21 Interested star_halfRate

    Over the course of the last two and one-half years, Fannie Mae has worked aggressively to transform itself from a heavily silo’d and firmly entrenched command and control culture, following a gated workflow, with long release cycles, to an Agile organization.  Today, Fannie Mae is a more dynamic value oriented organization that is responsive to stakeholders, focused on achieving greater efficiency by enabling fast-feedback loops, as well as using empirical data to optimize mature and persistent agile values and practices.  

     

    Within the larger context of the transformation to enterprise agility, this Experience Report will focus on the case for change, Fannie Mae’s journey and the corresponding challenges, benefits and key learnings realized.  Our conclusion, while it is important to build bridges with business stakeholders, mature agile teams, leverage automation and embrace the values and principles of the agile manifesto… a successful and longstanding transformation is dependent upon the unrelenting focus on changing the ecosystem supporting the organization’s change at the outset.

  • Added to My Schedule
    keyboard_arrow_down
    William Strydom

    William Strydom - The Silent Collaboration Experience - Review & Debrief

  • Added to My Schedule
    keyboard_arrow_down
    Robert Eisenberg

    Robert Eisenberg / John McLoughlin - Going with the Flow – Games for Understanding Product Development Flow

    schedule  03:15 - 04:00 PM place Ballroom C people 15 Interested star_halfRate

    Many of us having been heavily influenced by Don Reinertsen’s “Principles of Product Development Flow” and others who have advocated a focus on flow based optimization. Unfortunately, some of the key premises for optimizing flow are counterintuitive and counter to traditional practices. For example, the supposed benefits and the economies of scale with large batch sizes, or the belief that systems are optimized when the utilization of individual resources are optimized. Given these beliefs, how can we show in a simple and objectives way that these long held views and associated practices are actually counterproductive to our end goals? With games of course! This workshop will introduce dice games that demonstrate in a Scrum and Kanban context how small batches and a focus on flow vs. optimizing utilization leads to better team outcomes. Participants will be organized into teams of 4-5 people and play a game that simulates—in a fun way—the complexities of real product development work. Each team member will have an assigned skill that aligns with an activity type (e.g., analyst, developer, tester) in the team work flow. Each “story” to be worked will require varying levels of effort for each activity type. The dice provide the variability inherent in knowledge based work, with each roll determining how much “work” each person can accomplish in a fictional day. The quantifiable results of the game will demonstrate how a focus on flow can help lead to better team outcomes, providing attendees with a new tool for helping others understand why they should “go with the flow”.

  • Added to My Schedule
    keyboard_arrow_down
    Scott Showalter

    Scott Showalter / April Jefferson - Continuous Improv

    schedule  03:15 - 04:00 PM place Ballroom B people 8 Interested star_halfRate

    A playful, often hilarious look at agility and innovation through the lens of continuous improvement. Improv games aren't just intended for team engagement and fun. They can often spark ideas that have a potential to generate revenue. Last year's session was standing room only. Now Scott returns with a remixed format and even more innovation-empowering improv games that have transformative value we can apply to the products we build, leading to powerful, groundbreaking new levels of user-centered capabilities.

    Make improv work for you by exploring in the context of a real team during the session, and walk away having gone full circle on solving a real problem using it. During the session you'll be moved through the problem space in an enlightening way that enables you to take a meaningful approach to the solution space. You'll run through several short and medium-length interactive improv activities in your teams, coupled with the power of design thinking and inspect/adapt cycles, all with agility in mind.

  • Added to My Schedule
    keyboard_arrow_down
    Donald Patti

    Donald Patti / Aditi Dussault / Phil Jones - Don't Mess with Button Bear (and other key lessons from the US Small Business Administration's Agile Transformation)

    schedule  03:15 - 04:00 PM place Ballroom A people 8 Interested star_halfRate

    Many organizations struggle with failure and turn to Agile as a game-changer. But how do the dynamics of government magnify the challenge of Agile adoption? Through this 45-minute case study of the "SBA Certify" program, the start of the US Small Business Administration's Agile journey, we'll

    • Describe what triggered SBA's transition to Agile from waterfall software development
    • Explain how key players from the SBA, USDS and 8(a) contractors Telesis & Enquizit led the transition to Agile
    • Review the combination of tools, technologies and practices that led to the successful launch of certify.sba.gov in just seven months
    • Cover how the SBA has built upon the success of certify.SBA.gov to become a leader in Agile adoption among small government agencies

    In addition, co-presenters Aditi Dussault (former SBA Deputy Chief of Staff), Phil Jones (Telesis) and Donald Patti (Cedar Point Consulting) will propose a framework for understanding government inaction, helping others to make radical, transformative change in government possible.

    (And, of course, we'll also explain Button Bear).

  • Added to My Schedule
    keyboard_arrow_down
    Amber King

    Amber King - Culture, Collaboration, & Creativity: How to Keep Your Corporate Innovation Lab Relevant

    schedule  03:15 - 04:00 PM place Room 4 people 21 Interested star_halfRate

    Innovation Labs often don’t create the impact they’ve promised and many eventually fail. Capital One’s Innovation Lab, founded in 2011, has evolved to stay relevant throughout the years. In this session, Amber King, Senior Manager of Accelerator Operations talks about how the Labs' operating model has changed over the years, the details of how the Lab's new accelerator model works, how we incorporate Lean Start-up, Design Thinking, Google Design Sprints, Scrum, and Kanban techniques on our teams and what has triggered the need to reinvent the Labs' model in order to continue to push for disruptive innovation.

  • Added to My Schedule
    keyboard_arrow_down
    Nathaniel Cadwell

    Nathaniel Cadwell - Leveling Up Your Facilitation Skills

    schedule  03:15 - 04:00 PM place Room 5 people 45 Interested star_halfRate

    Group process facilitation skills are a key capability for collaborative, multidisciplinary teams. As a leader in a local facilitation community, I often hear the following question from new members: 'How do I improve my skills?' In this session you’ll learn how to assess yourself against a core competencies framework, as well as how to create a personal development plan for leveling up your facilitation skills. In addition, I’ll provide some concrete suggestions on how to improve both on your own and as part of a community of practice.

  • Added to My Schedule
    keyboard_arrow_down
    Jaap Dekkinga,

    Jaap Dekkinga, - Stakeholder involvement (sub title: How do I involve my stakeholders best in an Agile environment?)

    schedule  03:15 - 04:00 PM place Room 6 people 28 Interested star_halfRate

    One of the struggles I have seen when organizations transition to Agile in relation to the Agile principle "Customer Collaboration Over Contract Negotiation" is: When and how do I involve the right customer.

    Goal of this presentation:

    • Provide tools on how to involve different types of stakeholders
    • Tool to identify different types of stakeholders

    In the presentation I will explain the 2 step process of:

    • Step 1: map out the players for a value stream, product, or feature(set) in a simple 2x2 Stakeholders Matrix (influence/power and interest)
    • Step 2: Learn about the tools and techniques to involve players in each quadrant based on their specific strength or opportunity

  • Added to My Schedule
    keyboard_arrow_down
    Tom Grant

    Tom Grant - Technical Debt Is A Systemic Problem, Not A Personal Failing

    schedule  03:15 - 04:00 PM place Tiered Classroom people 17 Interested star_halfRate

    You often hear technical debt described as a personal failing. Why didn't you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result of bigger, systemic problems.
    Chances are, you're not a bad person. You didn't want this to happen. It's the system, not you, that's chiefly responsible.
    In this talk, we will present some of the conclusions from the Agile Alliance's technical debt working group, which has looked into the systemic causes and consequences of technical debt. While marginal amounts of technical debt will always accrue, that does not explain why substantial technical debt is a widespread phenomenon. The organization in which software development teams work is the much bigger culprit. Many systemic causes, such as deadline pressures, under-investment in skills, and even the unwillingness to measure technical debt, conspire to create a growing burden on software professionals, who would otherwise choose not to create this problem if given the opportunity.
    Just as technical debt has systemic causes, the real cost of technical debt lies at the system level. The increasing drag on software innovation has effects not just on individual and team productivity, but on the software value stream, the portfolio, and the organization as a whole. Sometimes, the cost is obvious, such as the valuation of a start-up company's code; other times, the consequences are far more subtle and insidious.
    During this session, we will use the language and methods of systems theory to better come to grips with the causes and consequences of technical debt. Don't worry if systems thinking is unfamiliar — we will cover the basics during the talk. We will also do an exercise in which you will create a simple systems model of your own challenges with technical debt, and discuss how this model should help you shape a plan of action for dealing with technical debt.
    Ultimately, the goal of this session is to give you the tools to better deal with technical debt. Rather than blaming individual developers, you will be able to show the systemic sources of technical debt, and assess the relative value of addressing each of them. Rather than depending on technical measures to convey the costs of technical debt, we will help you to put the costs of technical debt in stark business terms.

  • Added to My Schedule
    keyboard_arrow_down
    Brandon Carlson

    Brandon Carlson - From Continuous Delivery To Continuous Compliance

    schedule  03:15 - 04:00 PM place Executive Boardroom people 16 Interested star_halfRate

    Continuous Delivery (CD) and regulatory compliance are two critically important ingredients in today’s connected organizations. CD enables you to move quickly and respond to change in an era where change is increasing at an exponential rate with no sign of slowing down. Regulatory compliance ensures that your organization takes the appropriate steps to follow applicable laws and appear to require adding burdensome processes and controls to your software development lifecycle. While they appear to be at odds with one another at first, they actually complement each other well. While maintaining, analyzing, confirming, and reporting on the status of required information security, compliance, and privacy controls can be difficult, integrating these tasks within your CD pipeline is easier than you think. Using examples from real-world projects in organizations just like yours, Brandon explains how to integrate compliance and reporting into your CD pipeline using tools you already know such as pair programming, Jenkins, Chef, Metasploit, and others, leading you to the regulatory promised land known as “Continuous Compliance”.

  • schedule  03:15 - 04:00 PM place Break Lounge people 7 Interested star_halfRate

    I will be hosting two 45-minute Lean Coffee collaborative conversations at AgileDC this year. One session will take place in the morning; the other in the afternoon.

    What is Lean Coffee?

    Lean Coffee is a type of discussion for the people, by the people. Participants gather, build an agenda together, and begin talking. It is sometimes called a structured, but agenda-less meeting.

    1. We will identify what we want to talk about
    2. We will vote & discuss
    3. We will identify key findings/ideas/takeaways

    Why do it?

    It's a great technique to learn when you want to spark some engaged -- yet casual, collaborative conversations around topics that are of interest to the group. You can use the Lean Coffee format within your department, across departments, as a brainstorming platform or for team retrospectives. There are many different possible applications.

    What will we discuss?

    For the AgileDC sessions, our conversation topics will be determined by you! Our theme will be pretty broad. You've probably guessed it...Agile!

    When you come to Lean Coffee, please be prepared to write down at least 1-2 topics in the form of a question.

    Examples:

    • "My organization struggles with ____. How do we take some steps to get better at this?"
    • "Here's what we're doing in regards to ____, what are you doing?
    • "What metrics do you actually use?"
    • "How big are your agile teams?"
    • "We've got some basic processes in place, but what's next?"

    When you take Lean Coffee back to your organization, the theme of each session could be a real democratic set of agile topics making for truly spontaneous networking/collaborative/experiential learning and participation opportunities, or you can announce a theme in advance and attendees will be asked to focus their topic ideas around that specific theme.

    I hope you will join me at AgileDC for a Lean Coffee conversation!

16:00

    Coffee Break & Networking - 15 mins

16:15
16:30
16:45
  • Added to My Schedule
    keyboard_arrow_down
    Ben Morris

    Ben Morris - The 12 Factor App, a primer on the 'manifesto' for DevOps & cloud-native apps

    schedule  04:45 - 04:55 PM place Ballroom D people 15 Interested star_halfRate

    If you haven't heard of The 12 Factor App, you probably will soon. Think of it as "the agile manifesto for DevOps." This talk helps you quickly become familiar with the basics of the 12 Factors that make applications cloud ready or "cloud native."

    This talk allows you to trade 10 minutes of your time in order to get a bit smarter. Learn *just* enough to be dangerous, and use that knowledge to impress developers by spewing buzzwords like persistence, disposability, statelessness, and port binding. At least be able to push back intelligently when someone is telling you the app can't be put on the cloud. Learn what is meant by "livestock, not pets" and where to find out more if the talk sparks your imagination.

17:00

    Closing Reception, Raffle, & Networking - 120 mins