Let's Get Real About Agile Training for the Enterprise

As Agile has become a popular buzzword for the C-Suite, more organizations are taking the plunge into scrum and scaled agile from the top-down and expecting to reap the benefits of being a highly mature agile organization quickly. Easy training solutions like internal or vendor-delivered Agile 101 or even an enterprise-wide CSM certification are woefully inadequate, and potentially harmful, for a successful agile transition. In this workshop we'll learn a more realistic and effective (and less expensive) way to train an agile organization.

 
4 favorite thumb_down thumb_up 5 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. We discuss the problem: Even trained and certified scrum masters, product owners, team members, and executives often don't know how agile applies to them an are unable to articulate or implement how agile works in their world.
  2. We offer our solution: Instead of expensive and time-consuming general training such as CSM, Agile 101, or other variants, opt for a curriculum of highly contextual training, delivered in short bursts over weeks and months and reinforced with teams daily. We present our favorite "curriculum" of agile/lean concepts and discuss how to teach and introduce them in context.
  3. We demonstrate the solution: We will present (and potentially add to) the key lean/agile concepts and curriculum for review and re-prioritization by the attendees. Then, we'll take the top priorities build out contextual applications and learning opportunities that the attendees can use immediately in their day jobs. 

Learning Outcome

A new understanding of how to effectively train teams in context to ensure long-term understanding and the ability to apply the concepts in the real world.

Target Audience

Experienced agile practitioners and coaches OR management hoping for the best training for their teams.

schedule Submitted 2 months ago

Comments Subscribe to Comments

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

    Travis, can you expand what you mean in the Outline/Structure of the session? Point 2 is too terse for me to be sure what you mean. A few examples might help me understand point 3.

    • Travis Bjorklund
      By Travis Bjorklund  ~  1 month ago
      reply Reply

      Let me know if the updated outline makes more sense. The idea is for a very interactive and very applicable session.

      • George Dinwiddie
        By George Dinwiddie  ~  1 month ago
        reply Reply

        Travis,

        Please say more about "highly contextual training, delivered in short bursts over weeks and months and reinforced with teams daily." I cannot envision what this looks like.

        And if people haven't had an overview of lean or agile, how do you sequence the lessons and transition so that they continue to be productive and gain benefit?

         - George

        • Travis Bjorklund
          By Travis Bjorklund  ~  1 month ago
          reply Reply

          Sounds like you need to come to the session! :)

          Seriously, though, let's take an easy example. Agile 101/CSM will introduce you to the concept of three scrum roles: the product owner, the scrum master, and the team. Ok great. But my organization doesn't have scrum masters. We have delivery managers. And we have project managers. And we have business analysts. Who is the product owner? How does our organization differ from "out of the box" scrum? How can we make it work in an existing organizational structure? How do we have a good backlog when the product owners don't know how to do that yet?

          So to solve the problem we need to change a few things--focus on one or two ideas at a time (rather than Agile 101, for example, which introduces dozens and dozens at once), and then work through the individual challenges the team is having with them in real life. We also need to change the length of the training--one or two full days every week obviously isn't going to happen. So we have a deep dive into product ownership with the whole team for an hour or two--then we apply it for the rest of the sprint. 

          That's the idea. During this session, we'll actually pull out real examples of organizational challenges from the audience and address how we succeed in delivering business value using agile principles under those circumstances. 

          Make sense?

    • Travis Bjorklund
      By Travis Bjorklund  ~  1 month ago
      reply Reply

      Absolutely. I’ll make updates directly on the description.

       

       

       

      From: AgileDC 2017 [mailto:info@confengine.com]
      Sent: Sunday, June 25, 2017 4:54 PM
      To: Travis Bjorklund <TBjorklund@captechconsulting.com>
      Subject: New comment posted on Let's Get Real About Agile Training for the Enterprise

       

      Dear Travis Bjorklund,

      Your proposal Let's Get Real About Agile Training for the Enterprise has received a new comment from george-dinwiddie

      Travis, can you expand what you mean in the Outline/Structure of the session? Point 2 is too terse for me to be sure what you mean. A few examples might help me understand point 3.


      Visit https://confengine.com/agiledc-2017/proposal/4203#comments to respond to the suggestion OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

      Regards,
      AgileDC 2017 Team
      speakers@agiledc.org

      You have received this important update from ConfEngine on behalf of AgileDC 2017.
      Download ConfEngine's Mobile App to totally personalise your conference experience.
      If you are 100% sure, that this email was sent to you by mistake, please click here to unsubscribe from all future email updates from ConfEngine.


  • Liked Colleen Johnson
    keyboard_arrow_down

    Colleen Johnson - End to End Kanban for the Whole Organization

    45 mins
    Talk
    Intermediate
    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 Leland Newsom
    keyboard_arrow_down

    Leland Newsom - Comparing Scaling Frameworks - LeSS and SAFe

    Leland Newsom
    Leland Newsom
    Agile Coach
    CapTech Ventures
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Scaling Agile is easily misunderstood. Scaling is the term we often hear used to describe using Agile methods with large enterprises.  Larger enterprises often deal with bigger and more complex problems than small ones. They have more employees, subcontracting companies, different business units, more processes and a strong culture that defines how things are done. At the same time, they need to be able to deliver results in an ever-changing business environment. They need to be Agile but the bigger the company, the bigger the challenges are for scaling Agile. 

     

    Scaling frameworks available in the market today are maturing quickly and provide a variety of choices. Like the Agile Manifesto, these frameworks are based on principles, and they vary widely in the specificity of the recommended approach.

     

    In this session, we will compare how two scaling frameworks, LeSS and SAFe, address the challenges of agility at scale.  We will talk about how these two frameworks align, coordinate, and manage dependencies across multiple teams to maintain consistency and agility at scale. 

     

  • Liked Will Fehringer
    keyboard_arrow_down

    Will Fehringer - Breaking Free: How to Promote Innovation for Teams that Feel Shackled by SAFe

    Will Fehringer
    Will Fehringer
    Senior Consultant
    CapTech
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Everyone hopes that Agile will help increase innovation at their company.  But in the scaled, commitment-driven world of SAFe, organizations are finding it more and more difficult to innovate.  Learn some of the common barriers to innovation in SAFe organizations and what you can do to avoid them.

     

  • Liked Elisabeth White
    keyboard_arrow_down

    Elisabeth White - Culture Eats Process for Breakfast

    Elisabeth White
    Elisabeth White
    Agile Transformation Lead
    CapTech
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Executive

    "A brittle Culture can doom even a great organization." - Joe Tye

    "How do things get done around here?" It seems like such a simple question to answer, but pause, and try to answer that for yourself. And not from a process perspective. Do you truly understand the purpose (the why) behind the work being conducted? Does the working environment support that purpose and would you consider it a thriving or surviving environment?

    Defining what an organization wants to achieve and how it will go about achieving it is a critical step that many organizations completely overlook. We are quick to jump to process conclusions yet if an organization is going to experience a thriving Agile journey, they should first understand: how things get done around here. 

    Start with Culture - the foundation that leads to thriving Agile journeys.

  • Liked Elisabeth White
    keyboard_arrow_down

    Elisabeth White - Did you pack the 12 Agile Principles on your Agile journey?

    Elisabeth White
    Elisabeth White
    Agile Transformation Lead
    CapTech
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The 12 Agile Principles from the Agile Manifesto are building blocks for a successful, sustainable Agile journey - regardless of industry and/or department. Many pitfalls that organizations experience are due to oversight and lack of adherence to the Agile Principles. In this session, I will review the 12 Agile Principles, how they apply to all industries, common issues that lead organizations astray, and proven solutions to get back on course throughout any Agile journey.

  • Liked Hunter Willett
    keyboard_arrow_down

    Hunter Willett - "Frameworks are Like New Golf Clubs, They Won't Fix a Terrible Swing" How Understanding the Principles of Agile is the First Step

    Hunter Willett
    Hunter Willett
    Senior Consultant
    CapTech
    schedule 2 months ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    We have all been there, a shiny new and improved framework is released and we must implement it, but is this always the answer to improve your Agile organization? Frameworks are needed and provide guidelines for teams but if the teams/companies do not follow the principles and fundamentals of the Agile Manifesto it makes it very difficult for the framework to be successful. The belief is that switching up the specific framework is the answer but they soon realize that the framework is not the main issue that is the driving force. This can leave the teams/companies in a tough situation after committing to a framework that they are not ready for.

    I will be sharing my experiences across multiple different companies on how this assumption has let them down and how we had to return the teams back to the fundamentals to solve the issues they are experiencing.

  • Liked Leland Newsom
    keyboard_arrow_down

    Leland Newsom - The Role of Leadership in Scaling Agile

    Leland Newsom
    Leland Newsom
    Agile Coach
    CapTech Ventures
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The VersionOne 11th Annual State of Agile Survey for 2016 found that enterprise agility is increasing throughout organizations and across almost all industries at an accelerated rate.  Respondents from very large organizations, employing more than 20,000 people, also increased.  Scrum and scaling frameworks are getting a lot of attention at these large organizations as a way for them to do Agile, but the focus is getting the processes and tools up and running over the individuals and interactions.  Once these frameworks are deployed, the leader responsible for bringing the process change into the organization declares success and slaps the Agile label on their process and there is a belief that implementing Agile methods will generate culture change.  The culture remains one of compliance to the process over customer satisfaction, self-direction and continuous improvement. 

     

    In smaller organizations, having a clear line of sight between the employee’s daily work and the business value they are delivering is easier to establish and communicate.  In the larger organizations, the line of sight to the customers becomes much more elusive.  This lack of line of site to the customers puts the employees in silos of work that gets prioritized by urgency versus importance and often quick hits versus real business value.  Without clarity and alignment, people begin to disconnect from the purpose of their daily work and become order takers. 

     

    In this session, we will discuss the role of the agile leader in creating the culture where people can be successful in their jobs. A culture where everyone is aligned, engaged, and continuously improving so agility can take hold and thrive.  We’ll discuss using high alignment to create an engaging environment with Autonomy, Mastery, and a shared Purpose that values Individuals and Interactions over Process and Tools. 

  • Liked doug huffman
    keyboard_arrow_down

    doug huffman - Are You Being Agile or Doing Agile? Why Not Both?

    45 mins
    Talk
    Intermediate

    Nearly every organization that undertakes an Agile journey eventually runs into these questions: How do we measure progress? And how do we justify our activities and budget appropriately?

    The need to answer these questions has led many organizations to adopt agile-assessment models. When asked to measure agile progress, I recommend looking at specific aspects of how organizations are being agile and doing agile; determine where they need improvement; and then make positive changes in those areas that will deliver the greatest business value and the greatest ROI.

    • Transformation or “Being agile” is about the mindset within the company. It involves changing internal processes and ensuring that, as a group, you maintain a high level of energy and excitement about the changes.
    • Performance or “Doing agile” is about how well you are performing in the environment, rather than how well you are changing the mindset within the company.
  • Liked Travis D Dent
    keyboard_arrow_down

    Travis D Dent - “Everyone has a plan until they get punched in the mouth” Mike Tyson…. But what happens after you get punched

    Travis D Dent
    Travis D Dent
    Manager
    CapTech Consulting
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Everything we do in life and in work can have a hiccup.  No matter how much we plan, we are bound to run into things we did not account for.  The military refers to this as “Murphy’s Law”.  But what happens when you’re graced with an unforeseen change?  Mike Tyson describes it best: “Everybody has a plan until they get punched in the mouth.”

    This talk will focus on tactics within communication, transparency, and execution that teams/organizations can use after life’s curveballs have hit and it’s time to get back on track.

  • Liked Colin Ceperich
    keyboard_arrow_down

    Colin Ceperich - Agile Transformation without Change Management? … Like Diving in the Deep End without Knowing the Depth

    Colin Ceperich
    Colin Ceperich
    OCM Senior Lead
    CapTech
    schedule 2 months ago
    Sold Out!
    10 mins
    Tutorial
    Intermediate

    While individual teams frequently experience new levels of productivity after adopting Agile, those same practices when applied more broadly rarely align with an organization’s existing norms, especially with regard to management style. It is often those techniques that got middle managers promoted that need to desist. For example, instead of pushing their team to over-deliver to the client an Agile product manager is better served by supporting the team in giving the customer just a fraction of potential value, sooner. Such adjustments are hard to address, but if they’re not, managers and team members become misaligned – some hold on to what worked previously, and others embrace new Agile approaches and expectations. This is borne out repeatedly in assessments that look at Agile and organizational culture.

    Recently, Agilists representing 20+ Agile transformations at Fortune 500 companies were surveyed about the factors that most influence a successful transformation, positively or negatively. The two factors, among 24, that had the greatest influence – both as a roadblock and enabler – were Supportive IT leadership and Senior Executives Who Clearly Understand the Case for Change (to Agile).  

    These results speak to the reality that scaling Agile requires more than organic growth or a “Coach them and it will happen” mentality. Transforming the organization, any significant transformation, requires highly engaged leadership who deeply care about the change, the goals and the path. Aligning the organization during Agile transformation can be done with an approach that is typical for organization change managers.

    This talk will explain how to apply change management to your Agile Transformation so that ceremonies are better integrated, culture changes are more clearly defined and addressed, and management is positioned to lead the organization through the changes – all so that your organization delivers better results for its customers faster.

  • Liked Jesse Fife
    keyboard_arrow_down

    Jesse Fife - Stop pulling teeth! - Ice breaker activities for big group meetings

    10 mins
    Lightning Talk
    Beginner

    How can we avoid those painful awkward silences in meetings and ceremonies with large groups (big room planning, inspect & adapt/multiple team retrospectives, etc)? How can we get better participation and discussion in these meetings so that more than just the extroverts and senior team members participate? Do an ice-breaker activity! 

    By getting people to move, interact, work together, and even have some friendly competition we raise the level of energy in the room and break down some introverted inhibitions. Feel less like you are pulling teeth to get people to speak up and participate. Improve the quality and depth of your discussions by getting perspectives from more team members regardless of their title or tenure.

    In this lightning round we'll do a kick-off ice-breaker activity that can be used to start a large group meeting. We'll also share and discuss other ideas for group games and activities. 

  • Liked doug huffman
    keyboard_arrow_down

    doug huffman - Transforming Technical Managers into Agile Leaders

    45 mins
    Talk
    Intermediate

    In my experience shepherding agile transformations, I see natural tendencies to focus support of role transformation at the executive level and at the team level.  We partner executives with coaches to guide them into new ways of leading delivery, and train and coach individuals into new team level roles such as product owners and scrum masters.  Despite acute awareness of key role transformation requirements, organizations tend to neglect the crucial middle management level of technical managers who are key in driving and sustaining agile transformation, as much, or more so than even executive and team level roles.

    In this session we will explore the vital transformation of technical managers into agile leaders through a deeper dive into the following themes of delivery leadership,

    • Educating managers for a new way of leading technology delivery
    • Optimize the delivery system over optimizing individuals and directing teams
    • Coach and mentor staff, collaborate with peers and hold executives accountable
    • Drive the technology strategy, empower others to execute on the tactical 
  • Liked Colleen Johnson
    keyboard_arrow_down

    Colleen Johnson - Five Data Types for Continuous Improvement

    45 mins
    Tutorial
    Intermediate
    As Agile coaches we often spend a lot of time coming up with varied formats for our team retrospectives however what we are really trying to achieve is gathering better data. After hosting countless retrospectives both in person and online, I started paying more attention to what types of things people were posting. I sorted through stickies, spreadsheets, and flip charts and distilled all of the types of cards posted into five key types of data that are critical to great retrospectives. These are Stats, Events, Kudos, Observations, and Past Retros. Stats look at concrete numbers and performance metrics like through put, velocity, and cycle time and give teams something measurable to improve against. Events help the team create a shared context and invite memories of what took place. Kudos for a job well done set a positive tone for the team to open up. Observations allow everyone on the team a chance to be heard and express their unique point of view. And lastly, past retro data keeps us accountable and action-oriented in our improvements so we never get stuck. In this session we will walk through why each of these are important and HOW to make sure you get a good balance of all five types of data.