schedule 04:30 PM - 04:30 PM place Esquire

There is a level of "assumptions" that each one of us work with, while we deal with any system. Here in this case the system could be a team member, the manager, the management, or the entire organization. While we work with assumptions, the conversations or the discussions or the work we do, can seem like getting nowhere because of the conflicts, and a sense of frustration piles on .This is a common situation and a very common feeling amongst Coaches/Scrum masters/Project Managers or anyone dealing with project management scenarios. That is where "contracting" helps us get our way through!

Contracting is a concept of "Transactional Analysis" school of psychology. Eric Berne defines it as "an explicit bilateral commitment to a well-defined course of action". Sometimes contracts will be multi-handed - all parties to the contract will have their own expectations. In the unusual event that these are all congruent, then fine. However, if not, then discussing everyone's expectations will lead to greater understanding and therefore to a clear contract. The risk in not doing this is that problems in completing the contract will emerge at some stage.

3 Categories of contracts are administrative, professional and psychological.

Administrative contracts deals with the operational agreements- like fees, who has to do what, time, frequency, attendees etc.

Professional contracts deals with the expectations from each role and clarifies the essential setup required to achieve the same

Psychological contracts talks about how we work as people and help to understand how we express our comforts/ discomforts       

Amongst the three contracts psychological contracts are very essential and often ignored in projects. This type of contract will help us co-create any assignment and it’s a powerful tool for Agile coaches while they work with their teams, managers, organization etc.

Further to agree with any contract, both the parties should operate from a space where there is mutual trust and concern (I am Ok , You are Ok).

This report will discuss in detail about these contracts with examples from Agile projects, in an activity based sessions. We will also discuss the life positions based on 'I am OK, You are OK' theory.

Note: Please note that this presentation is not about the business/financial contracts that most of us are aware of. However, the framework of contracts could be applied in any situation including the business/financial contracts.

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

Outline/structure of the Session

  • Contracts – Introduction
  • Need for Contracts
  • Types of Contracts
  • Contracts in Agile Scenarios
  • Practical Examples

The presentation will be based on our coaching experiences with Agile teams and we would also do some activities with the participants, which would give a hands-on experience on the use of  contracts for Agile Team scenarios.

Learning Outcome

  • Helps people understand the theory of contracts and various life positions
  • Gives a structured framework to contract with the concerned stakeholders

Target Audience

Agile Coaches and Teams

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    Hi Karthik / Deepak

    Do you have additional info available now how do you intend to present?

    Thanks

    Sachin

    • AgileSattva Consulting LLP
      By AgileSattva Consulting LLP  ~  1 year ago
      reply Reply

      Hi Sachin,

       We are still working on the exercises and mode. on an outline, here is what we think could be a good structure:

      1. Introducing some real life examples, a conversation during a problem solving situation -

            for example:

      • Manager with Team about estimates and not considering the vagueness in the requirement - This discussion could go on and on without a OK-OK outcome.
      • As Coaches, sometimes, we listen to somebody sharing the problem, and we jump into solving their problem, and they say "Yes, but you know, it doesnt work for us", and Coach could say "Did you try this", and they say "yes, but u know... " .. These type of conversations can go on and on. 

      2. Then Introduce about the principles of Transactional Analysis to Audience.

      3. Then we talk about Contracting itself, and the types of Contracts.

      4. Now with the picked examples, have a role play dialog to show how to use contracts to avoid conflicts, get to know expectations before responding. 

      5. We also want to introduce "I am OK, You are OK", Life position that is healthier position for anybody to operate on. 

      6. if we can get some volunteers or make sub groups, ask them to find a difficult situation and use contracting questions to find a Workable outcome .

      The examples and the exercies are still underdevelopment for this workshop. Hence I have given you a rough outline of what it may look like.

      Me and Karthik would be happy to explain it over the call, if that would help!

      Cheers!

      Deepak and Karthik!

       

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

        Hi Deepak,

          When would you and Karthik be able to chat about the submission?  Could we skype sometime late this week / early next week?

         

        Best,

        Tosi

        • AgileSattva Consulting LLP
          By AgileSattva Consulting LLP  ~  1 year ago
          reply Reply

          Hi Tosi,

           Thanks for asking, It would be appropriate to discuss it over call. Could we have the call early next week? Will send u email about the details of time. Would that work?

          Cheers!

          Deepak

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

            That would be great Deepak, thanks much

    • steve ropa
      By steve ropa  ~  3 years ago
      reply Reply

      Hi Karthik,  

      I love the topic.  Also, congratulations on a well written proposal.  I wonder though, is this really a beginner level topic? My gut instinct was intermediate or advanced.  

       

      Steve

      • Karthik Kamal Balasubramaniam
        By Karthik Kamal Balasubramaniam  ~  3 years ago
        reply Reply

        Thanks Steve :)

        Honestly I am not too sure about the classification. However, in my mind the basic concept of contracts and it's applications would still be at a beginner level. Any complex idea with application of one or more theories together would qualify for an intermediate or advance level presentation.

         

        Regards

        KK

         

    • Karthik Kamal Balasubramaniam
      By Karthik Kamal Balasubramaniam  ~  3 years ago
      reply Reply

      Thanks Joel :)

      Yes we need 45 minutes to complete the session. I wil update the same.

      Regards

      KK

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

      Hi Karthik,

         I really like this submission. Is 20 minutes enough?  This is marked as a workshop - I see you mention activities - is 20 minutes enough time or should this not be a workshop / should be longer in time?

       

      Best,

      Joel


    • Liked Prathitha Gangadharan
      keyboard_arrow_down

      Prathitha Gangadharan - Cycles of Development Applied to Teams

      Prathitha Gangadharan
      Prathitha Gangadharan
      DIRECTOR QUALITY
      ARICENT
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Beginner

      In her theory of cycles of development, Pam Levin talks about 7 stages a human being goes through from birth to becoming an adult. Each of these stages have unique requrements for any individual. The way the environment responds to the individual in each of these stages will determine how the individual will make sense of themselves with respect to their environment.

      Interestingly an individual goes through these stages when they enter a new situation. This could be as simple as walking into a roomful of new people or when they join a new team, or an organisation. Each one has their own own pace. While this is very logical for an individual how is this related to Agile?

      I have seen that teams also go through stages in their development. This is not just the forming, norming, storming and performing stages which is the internal process of a team. This is about the team being identified as an entity and being supported in their journey of becoming a high performing team. In understanding the cycles of development, we get some clues of what needs a team may have at different points in their journey to becoming self-organised.

      I would like to discuss Dr.Pam Levin's model in the context of a team and propose do's and don'ts that can support the journey of a team

      The seven stages: