Scaling: Getting Big is NOT the Answer!

schedule Sep 23rd 04:15 - 05:00 PM place Ballroom B people 14 Interested

Ask someone why they want to scale and their response is often, "So we can continue practicing agile as we grow bigger." While the pursuit of agility is a noble one, most often the pursuit of "bigness" is not. But what is?

In this talk, David Bulkin and Donald Patti will introduce attendees to three of the most popular scaling frameworks -- Scrum@Scale, LeSS and SAFe -- comparing the qualities of each. In addition, they'll explain what organizations looking to scale SHOULD pursue as they scale.

 
 

Outline/Structure of the Talk

  1. Introduction (1 minute)
  2. The Four Scaling Questions [activity] (10 minutes)
    1. Is there more to scaling than getting bigger?
    2. Is there more to dependencies than identification & visual tracking?
    3. How can we collaborate effectively when we scale?
    4. How should our teams and our organization be structured to
      scale?
  3. Popular Scaling Frameworks -- Scrum@Scale, LeSS and SAFe (25 minutes)
  4. Selecting a Framework (or Not?) (5 minutes)
  5. A Return to the Questions: [Recap & Close] (4 minutes)

Learning Outcome

Attendees will be able to:

  • Make an informed decision about when and whether to scale agile.
  • Be able to select which scaling framework is most likely to work in their environment
  • Approach scaling more wisely, by having answers to the four questions.

Target Audience

Individuals considering scaling; or, individuals in scaled agile environments

Prerequisites for Attendees

Basic understanding of agile.

schedule Submitted 3 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Bob Payne
    By Bob Payne  ~  2 months ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • Comparative analysis of 

    I think the submission could be improved by:

    • Adding details to the proposal on the patterns that do work 
    • More closely connecting the title to the body of the proposal
    • Donald Patti
      By Donald Patti  ~  1 month ago
      reply Reply

      Dear Bob (and all):

      I have adjusted the proposal to reduce the time allotted for the intro and in-class exercise so that we can spend more time on summarizing the scaling frameworks AND providing guidance on selecting a framework. This increases time for the latter two by about ten minutes, making it clear we will provide guidance on selection - not just a scaling framework overview.  

      I have also clarified in the outline that we’ll be discussing four important scaling questions, all of which relate to the overall purpose of the talk — "Should we scale, and if so, how?"

      Finally, we expect attendees will say, "If getting big is not the answer, then what is?" We answer that question at the end of the talk, in the recap, which puts a nice bow around the preceding activity and presentation.

      I hope this addresses your requested improvements, but if it does not, please let us know and we'll make another round of adjustments.

      • Bob Payne
        By Bob Payne  ~  1 month ago
        reply Reply

        Thanks this will help the evaluation team.  Much appreciated.


  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - How to REALLY use the Agile values and principles!!

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 2 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Beginner
    Your organization is doing Agile, which great, but what does that really mean? Perhaps they are implementing Scrum, or Kanban, or one of the other Agile methods, but are they really being Agile? Does it feel like you are you are doing Scrum, but you’re team isn’t really Agile? There's difference between doing Agile and being Agile and this session explores that concept.

    In this session, we’ll understand what Agile really means and how that relates to the way we implement our Agile methods within our organizations. We'll identify how we effectively use the Manifesto value points so that we can maximize the value of our products while still ensuring that we have quality and governance built into our process. This session will also explore the use of Agile principles to guide our strategic and day to day decisions.

    This sessions is great not only for beginners, but for anyone who wants to get past simply implementing Scrum or Kanban by the book, but really understand how to use Agile values and principles to build better products and organizations.
  • Liked Donald Patti
    keyboard_arrow_down

    Donald Patti / David Bulkin - Plays over Plans: Using Transformation Plays to Coach Enterprise Change

    45 Mins
    Talk
    Intermediate

    Unlike agile at the team level, enterprise agility requires cultural change throughout the organization to be successful. But, cultural change is far from easy. Much like the roots of a tree, culture runs deep, so it takes persistence and the right approach to achieve success.

    In this talk, Donald Patti and David Bulkin will describe multiple successful plays, or approaches, to enterprise agile transformation, providing attendees with a number of practical ways to understand and change an organization's culture.

  • Liked Melinda Solomon
    keyboard_arrow_down

    Melinda Solomon / Ken Moser - IV&V Just Looks Like a Four-Letter Word

    45 Mins
    Experience Report
    Intermediate

    The job of an IT Project Manager is a difficult one and traditional approaches to governance tended to make it even more difficult. In the best of times, these approaches employ Independent Verification and Validation (IV&V) as an impediment to project teams; in the worst of times, they set IV&V up as judge, jury, and executioner for projects.


    But just because that’s the way things are often done doesn’t make it right. Oversight entities can be healthy enablers instead of adversarial obstacles.

    Traditionally, the role of a governance framework is to enumerate statutory requirements, promote best practices, and reduce risk. The purpose of an IV&V team within this world is to ensure that appropriate elements of the framework are followed so as to mitigate risk. Larger projects typically present greater risks and require more controls; smaller projects less so.

    The big challenge has always been in defining what is required for a given project.

    Project sponsors want working solutions. The CFO wants tight budgets and lower costs. Project teams want happy sponsors. These stakeholders often oppose IV&V because the cost/benefit case for everything it promotes can be difficult to justify in comparison to business needs. Also, when these stakeholders do not pay directly for development costs they can have a very high tolerance for risk – but that’s an issue for another day.

    What if we re-frame IV&V from risk mitigation to added value?

    • What if, instead of requiring reams of documentation, IV&V identifies information it needs in the tools and processes already in use?
    • What if, instead of forcing teams to follow so-called best practices in cookie-cutter fashion, IV&V provided the metrics and data they need to take specific action when it is most effective?
    • What if, instead of reciting regulations to teams, IV&V worked hand-in-hand help teams meet them in the most efficient ways possible?
    • What if, instead of looking for defects, IV&V asked teams how it could help and then provided the specific support they need, where and when they need it most?
    • What if IV&V helped to onboard new teams and train them in specific skills and resources they will need to succeed?
    • What if IV&V assessed team needs as they worked together and then developed training courses to address those needs?
    • What if IV&V built project dashboards to present useful information from development tools that helped teams surface problems quickly?
    • What if these and other steps help project teams deliver value while meeting regulations, reducing risk, trimming costs, and increasing quality all around?

    What if? There is no what if. This works. It really does.

    These are just some of the innovative governance strategies that our IV&V team at USCIS has employed and it has made all the difference.

    Let us tell you more about them…

  • Liked Scott Swanson
    keyboard_arrow_down

    Scott Swanson - Drive to the Cloud: DOT’s Agile Cloud Transformation

    Scott Swanson
    Scott Swanson
    VP, Cloud Services
    Enquizit. Inc.
    schedule 2 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Moving to the cloud is perhaps the most popular trend in technology since going agile and arguably just as difficult. What happens when you combine the two?

    The US Department of Transportation (DOT) and Enquizit, an Amazon Web Services Premier partner that specializes in cloud transformation services for education, government and not-for-profits, have done just that. Though cloud transformations often take organizations one or more years, cost millions of dollars and involve a series of failures before success, The DOT’s application of agile to their cloud transitions has shaved that time down to less than 6 months.

    In this talk, presented by Arnel Rivera (DOT,) and Scott Swanson (Enquizit), you’ll learn how the DOT and Enquizit applied agile to moving to the cloud, including what they’ve changed, how they’ve done it and who’s benefited. You’ll also learn some fundamentals about agile cloud transformations that can help you to do the same.