Scaling Agile is the hot trend these days. There are various options people are currently using to scale agile across their organization ranging from the trendy SAFe through the evolutionary Kanban all the way to classic LeSS. As an enterprise agile coach with straddling both the Kanban and SAFe worlds with experience helping various global enterprises to be more agile at scale I have a wide perspective of the agile scaling approaches landscape which I will share in this session. Together we will look at the various leading approaches to Scaling and understand how they compare, where each is appropriate, how to mix and match them. We will also spend some time discussing change management/implementation aspects of using the  the various approaches and how to move through the selection, kickoff, stabilization and recharge phases and ideally move to improve mode at some point. 

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

Outline/structure of the Session

      • Scaling Agile - what is the problem we are trying to solve
      • Short introduction to the various options
      • A bit more emphasis on Scaling using Kanban:
        • Expand/Collapse to deal with Scaled Agile Requirements such as Features, MMFs, Stories, Tasks
        • SOA Kanbans to deal with special services teams compared to feature teams
        • Dealing with complicated functions such as technical-writing, performance testing, UX that are typically hard to co-locate with all teams
      • Criteria for comparing and selecting an appropriate scaling approach for your context
      • Real-world examples for right and wrong choices of scaling approach - and what we can learn from it. 
      • Fitting a scaling approach within change management phases - Thinking/Selection, Kickoff, Stabilization, Recharge, Improve.

the session can be adjusted to be a deeper talk or even a workshop, depending on the needs of the program. 

Learning Outcome

  • Have a basic familiarity with key agile scaling approaches - SAFe, LeSS, Spotify, Kanban
  • Know when to consider which scaling approach. 
  • Know how to apply kanban thinking/practices to your scaling challenges.
  • Understand how the agilesparks way can help you manage your agile scaling journey

Target Audience

Agile Coaches, Development Managers, Program Managers, Change Agents

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Tathagat Varma
    By Tathagat Varma  ~  1 year ago
    reply Reply

    Yuval - surely, scaling agile adoption is a hot topic, and there are enough number of options to choose from. As this is an emerging topic, it will be helpful to compare and contract various approaches. I also saw you have mentioned you will look at some real-world examples - that will be very helpful. It there a strawman of your deck for this talk that we could look at?

    -TV

    • Yuval Yeret
      By Yuval Yeret  ~  2 years ago
      reply Reply

      Hi TV,

      I don't have a deck for this talk currently. I can tell you the real-world examples will including pull-based change using Enterprise Kanban, Scaled Agile Framework by the book, Home-grown SAFe-like release planning to accompany semi-autonomous feature teams, autonomous feature/product teams. This will all come from work with AgileSparks clients. Before the actual talk I will check my ability to refer to the customer by name, probably some of them will release their name and some won't.

      • Jerry Rajamoney
        By Jerry Rajamoney  ~  2 years ago
        reply Reply

        Hi Yuval,

        Nice topic. Thanks the same.

        Since your topic said Scaling Agile which is definitely more than any of these frameworks (LeSS / SAFe), do you going to share some points on that perspective or you are going to stick to the recommendation from these existing frameworks?

        Regards,

        Jerry

        • Yuval Yeret
          By Yuval Yeret  ~  2 years ago
          reply Reply

          I plan to compare the Less/SAFe frameworks as well as Enterprise Kanban / Spotify approaches and share my perspective on where each framework would be a good fit from social and technical perspectives. I definitely will NOT stick to the "by the book" recommendations of each framework. There are some contradictions between them that will need to be addressed :-)

           

          I Hope this helps understand better.

           

      • Tathagat Varma
        By Tathagat Varma  ~  2 years ago
        reply Reply

        Thanks Yuval. Actual names of clients are not required, as long as we can share the learnings and insights from the 'type of work' and help audience relate to various options, each with its own pros and cons, so they can understand more than one ways to solve a problem.

  • Prasad
    By Prasad  ~  2 years ago
    reply Reply

    Yuval,

    What is the context of scaling - is it a software prouct?  Enterprise IT?  will you be including the typical journey and key challenges faced?

    ~PP

  • Steve Ropa
    By Steve Ropa  ~  2 years ago
    reply Reply

    Hi Yuval, 

    This looks like a good talk.  As it is focused specifically on scalihg agile, I wonder if it is too specific for a keynote?  It looks like a session I would attend, but I usually expect a keynote to be a little more wide ranging. Might I suggest this talk would get a more active and interested audience as a talk than a keynote?

    • Yuval Yeret
      By Yuval Yeret  ~  2 years ago
      reply Reply

      Hi Steve,

      In my experience there are at least two kinds of keynotes. One is the wide ranging visionary ones which have implicit/indirect interest/influence on the topic of the conference. (e.g. bringing in Dave Snowden to talk about Complexity, Chet Richards about Boyd's work, Stephen Bungay about Leadership, all great keynotes) 

      Another is the more explicitly relevant down-to-earth keynote which takes a topic which is a strong trend in the industry that people are highly interested about and tries to give a high level view of it introducing people to the concepts from the perspective of someone with strong experience/oppinion on the topic which can hold the crowd. 

      I'm aiming at the second alternative with this talk. Whether it can be that or not, I'll let others decide. But I think the category is certainly relevant for keynotes at least in my understanding. You can also call it "Main Stage" in other conference. 

       

  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Yuval,

        To be completely transparent, my first concern is that this keynote is an attempt at pushing another scaled idea, i.e. your agile parks way as 'the best way'.  While that probably isn't your intent, if that was my first thought I'm concerned it would be the first reaction from more people.  Perhaps you could reframe the session with that in mind.

    Also, is this presentation just about presenting various 'scaled' frameworks or are you going to be looking at why the need to scale in the first place, etc?

    Best,

    Joel

    • Yuval Yeret
      By Yuval Yeret  ~  2 years ago
      reply Reply

      Good point Joel. I can see how people might perceive this to be the goal of the session although as you guessed that is not my intent. AgileSparks Way is not a scaling approach anyhow. it complements any approach you choose by focusing more on implementation/change management approach rather than the actual agile practices you choose.

      Based on your feedback I chose to deemphasize the agilesparks way in the abstract/outline and emphase the user story behind it instead - the need to go through various implementation phases and be aware of the different focus and goals in each.

      • Joel Tosi
        By Joel Tosi  ~  2 years ago
        reply Reply

        Hi Yuval,  

           I do like the changes you made.  I am trying to get feedback to more sessions that are still missing feedback but will circle back around.

         

        Best,

        Joel


  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - Understanding and Implementing DevOps Flow

    Yuval Yeret
    Yuval Yeret
    Enterprise Agile Coach and CTO
    AgileSparks
    schedule 2 years ago
    Sold Out!
    480 mins
    Workshop
    Intermediate

    DevOps seeks to extend the agile benefits of Flow, Collaboration, Inspect and Adapt thinking all the way to Production. While DevOps and Continuous Delivery were born in the world of web operations in companies like Etsy, Google, Amazon, Facebook and Flickr (also called Unicorns in the DevOps community) it is now clear that Enterprise IT/Product Development companies (also known as Horses) can  also benefit immensely from the ideas and practices and achieve similar results if they manage the change/journey towards DevOps in a way that makes sense in their context. In this workshop we will introduce the concepts of DevOps and Continuous Delivery and help attendees figure out how DevOps can fit into their world as well as how a “DevOps Implementation” might look like.

  • 45 mins
    Talk
    Advanced

    Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:

    1. Why plan-driven IT projects are a bad idea why we need value-driven projects instead
    2. Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
    3. Why IT budgeting needs to change from being project-based to being team-capacity based
  • Liked Pooja Uppalapati
    keyboard_arrow_down

    Pooja Uppalapati / Ravindra Chebiyam - Scaling Agile in a Mainframe Product Development Organization

    20 mins
    Experience Report
    Intermediate

    Agile transformation in any organization will go through myriad of challenges that involves people, existing organization culture, technology/domain etc. Instead of seeing these challenges as obstacles, if you view them as opportunities to grow and improve, transformation will be more impactful and long-lasting. If neglected, the very same obstacles would severely damage the motivation and trust of employees.

    In this experience report we would like to walk you through the agile transformation journey in a Mainframe product development enterprise by unraveling the challenges and the remediation steps that has helped us in keeping this journey alive. Specifically we would like to touch upon 

    1. Self-organizing teams
      • Resistance to change
      • Culture shift
    2. HR
      • Lack of role clarity and
      • Effective R&R in agile space
    3. Agile Engineering Practices adopted in Mainframe product development
      • Unit test automation
      • Continuous Integration

    Along the presentation we’ll highlight few anti-patterns and the effects of ignoring them.

  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - Good and bad ways to kickstart agile the Kanban way

    60 mins
    Talk
    Beginner

    In fall 2014 there is no question that business agility is required. You will also be hard pressed to find anyone arguing against the core principles of lean/agility or against most of the practices. But most enterprise organizations have not yet reached the levels of agility you read about in books or hear about at conferences. Lean/Agile is now trying to cross the chasm into the mainstream enterprises where effective change management for today’s context is the name of the game. Through stories from the trenches of enterprise change management we will discuss different approaches to change and when each is appropriate. We will see how a combination of the Kanban evolutionary approach to change combined with "free market / pull based change management" helps accelerate the journey towards agility without risking its stickiness, and share some hard-learned lessons that resulted in patterns like “Manager’s first”, “Document/Methodology later”, “Market & wait for Pull”, “Case Study”, “Opt-in vs Mandate”, “Guidebooks OVER guided tours”. 

  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - Kanban - A Way Towards DevOps in the Legacy Enterprise

    45 mins
    Talk
    Beginner

    DevOps is a higher form of agility. It is a blueprint for a great culture and and process between the different groups involved in the delivery pipeline. The big question is how to achieve it. If you are founding a startup today, it can be quite easy to take that blueprint and use it to create your process, hire the right versatile flexible people, and start delivering without any technical/automation debt or friction. But most of us are not founding new startups. Most of us already have a running operation with people, culture, process that matured over the years and despite its flaws is currently the way we do things. Changing that is non-trivial. For things to change people need to understand WHY change, what we are changing, and we need an effective process for managing the change itself (HOW to change). So what ARE we changing to? DevOps is highly focused on looking at the whole value stream from idea to value and ensuring effective flow through this pipeline. Kanban is ONE way of HOW to change. It starts by visualizing all the work flowing in the pipeline, then managing the flow focusing on finishing things end to end rather than starting in order to stay busy. It continues to what we call the “Work in process Diet” – Straining the flow more and more in order to identify obstacles to tighter and tighter DevOps culture/operation and faster feedback cycles. You can expect to come out of this session with ideas how to take your current operation and DevOpsify it in a safe evolutionary way using the Kanban method.

  • Liked vinaya muralidharan
    keyboard_arrow_down

    vinaya muralidharan / Sutap - The Snowball Effect - From Team Kanban to Enterprise Kanban

    20 mins
    Experience Report
    Intermediate

    About two years ago, we embarked on our journey towards Agility and Kanban was our vehicle.

    But Kanban had people worried.

    How can we not have detailed plans?! How can we limit WIP when we have so many things to work on?!

    We have due dates to meet! And so on.

    We would like to share one of the approaches that we adopted to help move the change along.

    In addition to focusing on the Kanban implementation at the project levels, we adopted another route – to work through the individuals and the teams – a grounds up approach. We encouraged people and teams to use Kanban boards to manage their daily tasks.

    You have difficulty in managing personal stuff? We’ll help you manage better!

    You have issues in managing team level priority? Look what we did within our team- we have a Team Kanban and we are now much better organized!

    One by one we saw people getting interested. The movement gathered steam - we worked directly with a handful of people and they in turn got their peers onboard. And we saw various flavors like Personal Kanban, Team Kanban cropping up all over the place – even in our Travel Office and Corporate Office. What this did was give people a safe, controlled environment to experiment and learn in.

    As they got used to the ideas of limiting WIP, pulling work, visualizing work and “stop starting, start finishing”, it gave them the confidence to work this way at the project level too. And it made our lives as change agents just a wee-bit easier!

    We welcome you to come hear our story about nurturing the change towards Agility by making it a grass roots movement.

    A brief introduction to Amdocs - Amdocs is a leading provider of Customer Experience systems and services in the telecommunications domain, typically doing large scale transformation projects.

  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - ScrumBan - Boosting your Scrum using Kanban/Flow

    480 mins
    Workshop
    Intermediate

    ScrumBan is a hybrid Lean/Agile approach combining Scrum and Kanban. It combines the team-focused rhythmic nature of the Scrum Framework with the Lean/Flow focus of Kanban to create a winning combination. This workshop provides attendees with sufficient knowledge about Scrum, Kanban and Scrumban to lead or guide a team in their adoption of ScrumBan – from system design through to evolutionary change. They will have an understanding of the principles and thinking behind Scrum and Kanban to help them drive meaningful focused continuous improvement using context-specific strategies/practices.

  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - Agile Boost Camp - Accelerate your path to a healthy and sustainable Agile Process

    480 mins
    Workshop
    Intermediate

    So, you started adopting Agile practices, maybe you took a course or read some books and articles and decided to jump into the water. Good for you! However, you quickly realize things don’t work the way they used to. It feels like chaos, it is typically painful and frightening and you have many questions and concerns. Over time, you might find a way of working that makes sense, but most likely, you will still stay stuck with some of the pains or avoid challenging some of the things that do not allow you to become truly Agile.


    In this workshop we will leverage our vast experience with AgileSparks clients all over the world to provide participants with practical tips and tricks, patterns and anti-patterns and good practices that can accelerate your path to a stable, healthy and sustainable Agile way of working as well as boost your performance.




  • Liked Yuval Yeret
    keyboard_arrow_down

    Yuval Yeret - Modern Agile Change Management approaches leveraging Kanban & pull-based change

    480 mins
    Workshop
    Advanced

    In fall 2014 there is no question that business agility is required. You will also be hard pressed to find anyone arguing against the core principles of lean/agility or against most of the practices. But most enterprise organizations have not yet reached the levels of agility you read about in books or hear about at conferences. Lean/Agile is now trying to cross the chasm into the mainstream enterprises where effective change management for today’s context is the name of the game. Through stories from the trenches of enterprise change management we will discuss different approaches to change and when each is appropriate. We will see how a combination of the Kanban evolutionary approach to change combined with "free market / pull based change management" helps accelerate the journey towards agility without risking its stickiness, and share some hard-learned lessons that resulted in patterns like “Manager’s first”, “Document/Methodology later”, “Market & wait for Pull”, “Case Study”, “Opt-in vs Mandate”, “Guidebooks OVER guided tours”.

    In this interactive workshop we will explore the various techniques in depth through case studies, consider their pros and cons compared to classic change management approaches like the mandatory/perscriptive rollout and establish criteria for when to use which approach in the field.

  • 60 mins
    Talk
    Advanced

    There is a world of difference between the management principles in the era of the Industrial revolution to the current world of information revolution. We need to acknowledge the increasing gap between the way employees are being managed at work, and the way they want to be managed. Many surveys have been done in this area, ending in headlines like “6 out of 10 employees are miserable” and “74 percent of staff not engaged at work.” Dig into these surveys and you’ll see the quality of leadership on top of the list of complaints. The poor state of leadership and management skills in organizations is being driven by a broad range of factors, including but not limited to

    The changed nature of work - More of skill and innovation

    The increasing education of employees - Continuous improvement and learning needs

    The needs of later generations - The more sofisticated needs of the system

    The pace of change - The quick pace of changes

    In the current “rat race”, the management focusses on higher productivity and higher ROI, but they lack the capacity to “motivate” their employees that can take them to the next level of thinking. The "leaders" do not understand the subtle difference between teaching, mentoring and coaching. They use these words interchangeably without realizing that coaching teams can help them to increase the productivity, morale and create great employees resulting in more successful products.

    A new coaching model is required to enable continous improvement with quick feedback cycles that fosters adaptability and innovation.

    Two relevant quotes which I can relate to this issue are

    "It is people who build organizations and not organizations who make people" - unknown

    "Beware of little expenses; a small leak will sink a great ship" - Benjamin Franklin

     

  • Liked Hrishikesh Karekar
    keyboard_arrow_down

    Hrishikesh Karekar - An Empirical Approach to Agile Transformations

    Hrishikesh Karekar
    Hrishikesh Karekar
    Agile Coach
    Amdocs
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Enterprises big and small are aspiring for agility these days and kick-starting Agile transformations. Agile is mainstream. The movement that started with a manifesto and principles has grown bigger. From product development and startups, agile is now being adopted in mainstream (read legacy) companies for all kinds of knowledge work beyond the scope of pure product development – in services, support, marketing, HR and so on.

    With the widespread application, many ways to achieve agility have also sprung up. We have ScrumKanbanScrumbanSAFe and probably few more variations. Each have their benefits and challenges depending on the organizational context that they are being used into.

    For organizations that are just starting, this plethora of information is quite confusing and intimidating sometimes too. Transformations also involve a lot of investment - both financially and otherwise. Its a big change. Deciding on an approach at the outset is not trivial. 

    The talk would suggest an approach to Agile transformations that is based on the fundamental premise of Agile - the empirical philosophy of transparency, inspection and adaptation and provide practical tips and tricks based on my experience with large scale transformations.