Voici les slides de ma présentation “Le Facilitateur, un rôle encore méconnu”, à l’Université du SI, organisée par Octo les 2 et 3 juillet.
L’audiocast devrait arriver dans quelques semaines.
I’ve been using C# .Net and WPF for a few months now on a projet with two other collegues from Valtech. I have to say that besides minor things, I now tend to prefer C# 3.5 language to Java. Linq is very powerful, extension methods are a must, lambda expressions are of great value…
However, I wouldn’t be so enthousiastic with WPF. It’s quite nice for simple things. But when you want to do medium complexity, it’s not so fun. Documentation is not good, performance is not good, Xaml can become more complex to read/write than C# (a non-xml based DSL would help).
Latest problem is the lack of free nice looking themes for WPF. I googled quite a lot and couldn’t find any. The ones I found are all very expensive. This is the last major weakness of .Net : the whole ecosystem is $-oriented.
In Agile, there’s a never ending debate between the “Keep track of your estimates, compare them to actuals, use the deviaiton to improve your future estimates” family and the “DON’T track actuals” family.
I’m feel much more in the “don’t do it” family, however, as a coach or Scrum Master, my approach is :
“Do what you feel is the right thing. If you choose to keep track of the actual vs original estimates, do it well. If after a few iterations, I realize that you don’t use this data to improve the estimates, I’ll remind you to at least try. Then you’ll tell me if this improved anything and is worth the time spent.”
60% of the teams decide not to track the actuals, 20% don’t track the actuals in a usable way, 19% don’t use actuals during the planning meeting, 1% find it useful.
What is your experience ?