For people who support Agile teams or organizations and want a forum to advance their skills, the Coaching Stage is an Agile2010 track that provides a focus on team, organizational, and individual coaching experiences, techniques, and tools. Unlike other Agile conference stages, this stage is specific for the people who help others learn and practice Agility.
The Agile Manifesto demonstrates the necessity of coaching in its first sentence:
”We are uncovering better ways of developing software by doing it and *helping others do it*…”
Coaches help other people implement the right change for their context through listening, feedback, facilitation, guidance, and skill transfer. Coaching requires a diverse set of skills and tools to enable teams with different organizational, cultural, and technical challenges. For a receptive organization, high-quality coaching often translates to successful Agile adoption. Unfortunately, these skills and tools, especially in the Agile context, are still not documented enough and the forums for learning them are few. The two books dedicated to Agile coaching only came out in the last 12 months.
Have you ever brought in a coach to work at the team level, but the problems were at the management level? Or, have you been brought in to coach managers, but the team isn’t delivering on its promises--and they don’t know why? You may have discovered that you work at multiple levels: one-on-one with the team members, facilitating team work, one-on-one with a manager, facilitating a manager’s work, helping the team or the manager work up and down the organization. Experienced coaches George Dinwiddie and Johanna Rothman will help you explore the multiple dimensions and levels of coaching.
|Presenter(s):||George Dinwiddie , Johanna Rothman|
|Day and Time:||Monday, 09 August 2010, 13:30 - 17:00|
What does an agile coach actually do? How does context affect what works and what doesn't? In this session we reflect both on the big picture of a number of agile coaching assignments and on some of the detailed interventions including activities that relate to the team and those impacted such as managers and business stakeholders. In the true spirit of retrospectives both success and failure are considered with the intention of looking for opportunities to improve. Attendees will be asked to consider how they might deal with particular scenarios and learn lessons from my mistakes.
|Day and Time:||Tuesday, 10 August 2010, 11:00 - 12:00|
An agile coach is typically an experienced expert. He has a solution for everything. In many cases, good advices without client’s ownership will not lead to real change. Sometimes it may be wiser to abstain from giving direct advice and ask questions instead. In this workshop the participants will learn why use questions when coaching and how to make them effective. We will practice making great questions that increase coachee's awareness and help him find solutions himself. We will also present a clear model of how to proceed from a problem to improvement using questions.
|Presenter(s):||Arto Eskelinen , Sami Honkonen|
|Day and Time:||Tuesday, 10 August 2010, 13:30 - 15:00|
BDD is a Lean toolset that encompasses the whole software lifecycle. In BDD we define goals at varying levels of granularity, talk through the definition with stakeholders, explore contexts to produce different outcomes, and break down large goals into smaller sub-goals for quick learning. With a few additional tools from coaching, NLP and Real Options, these patterns can be applied to real life - and it's also a fun way to practice the BDD mindset. This talk introduces the non-technical principles of full-stack BDD together with a few simple examples, so is suitable for beginners.
|Day and Time:||Tuesday, 10 August 2010, 15:30 - 17:00|
The word "respect" tops the list of both the Scrum Values and the XP Values. In both, the agile definition of respect comes through loud and clear: to hear ideas from everyone on the team because diversity of ideas yields astonishing results. Yet, every team I've coached seems divided into two camps - the dominant ones and the quiet ones. Just talking and brainstorming doesn't level the playing field. But "silent work" does. Come to this session to practice techniques you can take home so that your teams become free to create more and better results (faster, too) through silent work.
|Day and Time:||Wednesday, 11 August 2010, 11:00 - 12:00|
July 1991 Yves` parents go on holiday. Leaving him (19 years old) to guard their house. 1 august 19 hour 36 minutes: Yves´ parents house burns down. It was yves´ fault. And yet it was the best thing that happened to him till 2002. If you want to know why, come to our session. This interactive talk will show you why a crisis is a good thing. We make the link to agile transitions and how coaches can use a crisis. Why do people change? Do we consider their interests when making a change?
|Presenter(s):||Yves Hanoulle , Robin Dymond|
|Day and Time:||Wednesday, 11 August 2010, 13:30 - 15:00|
Come to a Dojo for Coaches! Take part in a unique interactive session that builds on the popular Dojo format used by agile developers. Instead of coding problems, we'll be exploring typical challenges faced by an Agile Coach. You get to offer your own counter-moves and also hear how other experienced coaches would tackle the same problem. What you'll see is more that one way to approach coaching that reflects the personal style of each agile coach and their reaction to a given context.
|Day and Time:||Wednesday, 11 August 2010, 15:30 - 17:00|
In an Agile workplace it certainly seems that extroverts have the run of the roost. It’s loud. It’s interaction-intensive. It’s focused on rapid results. The introverts on your team can end up feeling excluded, overlooked, or simply misunderstood. What’s a coach to do? This session explores how knowledge of Myers-Briggs personality types can help you decipher the interactions & friction within your team. Building on Jennifer Kahnweiler’s Four Ps we’ll delve into ways to bring out the inherent leadership potential of the introverted agilista to make their voices heard.
|Day and Time:||Thursday, 12 August 2010, 09:00 - 10:30|
At salesforce.com the ScrumMaster role is filled by Development Managers, QA Managers, Program Managers, and individual contributors. Because of these dual roles and differences in background, it is common for people to be confused about the expectations of a ScrumMaster. To increase ScrumMaster effectiveness and help the organization distinguish great ScrumMasters from good ScrumMasters, salesforce.com developed a ScrumMaster competency model. In this session we’ll present the competencies, discuss how they were created, and how they are used.
|Presenter(s):||Eric Babinet , Alida Cheung|
|Day and Time:||Thursday, 12 August 2010, 11:00 - 12:00|
|Supporting Materials:||Download Presentation
Have you ever had clients who “just don’t get it”, who are unwilling to change, and with whom you become frustrated over their inability to embrace Agile practices? Do you find your advice is ignored or altered so significantly that the end result no longer seems to represent the foundational Agile values and principles? In this session you’ll discover a set of beliefs, attitudes and behaviors that are designed to help Agile coaches remain grounded in their convictions while also being curious, empathetic and adaptive to their client’s toughest circumstances.
|Presenter(s):||David Spann , Gil Broza|
|Day and Time:||Thursday, 12 August 2010, 15:30 - 17:00|
Your Logo Here!
Producer: Gil Broza