May 2009

Tuesday, May 19, 2009

. People

If anything I like

Scrum as a methodology is fast trying to get the most potential to computers. Understanding team not a bunch of people working together, but as a group of people who share a vision and motivation that unites them with special bonds. measurement metrics in Scrum is very team-oriented: The speed and burn-down are standard elements of this group. People are controlled by the same team as secondary. If each daily-scrum, is a person who does not progress, there are reasons and data for the other people help you or give you a hint, but the focus is on the computer. Alistair Cockburn
already said that building software is a cooperative game
that there is no play without equipment, or at least no satisfactory game. Lean tells us about the quality of conceptual integrity , you notice that product quality to bring out the integrity of the computer user. Now I ask myself how to make metrics to evaluate the performance of people ... why is it necessary in an agile environment? People who do not "work" will be quickly detected by the teams and do not want them. Is there a better metric than that?
If personal metrics depend on the estimated ratios of fulfilling their tasks, ... So is it possible to form a team with a common motivation? What we do not tightening too much? I guess it must be a balance, but I certainly would ma weight on the computer. Nobody builds software alone.
Anyway, more questions to Agile-Spain
;)