fvrier 2011Monthly :

Une belle réussite de Pyxis à CAE Santé

Dernièrement, CAE Santé annonçait le déploiement d’un système de gestion de centre d’entraînement médical avec le CHU Sainte-Justine.

Saviez-vous que Pyxis a collaboré à ce projet?
Pyxis est très fière des résultats de la mise en place de Scrum pour la réalisation de ce projet. Trois collaborateurs ont participé au projet. Marc-André Filion-Pilon occupait le rôle de Scrum Master, veillait à la gestion du projet et agissait à titre de facilitateur. Erik Lebel et Éric de Carufel ont agi à titre de développeurs .NET. Leur expérience a permis d’aider l’équipe dans l’application de pratiques Agiles d’ingénierie logicielle.

Ce que Scrum a permis à l’équipe de CAE Santé
L’emploi de la méthode Scrum pour la réalisation du projet a permis d’atténuer plusieurs risques, notamment en favorisant des cycles courts de développement (sprints de 2 semaines). Ceci a permis la révision en continu des priorités et l’adaptation du processus en fonction des succès et problèmes rencontrés. De plus, nous avons utilisé plusieurs artefacts simples et efficaces de Scrum pour assurer la visibilité relativement à l’avancement du projet (carnet de tâches du sprint et de la livraison, graphiques d’avancement, etc.).

Au niveau des besoins, il était essentiel de les clarifier et de les prioriser conjointement avec le client et les utilisateurs finaux. Le rapprochement avec les utilisateurs et une plus grande implication de leur part ont permis de gérer les attentes tout en assurant une grande transparence.

Défis techniques
Un des plus grands défis d’un projet de développement ayant un délai très court et un important périmètre est de ne pas couper dans la qualité (perçue ou interne). Or, ce risque a été pris en compte en favorisant des déploiements rapides, ce qui a permis de faire des tests et de recevoir du feed-back rapidement. De plus, l’utilisation de patrons et de cadres transversaux dans l’application permet du développement plus rapide, uniforme et fiable.

Bravo à toute l’équipe qui a réalisé ce beau projet!

Voir le système en action

#scrum release burndown chart

PM: I want to see increase the velocity of the Team
PO: I want to see decrease the remaining work

PM: If the velocity increases, the remaining work will decrease
PO: No, new work could be added at the same time

PM: I don’t like when the Team updates an item with a smaller effort estimation because the velocity could decrease
PO: I like when the Team updates an item with a smaller effort estimation because the remaining work decreases

PM: You don’t track the velocity in a velocity chart?
PO: No, I track the remaining work in a release burndown chart

Great news the project is over! Now let’s dismantle the team

Image by pgcCongratulations, you have finally delivered the project! The team you have carefully assembled over many months can now be dismantled and people can go back to their normal job. That’s the natural sequence in the project management world – project is kicked-off, team is assembled, team develops solution, team encounters delays, team tests solution, team moves solution into production, team hands-off solution to maintenance team, project team is dismantled, and life goes back to normal.

I wonder if the Green Bay Packers will do the same now that they have won SuperBowl XLV or maybe the San Fransisco Giants may want to start their 2011 season with new players after winning the 2010 World Series. At least the F.C. Internazionale Milano should want to give it a fresh start after winning the Serie A championship, wouldn’t you think?

Nobody would consider breaking up a highly performing sport team but when it comes to software development, it is common for organizations and departments to split up team members and start new with their next project.

From a purely practical perspective, breaking up a performing team makes no sense considering the time invested in:

  • carefully selecting and recruiting the right people with the right skill sets and the right attitude,
  • hiring external consultants with specific skills to complement the existing team,
  • getting the team to work together despite the team members’ personalities, work methods and obvious looming conflicts,
  • training people on the organizational culture and business activities,
  • establishing a leadership style that will work well with the team’s expectations,
  • eliminating the bad hires,
  • building relationships with the team members and between the project team members themselves,
  • etc.

Team members need time to become highly performing. Why not keep those team members together after the completion of their project and assign them together to the next project – even if the skill sets doesn’t seem to be perfect at first glance?

Unknown method ‘+’ for a Hash…

Last week, during a little bit of downtime, I continued working on the Hibou, a project started during Codapalooza One (read more). As I introduced the concept of Family and the relationship it has with the Child concept, I started getting a rather bizarre error :

Unknown method '+' for {:family => "Famille"}

At first I didn’t understand what was going on. After a bit of googling, I stumbled upon the solution: ‘:family’ was not translated in my french locale and formtastic doesn’t play nice with untranslated keys (which is awesome! better fail early than late)

Lesson Learned : Always translate your application when you know it’s going to be used in something else than English

Martin Proulx (Analytical-Mind) to celebrate International Coaching Week with free leadership coaching

 

In celebration of International Coaching Week, February 6–12, 2011, I am pleased to offer as I did last year, 10 hours of leadership coaching.

See what Louis had to say about his coaching experience:

I contacted Martin to help me transitioning to a senior role in the banking industry. He always used appropriate questions to bring my reflection to the right point, allowing me to accelerate thoughts I could possibly have but on a much longer period of time. Martin is smart, clear and articulate and efficiently interfere with a minimum number of words to help in the evolution of the reflection. Our coaching sessions helped me to improve my management skills, and I would definitively recommend him!

Coaching is partnering with clients in a thought-provoking and creative process that inspires them to maximize their personal and professional potential. Coaches work with clients in many areas, including business, career, finance, health and relationships.

Image by seier+seierIf you ever wondered if a coach can help you achieve better results faster, I invite you to send me an email (martin[at]analytical-mind[dot]com) with the following information:

  • Description of the professional objective you are hoping to achieve.
  • Why you think a leadership coach could help you achieve your objective?
  • Why YOU should be selected?

I am donating 10 x 1-hour sessions to one leader who wishes to achieve a specific goal. The sessions will take place over the phone (skype) at the rate of 1 session per week. You have until Wednesday, February 16th to submit your profile and I will select the coachee on February 19th. I am confident you will enjoy the experience.

International Coaching Week (ICW) is a weeklong global celebration of the coaching profession held each February since 1999. ICW is a designated time for coaches and clients to educate the general public about the value of working with a professional coach and to acknowledge the results and progress made through the coaching process. During this extended commemoration, coaches around the world offer a variety of activities and pro bono services in their local communities to share what coaching has the ability to do. For more information about ICW, visit www.coachingweek.org.

The International Coach Federation is the leading global organization for coaches, with more than 16,000 members in more than 90 countries, dedicated to advancing the coaching profession by setting high ethical standards, providing independent certification, and building a worldwide network of credentialed coaches. The ICF is the only organization that awards a global credential which is currently held by over 5,700 coaches worldwide. For more information about the ICF, please visit our Web site at www.coachfederation.org.

The Carrot Principle – Using Recognition to Increase Team Performance

Increasing teams and departmental performance – isn’t this why most organizations adopt the Agile principles?

Although there might be other reasons, many of the organizations we work with aim to increase their teams’ performance. I recently read The Carrot Principle – How the Best Managers Use Recognition to Engage Their People, Retain Talent, and Accelerate Performance – to see how recognition may help increase teams’ performance.

While many organizations still believe an above average salary is enough to keep people motivated, salary alone is not a good motivator. As Daniel Pink described, above an acceptable base salary, salary no longer is a good motivator. As such, managers often look for alternate ways to keep their team motivated.

The fact is that money is not as powerful a reward as many people think. While pay and bonuses must be competitive to attract and retain talented employees, small amounts of cash – anything short of $1,000 – will never make the best rewards because they are so easily forgotten – The Carrot Principle.

Recognition is deemed an important source of motivation and is usually used to maintain a low employee turnover rate and, increase employees’ performance and business results. Many organizations who adopt Agile practices recognize that it is increasingly difficult to attract top talents and in order to remain competitive, they should focus on increasing the performance of their existing work force.

Engaged employees demonstrate: innovation and creativity, take personal responsibility to make things happen, desire to contribute to the success of the company and team, have an emotional bond to the organization and its mission and vision.

U.S. Department of Labor statistics show the number one reason people leave organization is that they “don’t feel appreciated” – The Carrot Principle.

The book relies on surveys done by HealthStream Research and supported by data from Towers and Perrin. Below are some of the conclusions derived from the data:

  • Companies that effectively recognize excellence enjoy an ROE (return on equity) three times higher than the return experienced by firms that do not;
  • Companies that effectively recognize excellence enjoy an ROA (return on assets) three times higher than the return experienced by firms that do not;
  • Companies in the highest quartile of recognition of excellence report an operating margin of 6.6 percent, while those in the lowest quartile report 1 percent.

The authors point out that to be impactfull recognition should be combined with what they call the basic four areas of leadership:

  1. Goal Setting: defining the purpose of a task and tying it to a desirable end result
  2. Communication: discussing issues and sharing useful information with employees, welcoming open discussions
  3. Trust: keeping his word and owning up to his mistakes, maintaining a high ethic and positively contributing to the reputation of the organization
  4. Accountability: ensuring people deliver on their commitments.

Recognition can take many forms but whatever it is, the best reward is always personal and tailored to employees interests and lifestyle, given by a manager who cares enought to find out what motivates each individual - The Carrot Principle.

Finally, the book presents four levels of recognition:

  • Day-to-Day recognition: low-cost but high touch recognition such as Thank You notes to encourage small steps leading toward success
  • Above-and-Beyond recognition: provide a structured way to reward significant achievments that support the company’s core values
    • Bronze: to recognize on-time above and beyond related to core values
    • SIlver: reward on-going above and beyond behaviors for consistently demonstrating company’s values
    • Gold: behaviors that produce bottom-line results
  • Career recognition: recognize people on the anniversary of their hire
  • Celebration and events: celebrate successful completion of key projects or new product launches.

Comment est-il possible d’être agile avec TFS 2010 et Urban Turtle ce soir à Agile Québec

Face à la vague d’adoption de la méthode Scrum, Microsoft et l’équipe MSF nous livrent dans la version 2010 de Team Foundation Server un modèle intégrant Scrum.

Partons à la découverte du modèle MSF de processus agile. Cette présentation est une introduction à la méthode Scrum avec Visual Studio 2010. A la fin de la présentation, Urban Turtle, un plugiciel de gestion de projet Scrum qui s’intègre avec le modèle MSF sera présenté.

Ce soir à Agile Québec.

En savoir plus »

Pyxis recentre ses activités

En 10 ans d’existence, Pyxis a connu une forte croissance et est devenue le leader des approches Agiles dans la francophonie. Pour demeurer l’entreprise de référence et poursuivre sa recherche de l’excellence, Pyxis a procédé à une restructuration de ses activités la semaine dernière, ce qui a entraîné la suppression de quelques emplois.

Le double objectif de la restructuration est de réduire la structure opérationnelle et de recentrer Pyxis sur ses activités principales, soit l’accompagnement Agile, le développement logiciel à haute valeur ajoutée, la formation ainsi que le développement de produits dans le domaine de l’Agilité. Pyxis se positionne ainsi pour stimuler sa croissance au Canada et en Europe.

Cette restructuration a eu malheureusement pour conséquence la fin de l’emploi de quelques-uns de nos collègues, tous des contributeurs et collaborateurs de valeur. Cependant, elle n’affecte aucunement la qualité de nos services ni la collaboration avec nos clients.

————–

During its 10 years of existence, Pyxis has grown tremendously and has become the leader in Agile approaches in the francophony. In order to remain the company of reference and to continue its search of excellence, Pyxis proceeded with a restructuring of its activities last week, which resulted in employment termination of a few employees.

The double objective of this restructuring is to reduce the operational structure and to realign Pyxis on its main activities: Agile coaching, high added value software development, training as well as Agile product development. Pyxis is positioning itself to stimulate growth in Canada and Europe.

Unfortunately, this restructuring resulted in employment termination of a few of our colleagues, all contributors and collaborators of great value. However, it affects in no way the quality of our services nor the collaboration with our clients.