mai 2011Monthly :

Des Pyxissiens plus qu’Agiles

En plus d’être Agiles, nos Pyxissiens sont persévérants.

Le week-end dernier avait lieu l’événement Courez Ottawa. Quatre Pyxissiens prenaient part à cet événement et ont dépassé leurs limites.

Les Pyxissiens suivants ont couru le demi-marathon :
Line Fortier -  2:40:30
Tremeur Balbous – 1:55:19
Dominic Danis – 1:52:37

Jean-François Proulx effectuait le 10 km qu’il a réussi en 51:10.

Nous tenons à les féliciter. Nous sommes tous très fiers de leur accomplissement.
Bravo à nos coureurs!

Dojo@Pyxis

J’animerai un coding-dojo dans les locaux de Pyxis à Laval le mercredi 29 juin prochain de 5pm à 7pm. Et vous êtes tous les bienvenus !

Pour ne pas lutter avec un clavier et un IDE inconnus, apportez votre laptop avec votre environnement de développement préféré prêt à faire rouler des tests.

Pour cette première édition, je vous proposerai une formule que j’utilise lorsque j’aide un groupe à débuter avec les katas. Cela ressemble au déroulement ci dessous.

  1. 5′ introduction
  2. 15′ présentation du sujet
  3. 40′ travail libre en binôme
  4. 10′ pause
  5. 15′ présentation par un binôme
  6. 15′ perfection game par le public
  7. 10′ clôture

Habituellement on choisit le binôme qui présente pendant la pause.

A bientôt :)

Tribal Leadership – What level of leadership are you at?

There are many perspectives about what leadership is and how it should be done. Contrary to many recipe books on this topic, Tribal Leadership is a useful tool to assess the stage of your personal leadership style and evaluate the impact and the consequences of each stage. Although the backdrop of the book is that a higher leadership stage is better, the real value for me was as a tool to understand the culture and more importantly the people we deal with as part of Agile transitions.

While the majority of leaders in the work place are at stages 2 and 3, Tribal Leadership shares tools and insights to help individuals and organizations break through to the next evolutionary stages – which are usually much easier for a transition.

To help you get a gist of where you may stand as a leader and possibly help you determine at what level people you work with are, the authors provided on their web site a quick map (below).

As Agile coaches, we must often work with teams and their leaders. Understanding the behaviours of the leaders and their motivation is extremely useful. As such, the book presents a model allowing the transformation of Level 1 leaders to higher levels – granted most people start at level 2 or 3.

The book provides rich insights into human behaviour, group dynamics and individual motivation. Overall, it provides a good framework to understand people’s behaviors and with some clear thinking, can lead into actionable strategies to help support an agile transition.

Tribal Leadership is available in audio book [285 Mb zipped file] and in a traditional book format (Tribal Leadership: Leveraging Natural Groups to Build a Thriving Organization).

See Dave Logan’s presentation at TED.

ATTD avec Cucumber

L’exercice proposé ce mois-ci par @12meses12katas m’a donné envie cette fois d’utiliser Cucumber. J’avais dans l’idée d’apprendre à utiliser les Scenario Outline qui sont une alternative intéressante aux tableaux lorsqu’on veut donner plusieurs exemples d’utilisation d’une même formule. Comme je n’avais jamais fait cela, c’était une bonne occasion.

Pour ceux qui ne voient pas de quoi il s’agit, voici à quoi cela ressemble rapidement:

Je voulais rester dans des temps raisonnable pour l’enregistrement vidéo. Alors j’ai essayé de n’écrire que des tests Cucumber, pour gagner du temps. Je n’étais pas très confortable avec cette idée car j’anticipais que j’allais avoir envie d’écrire des tests plus unitaires en cours de route. Cela m’a incité à écouter les tests avec plus d’attention et à programmer par intention.

J’ai vraiment apprécié cet exercice et plus particulièrement:

  • Coder dans le train avec Vincent qui a mis à mal la première version de mon modèle,
  • La liste de tests capturée sous la forme de scénarios à venir,
  • le refactoring de la liste de test qui précise les intentions des tests quand vient le temps de les écrire. Cette activité est homogène à un travail sur un backlog pendant un planning d’itération.
J’ai fait le choix de mettre toutes les classes du domaine au même endroit. Il s’agissait au début de gagner du temps au chronomètre. Finalement cela s’est aussi avéré très pratique en cours d’exercice.

Pyxis is a proud partner of DevTeach 2011

DevTeach week in Montréal starts on Monday May 30th. Many Pyxissians are participating and animating dynamic sessions. Join us and learn more about Agile software development.

On Wednesday June 1st, Eric De Carufel will present ‘Comparing UI patterns, MVP, MVC and MVVM’. During this presentation, you will learn to identify presentation patterns and know when to use which.

Also on Wednesday June 1st, Eric De Carufel, Eric Lebel, and Mathieu Szablowski will host a dynamic panel on Agility: ‘How to develop differently?’

Finally, on June 2nd, Mathieu Szablowski and Vincent Tencé will present ‘Building functional software in 30 days’. Join us for this session where we will present a 5-day course that offers a unique intensive experience to software developers. An experience during which teams learn to use modern software engineering practices in order to develop increments of software by using Scrum and Visual Studio 2010.

If you are gonig to DevTeach, don’t miss our sessions.

Kata .Net

Que faites-vous le 15 juin prochain après le souper ? Vous êtes les bienvenus dans les locaux de Microsoft à Montréal à partir de 18:30 pour un kata. Amenez de quoi coder pour en tirer le maximum. Plus d’info sur le site de la communauté .Net de Montréal ici.

Cracking the Code for Standout Performance (part II)

image by shadaringtonAs Agile team coaches or organizational coaches, we aim to increase the teams’ performance in an attempt to deliver better results. We improve quality, help the team work more efficiently, and have fun while delivering increased business value. Interestingly, many of the observations presented in Great Business Teams: Cracking the Code for Standout Performance (this is the second part of the book review) are in line with the Agile values and principles. Here are some of the keys points to remember:

THE LEADERS

The leaders have an important role in developing high performance teams. Their actions and behaviors will be closely observed and people will modify their own behaviors based on those of their leaders. Guttman highlights some of the leader imperatives to achieve high performance.

Develop and drive the horizontal vision

An horizontal organization means moving to an organizaton in which everyone operates according to a clearly defined set of decision-making protocols, where people understand what they are accountable for and then own the results.

For an organization to raise its level of performance every team, on every level, must be a great team. That is to say, it must be aligned in five key areas:

  1. business strategy
  2. business deliverables coming from the strategy
  3. roles and responsibilities at individual and business unit or functional levels
  4. protocols, or ground rules, for decision making and conflict resolution (see a recent post on this topic)
  5. business/interpersonal relationships and interdependencies

Create the right mindset

  • Being candid from “wary, closed with hidden agendas” to “candid, open, relaxed, easy to speak your mind” – from “no tolerance for confrontation, conflicts suppressed” to “tensions surfaced, confronted, and resolved”
  • Accentuating accountability: putting equal emphasis on cross functional, peer-to-peer accountability, as well as peer-to-leader acountability.

Provide the right skills

Such as influencing, active listening, assertion, giving and receiving feedback, conflict management, decision making and leadership.

Keep the game and guard the rules

Everyone is clear about and committed to the business strategy and the operational goals that flow from it; undertsands his or her roles and responsibilities, and adheres to agreed-upon protocols, or ground rules for decisions making and for interpersonal behavior, especially those relating to conflict management.

Here’s how great teams make decisions:

  • Identify the decisions that need to be made
  • Identify decision subteams
  • Assign accountability
  • Set objectives and timelines
  • Select the decision making mode
  • Identify information sources
  • Determine the shelf life of the decision

Raise the bar

Keep challenging the status quo, revisit the targets and get the team involved in the process.

Be player centered

Leadership is in large part about power – about how it is exercised, shared, delegated, and used. High performance leaders seek to leverage power, not monopolize – to put it to use to drive up their team’s or organization’s performance. Putting the power in the hands of the teams members provides the right conditions to deliver maximum payoffs.

THE PLAYERS

The road to a great team begins with two nuclear elements of team reality: the leader and the team members. Consequently, team members must show four very obvious characteristics.

Think like a director

Keep their eye on overarching goals and the need to stay on top of their competition.

Put team first, function second

They are team members first and functional representatives second.

Embrace accountability

Slowly move from an individual accountability for their own results toward accountability toward the success of the entire organization.

Become comfortable with discomfort

People need to be or become comfortable with the changes required of them and their leader.

Building an outstanding team requires time and energy and is achievable once people agree to work together and pull in the same direction.

Expected behaviors of a self-organized team

Picture by Creative DonkeyFollowing a recent post on the topic of self-organization, I’m offering a few examples of how people react / should react when a team is self-organized.

 

Not self-organized Self-organized
  • Waits to be told what to do
  • Figures out what needs to be done
  • Is a victim of circumstances
  • Is responsible for his actions
  • Gossips about the motives
  • Seeks information to understand
  • Whines about the constraints
  • Attempts to operate within the constraints
  • Complains about his colleagues’ performance
  • Holds his colleagues accountable
  • Waits for rules to be defined
  • Defines the rules of operations
  • Reactive
  • Proactive

What other behaviours have you noticed?

Are you attending Microsoft Tech·Ed 2011 Conference?

Are you attending Microsoft Tech·Ed 2011 conference next week in beautiful Atlanta, Georgia? Please, do not missed this great session featuring Urban Turtle.

DEV271-INT Would You, Could You with TFS
Speaker: Richard Hundhausen
Thursday, May 19 | 8:30 AM – 9:45 AM | Room: B301
You’re considering Team Foundation Server, or perhaps you have already deployed it. You think you know what it is capable of, but do you? Microsoft built in many extensibility points which developers have used to build interesting and useful add-ons. These solutions include tools for managing requirements, product and sprint backlogs, work items, and software deployments. In this session, we discuss the partner ecosystem and demonstrate some of these products. See how to go beyond the out-of-the-box capabilities of Microsoft Visual Studio Team Foundation Server without custom development or going to other ALM platforms.

Furthermore, if you want to learn more about agility, here are two Birds-of-a-Feather (BOF) sessions that I will lead.

BOF09-DEV Is Scrum better for My Projects?
Discussion leader: Mario Cardinal
Wednesday, May 18 | 8:30 AM – 9:45 AM | Room: B209
Have you thought about, or are you using Scrum as a project management framework for agile software development? Jump start your learning or, if you’re a Scrum veteran, share what you have learned with fellow developers. Discuss the strengths and weaknesses, best practices, pitfalls, and more with in this session.

BOF17-DEV Agile Development: Can it Work for Everyone?
Discussion leader: Mario Cardinal and Phil Japikse
Thursday May 19 | 1:00 PM – 2:15 PM | Room: B209
As software developers, engineers, and craftsmen, we are focusing more and more on improving the code that we write, shifting from mere Delivery to Code Elegance. But our customers typically want the lowest cost, fastest to market option. Whether you are struggling with this issue or your team has found the perfect solution, join us to learn (and to share) how to manage this balance.

Do not hesitate to say hello, either at these sessions or simply by stopping at the Microsoft booth. I will hang around the Microsoft® Team Foundation Server 2010 demo station during the week.

Professionnal Scrum Foundations

Salut,

Nous (Vincent et moi) venons de donner deux sessions de la nouvelle formation PSF de scrum.org. Et je voulais partager avec vous ce que j’ai appris.

Les participants aiment les exercices de simulation pendant lesquels ils construisent du logiciel. J’ai donné des formations pendant lesquelles les participants construisent des prototypes papier. J’ai ressenti qu’ils préfèrent le logiciel. Cela améliore visiblement leur compréhension de comment utiliser Scrum dans leur projet. Cela augmente aussi la participation ; ils sont plus motivés à faire les exercices.

La mise en pratique d’un Scrum avec plusieurs équipes a beaucoup de valeur pour les participants. Pendant la PSF, la quatrième itération – pendant la seconde après-midi – impose aux participants de mettre en commun leur travail pour construire un site internet portail de leurs différents produits. Les échanges sur les différentes stratégies d’intégration sont beaucoup plus profonds que dans une formation théorique car les participants sont riches de cette mise en pratique.

La PSF est plus pertinente que la PSM pour les équipes qui débutent avec Scrum. J’ai donné beaucoup de PSM. Elle n’est pas faite pour les débutants. La PSM se concentre sur la compréhension de Scrum nécessaire à un Scrum Master. La PSF aborde tous les rôles de Scrum de façon plus équilibrée. Les Product Owner, Team et Scrum Master ainsi que toute personne qui est ou sera en contact avec une équipe Scrum trouveront dans la PSF ce dont ils ont besoin pour commencer: des réponses à leurs questions commençant par « comment ».