Agile development isn’t any longer considered to work for small teams only. Also large teams, projects and organizations are asked to focus on delivering value. So the question arises, how to adhere to the agile principles when applying them in the large.

In this workshop we want to use the agile principles as a guideline for scaling. This is basically by understanding agile as a value system, a mindset, a culture – and not as a tool. So be prepared to being asked to think for yourself and to balance forces based on your own needs and requirements instead of finding a recipe that assumes that one size will or can fit all (organizations, projects, products, or teams). Thus, this workshop is not about providing or defining a framework for the enterprise or the organization, scaling scrum or using other existing methodologies at different organizational levels. It is about examining the agile principles according to their effects and application when scaling up. For example, we will discuss what a principle such as "self-organizing teams" means when it is applied to a team of more than 100 developers or to the enterprise level.

The workshop is based on the necessity of large-scale Agile to give and get frequent feedback in order to deliver the highest business value to the customer at all times besides learning and getting better continuously.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

  1. Setting the stage by clarifying the goal of the (5 min)
  2. What (Part 1): At first we will use an interactive format to share data on presenters' and gather data on participants' experiences on the concept of scaling and how scaling is perceived from the different perspectives (10min).
  3. What (Part 2): In small groups we will discuss what (in the participants context) has supported, hindered, and what was difficult along the way when applying agile in the large. (15min).
  4. So what/Generate insights (Part 1): Making sense of the experiences in the participants' context, we’ll explore the agile principles in order to find out how they support and what extra challenges they provide for scaling. Participants will identify their own "sticky issues". (15min).
  5. So what/Generate insights (Part 2) We will dig deeper into each participant's topic and the new possibilities for understanding and supporting scaling (and the consequences of the lack thereof) by incorporating learning from the principles and as well existing experiences. (15 min).
  6. Now what/Decide what to do (Part 1): We will examine how these learnings can be applied in the participants' context so scaling can be supported. We will also explore how participants can apply this knowledge base to their impediments to change their "sticky issues".       (10min).
  7. Now what/Decide what to do (Part 2): We will look for practical ways to leverage the learning to overcome these obstacles and to convince stakeholders on the importance of this (10min).
  8. Debrief and Wrap-Up (10min)

Learning Outcome

  • Understand the importance of adhering to the agile principles when working in the large
  • Become clearance about the challenges when scaling
  • Understand the adverse consequences of using Agile as a tool
  • Know how to adjust and adapt the change toward organizational agility to your own needs
  • Understand how to discover constraints (and strengths) and using them to create an outcome based adoption, either to introduce or improve the use of agile methods

Target Audience

Project managers, program managers, coaches, consultants and everyone looking for ideas about scaling Agile

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal