Does your organization or team’s Agile practice feel stale? Do you believe your team can reach a higher level of performance but not sure what the next step is?

Marie Dingess and Christina Murto will share the changes we have fostered over the past couple of years to move our Agile game to the next level at Capital One.

We will highlight the “seeds of change” we planted and cultivated in our Digital Technology space as well as patterns we saw as teams evolved their practices including:

  • Lean, Systems Thinking, Kanban/Scrumban
  • Continuous improvement (leveraging PDCA & Improvement Kata)

We will speak to considerations for trying these practices, tools and techniques, and showcase the results:

  • Quantitative improvements: decreased cycle time and increased story throughput
  • Qualitative measures: improved morale, team ownership of processes, and engaged Product Owners.
2 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

[5 min] Intro

  • Our Agile Journey
  • Areas of Opportunity
  • Areas of Focus to address the opportunities
    • Lean Kanban/Scrumban
    • The Scrum Master Role
    • Continuous Improvement

 [10 min] Lean Kanban/Scrumban

  • Team Level
    • Lean Systems Thinking Workshops & GetKanban
    • Key changes & emerging patterns
    • Highlight of Results – quantitative (cycle time, story throughput) & qualitative (morale, ownership, engagement)
      • Video clip of Engineer presenting at a Gemba Walk
    • Leadership Level

 [10 min] ScrumMaster Community

  • New Vision for the Role (including optimize flow & experimental mindset) and socialization to leadership and community
  • ScrumMaster CoPs & Book Clubs

 [10 min] Continuous Improvement

  • Continuous Improvement Approaches (PDCA, Improvement Kata - Programs and Teams)
    • Program Example - Reducing Cycle Time by Examining Shared Service Process Flow
    • Team Level - Focus/Approaches for Scrum Masters

 [5 min] Lessons Learned / Change Principles

  • Connecting and Aligning the Enterprise & Local - Agile Double Down Program
  • SAFe Progam and Team Kanban conflict
  • Bottom up engagement is more difficult
  • Providing flexibility at the local level made aligning on some areas difficult (such as Metrics)

 [5 min] Q&A

Learning Outcome

  • How Identify Areas of Opportunity for Improving Agile
  • Tools, Techniques and Approaches to Introducing Changes
  • Importance of a Robust Approach to the Scrum Master Role
  • Using Quantitative and Qualitative Measurements

Target Audience

Scrum Masters, Coaches, leaders and engineers


Basic familiarity with Agile and Scrum.

schedule Submitted 3 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  1 week ago
    reply Reply

    Christina, Marie,

    A bit more about the content and mechanics would help the reviewers evaluate this proposal.

     - George

    • Christina Murto
      By Christina Murto  ~  5 days ago
      reply Reply

      Hi George - We've updated our outline to provide more details.  

      Please let us know if there's anything else the reviewers need.

      - Christina  & Marie

  • Liked Colleen Johnson

    End to End Kanban for the Whole Organization

    45 mins
    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.  
  • Liked Matt Badgley

    Becoming a High-performing Team Doesn't Happen Overnight, It Takes Practice

    45 mins

    Have you ever been a part of a team that attended some form of Agile training for a day or so, and then expected to go forth and be Agile?

    Or, even worse, have you ever been asked to help a team improve, but the team found themselves too busy to improve?

    I unfortunately have said yes to both of these questions and for each, the result wasn’t good and as a leader of the teams impacted — I failed them. After these and many more frustrating experiences, I set out to figure out what needs to change in order to improve the outcomes and help make people awesome. In this session, I want to share what I discovered.

    During this interactive session, we’ll brainstorm the areas that we struggle, explore the aspects of becoming good and high-performing, and we’ll establish a baseline understanding of agile practices. We’ll dive into the concept of deliberate practice and look at how we create an environment that enables deliberate practice to occur. Finally, we’ll wrap-up with a group discovery of practices the we’ve used in the field to overcome the areas that we struggle.

    Please join me for an outcome focused, practice based coaching discussion.

  • Liked John Tanner

    The GQM Approach to Enterprise Agile Metrics

    45 mins

    When undertaking an Agile transformation, there is a need to collect data to demonstrate progress and show improvement, but where does one even start? Common Agile metrics approaches do well at measuring team velocity and throughput, but can sometimes overlook the requirements of executive sponsors, product management, and other key stakeholders. This problem is often rooted in a lack of understanding about what business goals are driving decision making throughout the organization and what questions we should be answering with the metrics we collect.

    The “Goal-Question-Metric” (GQM) approach is a proven method for driving goal-oriented measures throughout a software organization. With GQM, we start by defining the goals we are trying to achieve, then clarifying the questions we are trying to answer with the data we collect. By mapping business outcomes and goals to data-driven metrics, we can form a holistic picture of the Agile environment and clearly articulate how we are doing across the span of the enterprise.

  • Liked Jolly Rajan

    WIP it! How slowing it down makes you go faster

    10 mins
    Lightning Talk

    Traditional management techniques have emphasized Utilization as a key metric to increasing team productivity. Agile and Lean management techniques, instead, focus on reducing Work In Process (WIP) and building in Slack as the key to decreasing cycle time and increasing team efficiency. In this session, we will take a look at the correlations between these seemingly unrelated data points and how teams can leverage it to deliver value faster.