Sunday, February 19th, 2012 by David Chilcott
Effective coaching deepens awareness and learning, supports choice, and and is grounded in action. Sometimes our habitual ways of thinking get in the way of seeing options that might support more successful outcomes. As a coach I want tools and skills that help me reveal a system to itself, whether that system is an individual, a team or an organization. One such tool is Agile Coaching with Geography.
This session, designed for experienced coaches and facilitators, will introduce using “geography” and teach specific exercises that you can use in your coaching work with individuals and teams.
Humans are gifted with a variety of ways of learning and knowing. Our left brain thinking emphasizes rational and verbal knowing. Our right brains connect us with more sensory-based, intuitive and spatial knowing. Agile Coaching with Geography uses both to work at the intersection between our inner and outer landscapes.
Agile Coaching with Geography supports individuals and teams to more deeply access non-verbal and intuitive ways of knowing and perceiving aw well as helping to make these aspects of a system visible to the system itself.
Process/Mechanics
Introduction to Geography & MetaSkills
— Introduction to working with Geography — i.e. Why is it called geography? And why do I care? In this context, “Geography” makes use of our basic human capability to orient in space as an opportunity to learn and explore what we think and feel as well as a means to reflect this information about the system to itself.
— Introduction to MetaSkills — A MetaSkill is the attitude, stance, or “come from” place that the coach stands in when coaching. (from CRR Global ORSC)
Working with Geography Exercises
We’ll explore a sequence of exercises that form an arc that supports incremental learning. We’ll work through as many exercises as we have time for. And to be clear, it is unlikely that we’ll complete all of the exercises in the 90 min available. My intention is to introduce the topic and give you a taste of a variety of different exercises so that you’ll be able to determine how and where you might use these techniques in your day-to-day coaching practices.
For each of the exercises we will:
— Describe the MetaSkills involved
— Define desired Learning Outcomes
— Describe the required Materials
— Setup the exercise
— Experience the exercise
— Conduct a debriefing for learning
Continuum Exercise - Explores self-organization and how individuals and teams make qualitative vs quantitative distinctions
Tribes Exercise - Explores the boundaries of belonging & not belonging and normalizes diversity
Center of Gravity Exercise (Informal Constellations) - Explores self-organization, normalizes diversity and reflects the system to itself
Coaching Wheels Exercise - A tool for individual and team learning and topic exploration
Living Systems Diagrams (Constellations Lite) - Models relationships in teams to support deeper communcation and understanding
Q & A
Materials & Hand-outs
Learning outcomes
- This fast-paced workshop will:
- — Introduce you to using geography in your coaching work
- — Give you a basic understanding of the range and depth of various geography exercises so that you can adapt them to suit your desired outcomes with your clients & teams
- — Teach you several specific geography-based exercises (how many will be based on available time)
Tags: Agile, agile coaching, agile team dynamics, collaboration tools, complex adaptive systems theory, facilitation, tacit knowledge, team wisdom
Posted in Uncategorized | No Comments »
Sunday, February 19th, 2012 by David Chilcott
NVC is both a set of skills and a mindset. As a coach, I believe it’s important to be able to distinguish our own judgments, biases and feelings from those of our clients. NVC helps make these distinctions clearer. Having and using a needs-based perspective also helps the coach work more effectively with individuals & teams that are experiencing conflict.
This session will show how NVC can be an important addition to your Agile coaching tool kit.
Last year this session was very well received.
NVC delineates four components of communication:
1) Observations free of evaluations;
2) Feelings straight from the heart;
3) Needs, values and longings;
4) Requests expressed clearly in positive action language.
We briefly introduce each area and then use experiential exercises where participants work in small groups to deepen the learning, followed by debriefing in the whole group to capture and share insights. We’ll also explore examples of how you might use these concepts in YOUR Agile coaching environment,
Process/Mechanics
It’s a fast paced workshop format mixing subject matter presentations, role play and activity-based experiential exercises. We will use real examples from our personal and professional lives to experience the depth and breadth of NVC and how we might use NVC in our day-to-day coaching practices.
—————PROCESS OVERVIEW—————
START-UP /HOUSEKEEPING
— Working Agreements for the Session
— Introductions/Housekeeping/Setup
OBSERVATIONS
— Observations exercise
— Problems identified
— Needs identified
FEELINGS
— Introduce empathy
— Small group role playing exercise
— Report back to whole group
NEEDS
— Introduce Needs-centric perspective as foundation
— Small group role playing exercise
— Report back to whole group
REQUESTS
— Introduce “Well-Formed” Requests - Understanding difference between requests and demands
— Small group role playing exercise
— Report back to whole group
Q & A
Learning Outcomes
— A language and consciousness of compassion that can improve your relationships
— Skills to support dialogue in the face of judgment, criticism, and anger
— Practice in honest expression and empathic listening
— Effective ways to bring more joy, ease, and connection into your life and work
— A nonviolent approach to team and organizational change
Tags: Agile, agile coaching, non-violent communication, NVC, teams, teamwork
Posted in Agile, Uncategorized, by David | No Comments »
Wednesday, February 10th, 2010 by Scott Hurlbert
Posted in Agile, by Scott | 1 Comment »
Monday, January 11th, 2010 by Scott Hurlbert
Posted in Uncategorized | No Comments »
Wednesday, December 30th, 2009 by Scott Hurlbert
Posted in Outformations, Productivity, Values, by David, by Don, by Scott | No Comments »
Monday, December 28th, 2009 by Scott Hurlbert
Posted in General, Uncategorized, by David, by Steve | No Comments »
Wednesday, December 23rd, 2009 by Scott Hurlbert
Posted in General, Uncategorized | No Comments »
Wednesday, December 16th, 2009 by Scott Hurlbert
Posted in Uncategorized | 2 Comments »
Monday, November 30th, 2009 by Scott Hurlbert
Tags: Agile, Learning, Skills
Posted in Agile, Productivity, Uncategorized, by Scott | No Comments »
Monday, November 23rd, 2009 by Don Robins
I my last post, I described the benefits of applying the Repository pattern to encapsulate all logic pertaining to the direct manipulation of your data entities. The repository is responsible for shaping the data entities that will get passed back up through the ASL to your services or views, as well as pushing the data through the data services layer down to its final persistence location. You should note that this could be any number of data source types, from a relational database, to xml files, to an external web service. The repository is the manager of all such data centric interactions.
It is most important to note that when fetching data and passing it up into the application layers, it should be packaged appropriately based on the need of the calling layer. While you could simply pass full data entities of your Model into the application from repository calls, care should be taken to avoid unnecessarily exposing full Model entity details throughout your application. It is important to minimize the number of locations that will break if the data model changes over time, and rest assured, it will change over time. For this reason, we depend upon the ASL and Repository layer interfaces when using and accessing the Data Model as these methods can be used to create packages of data that represent just the specific information necessary to enact a Use Case or support a View. This collection of information is often referred to as the ViewModel; you can think of this as a Model specifically abstracted for the View, or a specialization of the domain Model.
Read the rest of this entry »
Tags: .NET, Application Development, Architecture, ASL, DTO, Enterpise, Layers, Repository
Posted in Uncategorized | No Comments »