Category : Conférences

Le 5 meilleures façons d’améliorer son code

Pour ceux qui ont manqué cette présentation à l’Agile Tour, voici votre chance.

Les 29 et 30 novembre auront lieu les Tech•Days à Montréal. Éric de Carufel y présentera les 5 meilleures façons d’améliorer son code. Le but de cette présentation est de vous aider à améliorer le vrai code de production.

Soyez-y!
https://payment.techdays.ca/fr/venue

Pyxis à la JiQ

Le mercredi 2 novembre aura lieu la Journée de l’informatique du Québec (JiQ). Jean-René Rousseau y sera présent à titre de conférencier. Le sujet de sa présentation : « Transition Agile : Démarrer du bon pied ». Au cours des dernières années, Jean-René a participé à de nombreux projets Agiles et démarrages de transitions Agiles. De cette expérience, des pièges à éviter et des trucs ont émergé. Il partagera son expérience avec les membres de l’auditoire afin de les aider dans leur préparation à l’Agilité. Un grand nombre d’organisations ont des initiatives Agiles en cours, mais peu ont de véritables projets de transition Agile. Cette conférence les aidera à mettre en place une telle initiative.

Soyez-y!

JavaScript TDD par l’exemple

Je propose d’animer une séance de type atelier pendant laquelle les participants seront invités à programmer un jeu en JavaScript à l’aide de la technique du développement piloté par les tests (TDD). La particularité de cette séance sur le TDD vient de la combinaison du TDD et de JavaScript. En effet, même si le TDD se propage assez bien dans les équipes de développement, de nombreuses équipes cessent d’utiliser cette technique au moment où elles écrivent du code JavaScript.

Continue Reading

Pyxis à l’Agile Tour Montréal

Pyxis est partenaire de l’Agile Tour, et nous avons hâte de vous voir samedi. Passez nous voir dans la section des exposants, c’est avec plaisir que nous discuterons avec vous.

Ne manquez pas les conférences de nos Pyxissiens :

Au plaisir de vous y voir!

Transition Agile : démarrer du bon pied

Partout au Québec, les projets réalisés à l’aide de Scrum ou de tout autre cadre méthodologique Agile se multiplient. Certaines organisations sont en mode exploratoire alors que d’autres soutiennent de véritables initiatives de changement organisationnel en s’appuyant sur les principes et valeurs de l’Agilité. Les approches de développement Agiles sont définitivement parmi les idées qui ont fait des pas de géant au cours des dernières années.

Continue Reading

Top 5 des meilleures façons d’améliorer votre code

“Think once read many.” Arrêtez de redécouvrir ce que vous avez déjà trouvé. Durant cette présentation, Éric présente 5 façons économiques et efficaces de remanier votre code pour en améliorer la clarté. Vous devez prendre le temps de rendre votre code lisible une seule fois pour éviter que les autres y consacre du temps à nouveau.

Agile isn’t easy

Anybody who says otherwise is probably trying to sell you something

I’m spending the whole week here in Salt Lake City; attending the Agile 2011 Conference.

Earlier this week, Agile veterans Ron Jeffries and Chet Hendrickson held a session on what they thought they got right and what they thought they got wrong over the last decade.

I’m taking the liberty today to cherry-pick and to comment on two of Chet and Ron’s assessments regarding the things that did not go so well since 2001.

Dogmatism

Yes, there is still a fair amount of Agile practitioners around who will religiously apply each and every principles of the Scrum Guide without having a deep understanding of what it really means, nor will they prove to have real-life experience from the field deploying Agile values and principles.

New people embracing Agility seem to frequently fall into that trap; coaching others at learning Agility like following a recipe cookbook.

Moreover, some experienced Agile practitioners clearly never came out of this paradigm. Hiding themselves behind dogmatism and religious behavior brings fear, ignorance, and inexperience to people willing to get the best out of Agility.

Besides material available on the web, from trainings, to books and the likes, I do believe a good Agile coach must be able to clearly demonstrate to his partners (usually called customers) the following top 5 core competencies;

  • Proven management experience at navigating inside complex organizational cultures, systems and politics
  • Exceptional listening skills
  • Ability to think outside the box; Agility being one box
  • Proven track record in having positively coached people on Agility
  • A genuine dedication towards delighting customers (I do recommend the following Agile 2011 conference blog post by my colleague Martin Proulx)

Bottom line, being dogmatic and following step-by-step guidelines can be comfortable for many reasons. One of them can be the silver bullet syndrome that solves every possible issues faced by an organization in one monolithic state of mind and rigid framework.

I do personally think serious coaches needs to be fully inclined at mastering the above top 5 competencies if they really want their partners to be not only satisfied, but totally delighted!

Agile is not the answer to everything

Taking a step back and looking at why organizations are moving towards Agile, we can observe a heavy trend emerging from Agile practices on the field.

In an attempt to achieve all the benefits promised by Agility, some ‘agilists’ have started to accommodate or to modify quite substantially the Agile framework.

Out of the many reasons why one would be inclined to do so, there is one particular frightening motivation that caught my attention.

Let’s turn that toaster into a dishwasher… both are kitchen appliances aren’t they?

Applying Agile values and principles inside an organization is a challenge by itself. It requires a lot of skills, efforts and commitments from all parties involved. Most of the times, the Agile adoption cycle will expose many caveats and pitfalls for which the framework has not been designed to address at all.

In such circumstances, we do see Agile coaches, scrum masters, trainers and product owners distorting their practices so they can extend and reach out areas of the organization for which Agility is simply not the best answer (a toaster is a toaster).

If you’re really into turning your partners into Agile organizations focused on totally delighting their customers, you may consider the followings:

  • Agile’s framework doesn’t answer all your needs for doing so
  • Instead of turning Agile into something it isn’t, ask for help and complement with other approaches based on your needs
  • Using traditional management approaches and tools is not a sin. If it fits the purpose, why reinvent something new for that is the same things?

A good example on expanding your mindset by complementing your Agile practices with better-suited approaches is covered in my colleague’s most recent post from the Agile 2011 Conference.

In his blog entry, Martin comments on an inspiring presentation by Steve Denning on Making the Entire Organization Agile. I do recommend the read!

Making the entire organization Agile

At the 2011 Agile Conference, I had the opportunity to attend Stephen Denning‘s session yesterday on Making The Entire Organization Agile and I was wow’d.

Before getting into the details of the presentation, I want to highlight that Steve is not an Agilist – and that’s a good thing. He is the author of many award-winning books (including The Leader’s Guide to Radical Management: Reinventing the Workplace for the 21st Century). Although the main topic covered during the presentation really didn’t have anything to do with Agile per se, it was a very powerful backdrop for coaches attempting the make any organization Agile. Steve has also published a short video that explains his concept.

Now, back to the presentation. [Note that Steve was kind enough to make his slides available to everyone.]

Steve’s presentation began with a simple question “Why do managers act the way they do?“, after all “These are highly intelligent, educated people!“, he said. He then followed by asking a powerful question: “Why did management systematically kill all the creative things in organizations?” To support his point, he provided relevant examples such as: knowledge management, lean manufacturing, innovation, marketing, leadership storytelling, and even Agile and Scrum!

See the connection with Agile transitions now?

The core of his presentation (and of his most recent book) is that “Traditional management rests on five interlocking principles”:

  1. The purpose of a firm is to produce outputs that make money - What is produced is much less of a concern than making money. Key point here is that traditional organizations strictly focus on generating money with little (or no) concern for anything that doesn’t generate money for the shareholders.
  2. Managers act as controllers of individuals – Traditional organizations need conformity and to get conformity, they need compliance. Having managers control their employees is the preferred method used within those organizations.
  3. Work is coordinated by hierarchy and bureaucracy – Historically, it was important to get standardization and compliance. As such, traditional organizations have promoted people who were good at ensuring the work of others was being done in accordance to the plans. The hierarchical structure supported by bureaucracy were great ways to ensure standardization, and hence to generate more money. In such organizations, planning, monitoring and reporting were critical activities.
  4. “The main thing is efficiency” – Since the most important thing the organization were focusing on was to make money, creating efficiencies became a critical activity in the system. Efficiency forces the organizations to look inside as opposed to focusing on the outside (the customers).
  5. Communicate by directives – The traditional model assumes that people aren’t able to determine the best way to do their work and that they need to be told what to do and how to do it. It also creates a dominating relationship where the one giving the order has more power and authority than the one receiving the order.
Image by Steve Denning

Based on an in-depth research from Deloitte (Deloitte’s Center for the Edge: The Shift Index), Steve presented some alarming statistics:

  • The rate of return on assets has fallen by 75% since 1965
  • The life expectancy of Fortune 500 firms down to 15 years, and is heading towards 5 years
  • Only 1 in 5 workers fully engaged

Based on such statistics, he claims that “Management is broken” (and I would agree) and as a consequence “We have to manage differently!” He proposes 5 fundamental shifts that organizations will be required to make.

  1. New goal for the organization -> delight the customers (from outputs to outcomes)
  2. New role for managers -> from controller to enabler
  3. New coordination mechanisms -> dynamic linking
  4. Shift from value to values -> radical transparency and continuous improvement
  5. New way to communicate -> conversation (adult-to-adult conversations)

Image by Steve Denning

Once Steve presented the five big shifts required for organizational survival, he quickly highlighted which of the 5 shifts the Agile approach are actually impacting, and which areas our community still needs to alter in order to make the entire organization Agile.

Steve rightfully pointed out that the Agile community hasn’t done such a great job at “delighting customers” (not just making them satisfied but really delighting them) and in “altering the conversations”. On this point, that fact that many of the sessions at the 2011 Agile Conference were about coaching, mentoring, and collaboration is a good step in this direction.

Image by Steve Denning

The other interesting observation that Steve had with regards to Agile and the big shifts, is the serious conflict Agile initiatives face (since they only address 3 of the 5 shifts). He explained that Agile transformation are executed while 2 of the required shifts (from “making money for the shareholders” to “delighting customers” and from “top-down commands” to “from commands to conversations”) weren’t being addressed. This situation creates an environment where “organizations are at war with themselves“.

Any Agile coach who has attempted a large scale organizational transition can certainly agree with the statement. The 3 shifts (from controller to enabler, from bureaucracy to dynamic linking, and radical transparency) are the realm in which the Agile teams are successful. Unfortunately, they are rapidly confronted to the remaining 2 traditional perspectives.

This is the area I referred to as the Level 5 – Management Level Maturity and where many paradigms need to be altered (such as the role of the Agile manager in a self-organizing team, among other things).

Image by Steve Denning

In the end, it is very interesting to realize that the shifts that are currently taking place within the software development field are not unique and specific. Many (most?) of the various industries are currently going through such fundamental shifts and we can learn from their experience along with continually improving our approaches.

For those with a systemic perspective, Steve provided a simple comparison between traditional management and the suggested radical management.

Image by Steve Denning

The presentation was, by far, the best one I attended during this week… so far!