“Help Me Do It Myself!” Growing a self-organization by using the Montessori Method

“Help Me Do It Myself!” Montessori is an innovative, child-centered approach to education, developed a century ago by Dr. Maria Montessori who was struck by how avidly the children absorbed knowledge from their surroundings. The goal of the Montessori method is to foster a child’s natural inclination to learn, where Montessori teachers guide rather than instruct, linking each student with activities that meet his interests, needs, and developmental level. But is this method only suitable for children?

In this talk, I will demonstrate how to apply the Montessori education method in growing self-organized teams. We’ll discuss what Leaders may find useful and how to adapt this methodology in the day to day work of your organization.

 
9 favorite thumb_down thumb_up 12 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • 5 min - Introduction
  • 25 min - What is the Montessori method? Pedagogical and Psychological principles
  • 15 min - Montessori method and Agile

Learning Outcome

Why Should You Attend This?

  • To know why each person is valued as a unique individual
  • To learn how Montessori students become confident, enthusiastic, self-directed learners
  • To understand how to apply the Montessori method in the real world

Target Audience

Scrum Masters, Agile coaches, Managers, Leaders

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi Alex,

    A very different topic. Thanks for the same. Your points are great. But How are you going to address the Adult part since we work with Adults in Software where the learning pattern is very different. Do you have any solution / learning to share on this part? If YES that will add lot of value for many

    Thanks,

    • Alexey Pikulev
      By Alexey Pikulev  ~  2 years ago
      reply Reply

      Hi Jerry,

      Thank you for your thoughts.

      The main idea of my talk is how to apply this methods in real adult life. I have some examples from my teams which I worked and adopted this methods. I'd like to share this examples with participants. 

      Best regards

      Alexey

      • Naresh Jain
        By Naresh Jain  ~  2 years ago
        reply Reply

        Hi Alexey, this is a very interesting topic and certainly the principles makes a lot of sense. However most people have already heard these principles. The talk would become very interesting if you can share first hand experience applying those principles. For the committee to really appreciate the depth of the proposal, we would like to see at least 3 examples before we can select the talk. Can you please share at least 3 specific examples of how you've used these principles.

        • Alexey Pikulev
          By Alexey Pikulev  ~  2 years ago
          reply Reply

          Hi Naresh,

          I'm going to prepare a practical (not theoretical) talk. I'd like to share some case from one company where I was an agile coach. We tried to adapt this methodology for different perspectives. Firstly, we used Montessory method for forming and performing teams. I'd like to talk about instruments for growing team diversity and team work. Secondly, we applied pedagogical and psychological principles for Scrum master work and obligations.  The next issue was how to apply method for changing environment. I'd like to talk about our information radiators and different stuffs. And finaly, I'd talk about the results from applying of Montesorri approaches: profits, benefits and problems.

          best regards

          Alexey 

          • Naresh Jain
            By Naresh Jain  ~  2 years ago
            reply Reply

            Hi Alexey, thanks for the clarification. I went thru the slides, I went thru your LinkedIn article. I understand the principles in theory. But I fail to see any concrete example of how you've used it to help teams you've coached.  

            For example, you've mention using information radiators for changing environment. Every sudo-agile team I've known, also use information radiators. I fail to see how different is the Montessori method. Can you please explain in more details so we can appreciate what was done. 

            • Alexey Pikulev
              By Alexey Pikulev  ~  2 years ago
              reply Reply

              Hi Naresh,

              You absolutely right about my previous presentation and article. It looks more theoretical approach. Let me share with you a practical details which we got from Montessori school. We brought a main value of mointessory - “Help Me Do It Myself!” in our teams. It became their motto. Furthermore we tried to build the majority of collaboration between teams and other using this principle. For example, when we faced with a conflict between team members before the Scrum Master always tried to resolve it. In "Montessori team" the ScrumMaster worked us a observer helping them to find a solution by themselves.

              From what we have observed from the actions of the team members, we followed them in what they need to do. If they want to choose new estimation approach, give them the opportunity. Following the person also means being non-directive, do not tell them what to do all the time. Give your team the freedom to choose what they want or need to do and to act on they own. 

              Another example about project obstacles. Within the "Montessori team" the Scrum master didn't resolve any problems or impediments, but helped them to found out. It helped us to improve a team trust and engage people to resolve challenges.

              We've changed a principle for team foundation and learning. We embraced a team diversity and peer learning. I know that a lot of agile team use a different information radiators. In "Montessori teams" you could find radiators papered with brightly colored images and pictures. For example, a Team Motivation Wall with color pictures and strong mottos. Furthermore, we borrowed and adapted some funny instruments from Kindergarten. We used a kinetic sand, a different sets of dice and animal figures.

              Best regards

              Alexey 

  • pradeep panda
    By pradeep panda  ~  2 years ago
    reply Reply

    Hi Alexy,

       I really liked the concept. And out of curosity even i went through the linkedin article you have provided. And I like the way you have compared the children with the organization team.

       But my query is on the HOW part. None of these explain on HOW to achieve in corporate organization. Taking own time to learn, giving opportunity for self-correction, working without any estimation (even few more examples) all these are cost to compnay. Unlike the children, every team and product is bound by three dimensions. Time, Scope and Quality. And unless and until something concrete is defined for all these situations, in my opinion it will cost a lot to organization.

    Hence in my opinon , crux of your session should be providing a solution i.e. clarifying the HOW part in the context of an organization and of course highlighting the ROI of such an investment.

    Can you please highlight and clarifymore on HOW part ?

    regards

    Pradeep 

     

     

    • Alexey Pikulev
      By Alexey Pikulev  ~  2 years ago
      reply Reply

      Hi Pradeep,

      Thank for your feedback.

      Sure, I can highlight a HOW part. I agree, it will be useful for participants.

      Best regards

      Alexey

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

    Hi Alexey,

         Very interesting submission.  I went through the slides and when I read it, I get more 'definition' than 'why / how' I would apply this.  How do you address that as part of the presentation? 

    Is this more of a thought exercise for attendees or is there some things you feel like attendees, like a Manager, could immediately apply?

    Best,

    Joel

    • Alexey Pikulev
      By Alexey Pikulev  ~  2 years ago
      reply Reply

      Hi Joel,

      Thank you for your letter.

      This slides from my webinar. I'm planing to add some thoughts and instruments which managers or leaders can immediately apply.  Hope to prepare more practical talk.

      Best regards

      Alexey

       

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

    Hi Alexey,

    Nice topic!  I had kids who went to Montessori schools and neve quite made this connection myself.  

    • Alexey Pikulev
      By Alexey Pikulev  ~  2 years ago
      reply Reply

      Hi Steve,

      Thank you! Yes, it's very interesting topic :)

      Best regards

      Alexey


  • Liked Alexey Pikulev
    keyboard_arrow_down

    Alexey Pikulev - Growing trust workshop: “In Team We Trust”

    Alexey Pikulev
    Alexey Pikulev
    Unusual Concepts
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    This one-day workshop will help your team in improving their trust relationships and gaining a deep understanding of trustworthiness.

    Learn to use the Team Trust Canvas methodology to strengthen your team performance. During the workshop, participants will learn which factors are essential for trust and how to use this new capacity to create an environment that brings the best of people.  The content is very practical. Most time of the day participants will do hands-on step-by-step exercises with the differents tools and games.  You’ll be able to use those right away when you go back to work.

     

  • Liked Sophie Freiermuth
    keyboard_arrow_down

    Sophie Freiermuth - Integrating UX into the Agile Development Cycle - A case study over 3 projects

    45 mins
    Case Study
    Beginner

    User Experience design is a product design discipline which sits throughout a product's lifecycle, from inception to development to maintenance and all the way to retirement. Waterfall enabled the discipline to have ample time and produce extensive design, in a "big design upfront" approach which rarely involved technical capabilities, and resulted in difficulties in build. The adoption of agile by product development team has offered UX a unique opportunity to work in a much more joined-up manner, and expend the design into the development, enabling the entire team to react to change.

    As a UX designer, I have over the last 7 years developped a solid appreciation of working embedded in an agile development team, and would like to share my experiences through 3 specific projects, sharing my learnings to help development team on-board the UX practitioner, their tools, practices and skills.

    This session will be a case study over 3 projects, highlighting the learnings and steps of the integration of UX into the development cycle. I'm taking Alistair Cockburn's sequence of SHU-HA-RI to detail the progress of my practice and will pay great attention to sharing sufficient context that my experiences and outcomes can be translated to your own projects and team setups.

  • Liked ShriKant Vashishtha
    keyboard_arrow_down

    ShriKant Vashishtha - Distributed Agile Patterns

    60 mins
    Talk
    Intermediate

    Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.

    In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.

    Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:

    The session is to share the these patterns and more (when to go for distributed Agile and when not etc)

  • 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.

  • Sneha Kadam
    Sneha Kadam
    Business Analyst
    ThoughtWorks
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

  • Liked Sophie Freiermuth
    keyboard_arrow_down

    Sophie Freiermuth - Prioritizing user stories: using value to users as a key criteria

    60 mins
    Workshop
    Beginner

    Product development in agile is always at risk of favouring velocity and developer's skills.

    Favouring velocity means that when it's time to select stories, the team will elect to do many short stories to keep velocity on the rise, or stable.

    Favouring skills mean that easy implementation may be selected, or sometimes tricky solutions which will give the developper the satisfaction of solving a difficult problem.

    The outcome of the story's execution and value to users is an important criteria, and I'd like to introduce you in this session to a technique that helps prioritize against two sets of criteria: technical difficulty and value to users.

    Using Personas, a tool from product design which I will explain, and a simple grid, this technique makes prioritization incredibly easy - which then enables the team to focus on getting stories done, rather than figuring out which stories.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - Lean and Kanban Implementation from Trenches

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    I was part of a Large Scale Agile transformation in my organization and I was one of the Agile coaches there. As part of transformation we have created LeanOps teams to manage the technical debt, production incidents with a focused concentration. This article covers the following:

     

    - Why the trasnformation required?

    - What are the structural changes implemented?

    - LeanOps inception

    - Lean Ops working Model

    - Challenges with the LeanOps

    - How we addressed those challenges?

    - Goal oriented approach

    - Q & A

  • Liked Alexey Pikulev
    keyboard_arrow_down

    Alexey Pikulev / Illya Pavlichenko PST, PSPO I, CSP, ACP - A Scrum Master’s Practical Workshop

    480 mins
    Workshop
    Intermediate

    The training is based on the material of our eponymous book  «A Scrum Master’s Practical Toolbox».

    To be a Scrum Master is not an easy job. You are supposed to have skills in different areas: to be a servant leader, a neutral facilitator and coach, teacher and mentor with a deep understanding of the empirical nature of Scrum.

     

    What training is about. The training consists of a large number of practical games and exercises that you can use in your companies and teams. We give a minimum of theory. Our goal is to arm you to the teeth with practical tools. We want you to be equipped and well prepared for attacking organizational dysfunctions.

     

    Who will be interested in our training. We assume that you already have practical experience in Scrum as well as a basic knowledge of Scrum Guide. Perhaps you have visited certification courses Certified Scrum Master (CSM) or Professional Scrum Master (PSM). Now it's time to pump your skills and reach the next level.

     

    The structure of the training. Training has a modular structure and this means that you will be free to choose whatever is interested for you throughout the day:

     

    • Facilitating and conducting Retrospectives using Lego Serious Play (LSP)
    • Cynefin with the Team Drawer
    • Brainswarming because Brainstorming does not work
    • Storytelling with Rory Cubes
    • Personal Maps for nurturing trust in teams
    • Blind Communications
    • Moving motivators and motivation web
    • Scrum Metrics as a thermometer of the process health
    • Broken squares for the team spirit
    • Responsibility as an individual skill
    • Hanabi cards for the focused dialogue
    • A3 method for identifying problems and problem-solving
    • Marshmallow Challenge and disciplined learning for building the "right" product

     

  • Liked Michael Harris
    keyboard_arrow_down

    Michael Harris - Agile Competency Development For Enterprises

    45 mins
    Talk
    Intermediate

    For agile to work at scale in enterprises, there needs to be clarity around the hierarchy (or lack of hierarchy) of roles across teams and products to ensure sound governance and, perhaps more importantly, to offer career (and salary!) progression.  This presentation will propose a competency-based approach for the development of skills and competencies of the workforce, and thus creating a sustainable transformation in an enterprise. We will include experiences of implementing those components of the proposed model that have already been tried and tested.  Feedback will be sought from the participants.

  • Shiva Krishnan
    Shiva Krishnan
    Agile Coach
    AgileFaqs
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    My journey as an agile coach has been a great learning experience.

    In this session i intend to share some key learnings that contribute to effective coaching.

    I have aggregated my presentation under the following topics:

    • Coaching with Compassion vs coaching for compliance - why it is important to understand the team's needs instead of running the coach's transformation agenda. How do we involve teams in the transformation?
    • The coach’s mindset defines his/ her coaching - Many times coaches are not able to identify team problems due to their own biases. How can a coach be aware of such biases and overcome them?
    • Making your coaching visible - A common failure in transformations is that coaches are unable to make their progress visible. We will look at some interesting techniques to make  coaching progress visible
    • Involving stakeholders -How do we involve stakeholders other that the teams? why is it important?
    • Coach for a coach - Every coach needs a mentor . How do we effectively utilize mentors? what role do they play in a coach's growth?
    • Celebrating success - We often fail to talk about our successes and acknowledge teams. How did we do this in our organization?

    In each topic i will be sharing my experience, learnings and techniques that i used to overcome challenges.