location_city Bengaluru schedule Mar 8th 10:30 AM - 12:00 PM place Mysore Hall 3 people 21 Interested

Many agile teams suffer from the mismatch of agile and organizational leadership, with the latter being reflected by the organizational hierarchy. Based on self-organization and iterative processes, the agile teams run into trouble with the top-down steering of their environment. Consequently, agile proponents very often believe that a supportive agile organization should be structured without hierarchies, the so called “no managers” approach of “reinvented organizations.” Several companies in the agile field are experimenting with different organizational approaches that don’t use hierarchies. Yet, “no hierarchy” or “no managers” is not an option for many organizations.

In this session we suggest using sociocracy as a solution that leaves the hierarchies in place in an agile way - an option the organization is free to choose. Sociocracy shows how hierarchies can actually be agile and can strongly support (rather than opposing) agile philosophy. It enables managers to become agile leaders. As a participant you will learn how the principles of shared decision making and double-linking are key to enabling self-organization. These principles convert hierarchies from linear to circular so that they support an agile mindset.

Sociocracy is a way for groups and organizations to self-organize. Based on four principles (self-organizing teams, shared decision making based on consent, double-linking, and electing people by consent to functions and tasks), sociocracy provides a path for existing organizations to have empowerment and self-responsibility on all levels. Different than comparable methods, sociocracy allows companies to start where they are – with their existing organizational structures and the like. It seems to be a perfect fit for organizations that need to be truly agile (due to market pressure) beyond their IT departments and software teams.

 
 

Outline/Structure of the Workshop

  1. Setting the stage by clarifying the goal of the session (5 min)
  2. Leadership, Management, and Hierarchies (15min).
  3. Shared decision making - experiential exercise(15min).
  4. Double-linking - experiential exercise (15 min).
  5. Self-organization in hierarchies (15min).
  6. Responsibilities of agile roles in a sociocratic setting - experiential exercise (20min)
  7. Debrief and Wrap-Up (5min)

Learning Outcome

  • Understand how the "sandwich position" of middle managers can be resolved.
  • Learn how scrum masters (and/or other team members) can be empowered for organizational agile adoption.
  • Experience a sociocratic election.
  • Understand experientially the sociocratic principles of shared decision making and double linking and how they can help you be an agile manager.

Target Audience

The session is addressed to everyone in leadership positions: Top Management, Middle Management, Product Owners, Scrum Masters, (Project) Managers, Junior Executives, and Advisors (Coaches, Consultants, and Change Agents)

schedule Submitted 4 years ago

Public Feedback


    • 480 Mins
      Workshop
      Intermediate

      Today companies are expected to be flexible and both rapidly responsive and resilient to change, which basically asks them to be Agile. Yet, doing Agile (the mechanics) is different from being Agile (the mindset). The mindset lets you apply flexible Agile patterns not only for software development teams but for whole company. In this workshop, we will examine what being Agile really means and how it can be implemented by combining principles from the Agile Manifesto, Sociocracy, Beyond Budgeting, and Open Space. We’ll draw on everyone’s experiences to show the path to transforming our companies into agile enterprises - from Board to janitor, offering concrete tools and methods that participants can apply right away.

       

    • Sundaresan Jagadeesan
      keyboard_arrow_down

      Sundaresan Jagadeesan - Leadership Engagement - Philips Scaled Agile Transformation Journey

      Sundaresan Jagadeesan
      Sundaresan Jagadeesan
      Program Manager
      Philips
      schedule 4 years ago
      Sold Out!
      20 Mins
      Talk
      Advanced

      Philips - SW transformation program is involved in the deployment of (Scaled) Agile framework to enable TTM and Quality in Business from the year 2014. We started with Pilots and then followed with Mass deployments. We have:

      1. 44 Agile Release Trains launched since Aug 2014 and 220 + PI planning sessions completed.
      2. Currently, focusing on System Business with multiple ART’s launched in Systems Business, including 1st ART launch in Philips –China.
      3. 3700+ people engaged in (Scaled) Agile way of working globally and part of ART's and 1300+ are formally certified in Agile and SAFe

      We have learned that when engaging, deploying, an important and not-to-be-forgotten first step is to brief Executives and leadership about the approach, changes .This typically takes 4-8 hours, which sounds like a huge investment, but almost always is seen as paying off. Involving Leadership along has been a key element of our Success in our deployment

    • Jutta Eckstein
      keyboard_arrow_down

      Jutta Eckstein - Business Value over Architecture?

      20 Mins
      Talk
      Intermediate

      At the core of lean product delivery is -of course- the continuous delivery of a product. Yet, how does this impact the architecture, especially when welcoming changing requirements (even late in development)? Basically, the architecture should be enabled to incorporate these changes and therefore to emerge over time. This implies not to finalize the architecture upfront.

      For a small team being jointly responsible for the product delivery AND the architecture this is often already a challenge yet even more so for a large team. But, also for large-scale agile development the requirement for an emergent architecture holds true. However, it is difficult if not unrealistic to expect e.g. 300 team members to decide jointly on the architecture.

      Moreover, the role of and support for the architecture depends not only on the degree of the size of your development effort but as well on the degree of complexity of the system. 

      In this session I report on my experiences using different models for supporting an emergent architecture in different (mainly large-scale) environments that take the degree of complexity into account.

    • Kurt Bittner
      keyboard_arrow_down

      Kurt Bittner - Two Dimensions Of Agile At Scale: How To Make The Most Of Your Agile Transformation

      Kurt Bittner
      Kurt Bittner
      VPEnterprise Solutions
      Scrum.org
      schedule 4 years ago
      Sold Out!
      45 Mins
      Talk
      Advanced

      Many organizations have achieved sufficient success at the single team level with Agile approaches like Scrum that they want to bring Agile to their entire enterprise. They want to reap the benefits of Agile across their whole organization, but they struggle with where to start and how to sustain the change. Scaling Agility has two dimensions: scaling horizontally, across large numbers of teams, and scaling vertically, integrating the work of multiple teams into a single product. Focusing on both dimensions enables organizations to achieve sustainable change by solving 3 main challenges: achieving consistency and the right Agile culture across teams without dictating behaviors, fostering the right interactions between Agile and non-Agile teams when there are dependencies between them, and adapting Agile approaches to deliver products that require a team-of-teams approach. 

    • Erwin van der Koogh
      keyboard_arrow_down

      Erwin van der Koogh - The 'Only' Two Things You Need to do to Scale Agile

      45 Mins
      Talk
      Intermediate

      The magic behind the Agile manifesto is in the question they asked. The 17 people assembling in Snowbird spend their time figuring out how they were similar, not what way of working was best. And in the course of those two days, they discovered the deeper truths in what worked.

      So what happens when we look what the different Agile Scaling frameworks have in common? A move away from projects towards product development and teams as the fundamental building blocks?

      In this talk, we will be exploring how these two shifts impact the way we scale Agile. Looking back on all the Agile Transformations I have done all of them have succeeded (or failed) when we have (not) focussed on these two things.

    • Fabiola Eyholzer
      Fabiola Eyholzer
      CEO
      Just Leading Solutions
      schedule 4 years ago
      Sold Out!
      45 Mins
      Talk
      Advanced

      “#1 trend: HR embraces agile" | HR Trend Institute

      "HR drives the agile organization" | HRO Today

      ---

      Agile HR is a hot topic. But what does it really mean: Is it about implementing Scrum in your HR teams? Is it about eliminating annual employee appraisals? Or is it more than that?

      Bringing your HR into the 21st Century with Lean | Agile values, principles, and practices starts by understanding the various aspects of Agile HR.

    • AnkitTandon
      keyboard_arrow_down

      AnkitTandon - DIY Scaling Agile Framework

      AnkitTandon
      AnkitTandon
      Scrum Master
      Citibank
      schedule 3 years ago
      Sold Out!
      45 Mins
      Workshop
      Intermediate

      Is the scaling framework your organization is on helping you to be Agile or pretend to be Agile? How about drafting one that stays true to Agile principles and helps with what your organization needs most while scaling

      While there are a many frameworks available to scale Agile it is important to see if these prescriptions address the real problems that an organization have while scaling up.  Does one size fits all? Is it worth adopting a framework and then retrofitting your organization into it or it makes more sense to understand the dynamics of your organization, the existing challenges and business objectives and carve out a scaling approach, keeping Agile principles intact, that suits the organizations needs best.

      This interactive workshop is about discovering the best approach to create your own scaling framework, one that is custom made to respond to your organization’s needs. 

    • Raghavendra (Raghav) Mithare
      keyboard_arrow_down

      Raghavendra (Raghav) Mithare - "Being" Agile or Doing Agile ? Ontological Perspective

      90 Mins
      Workshop
      Advanced

      The key element for successful agile adoption is “being” agile and not just “doing” agile. If you are using Scrum then it is not just about standups, sprints, demo and retrospectives.  Then what is this “being” agile?

      Ontology is a branch of philosophy, dealing with study of the nature of being. Currently ontology based concepts are used in professional coaching and leadership development work.  (Harvard Professor Dr. Michael C. Jensen (his initiative EJI) , Prof Dave Logan of UCS author of Three Laws of Performance, have done significant research and contribution to this field).

      The intention of the workshop is to give the participants a glimpse of “being” as an experience.  It is important to understand and know the difference between “doing” and “being”, since in any agile implementation “being agile” is more important than doing agile. If this distinction is not made very clear then all the agile practices will face the risk of ending up like rituals without significant outcomes.

      During the sessions one key exercise is to identify the subtle differences in actions taken (doing), results obtained (having) and the experience (being). The importance that the language plays in differentiating the experience is also discussed.  After the session you will start discovering (by observation) the world of being and the world of doing and their overlap.

       

    • Sakti Bagchi
      keyboard_arrow_down

      Sakti Bagchi - Servant Leadership: Learn from your Mom

      Sakti Bagchi
      Sakti Bagchi
      Sr. Development Manager
      Allscripts
      schedule 3 years ago
      Sold Out!
      20 Mins
      Talk
      Beginner
      Servant leadership is the most used (misused) term in the Agile world. If you check any people manager's profile or ask any people manager in the agile world, they would always describe themselves as a servant leader. But when you observe them you many times find the same age-old autocratic leader who is struggling to retain his/her relevance under servant leadership mask. This talk is to describe some life examples and drawing the similarity between the leadership that mother provides at our home.
       
      Mindfulness, compassion, coaching and becoming the best friend for life are some attributes that will be explained.
       
      In many agile forums it is said that role of people manager is diminishing in agile world. This talk will share a counterview to that belief and explain how a people leader's role has grown further and how we need expert life coaches as people leaders for our future agile world. 
    • AnkitTandon
      keyboard_arrow_down

      AnkitTandon - Agile contracting- Starting with the right mindset

      AnkitTandon
      AnkitTandon
      Scrum Master
      Citibank
      schedule 4 years ago
      Sold Out!
      45 Mins
      Workshop
      Executive

      One of the biggest challenges in achieving agility is the way contracts are written. More often than not, these contracts prove to be a deterrent to realize the ultimate benefits of Agile. The way contracts have done traditionally usually go well with the traditional way of building software where scope / time / cost are fixed. However when the focus is on delivering business value early to the customer for his competitive advantage, to reduce risk, cost by not building what is not needed, gain and retain users, traditional contracting does not help the cause. Agile is something that the entire organization has to embrace. It has to start with the sales team. It has to reflect in the contract. It has to start with the right mindset. It has to start with an Agile contract.

      Third value of Agile manifesto is Customer collaboration over contract negotiation. Not only should this collaboration be expressed during project development, it should be expressed in the contract language as well.

      In this talk + workshop session, I will be sharing various types of contracts that can be leveraged / customized for an Agile project, some good practices surrounding them and will be involving the participants into a small workshop of writing Statement Of Work (SOW) for Agile contracts related to a few real world scenarios.

    • AnkitTandon
      keyboard_arrow_down

      AnkitTandon - Performance management in Agile: Time to plug the hole

      AnkitTandon
      AnkitTandon
      Scrum Master
      Citibank
      schedule 4 years ago
      Sold Out!
      45 Mins
      Talk
      Intermediate

      Principles behind traditional performance management system are utterly opposite to that of Agile. While traditional one focuses on Individual ratings, surprises, one sided evaluation, Agile is built on the foundation of trust, transparency, respect and courage. Whole is greater than sum of its parts and individual ratings and outdated performance management processes may prove to defeat the bigger purpose. While aspiring for Agility both at team and organization level, it is important to ensure all the wheels are moving in tandem in the same direction. Technology has changed the way our people engage, work and communicate and the need for frequent and less formal points of progress reviews is in demand.

      Agile performance management is an attempt to plug the hole by providing an approach that compliments Agile values and proves to be a catalyst than detractor for a high performing team and organization.

    • subhashree mishra
      keyboard_arrow_down

      subhashree mishra - How we managed our dependencies in SAFe

      subhashree mishra
      subhashree mishra
      Scrum Master
      Philips
      schedule 4 years ago
      Sold Out!
      20 Mins
      Case Study
      Intermediate

      This is a case study on How we managed our dependencies in SAFe.