I was sitting in my Operations Management class yesterday, and we were discussing statistical quality concepts such as the Six Sigma movement which the business world has been obsessed with for the last several years. As we were going through the concepts and the statistical calculations, I realized that the same calculations could demonstrate the value of some key ideas in the agile software movement, such as team size and the value of pair programming.
I have had occasion in the past few years to participate in several different teams that were cutting their teeth on agile and Scrum for the first time. One thing that always seems to trip people up when they are first learning about agile is the concept of a “Story Point”. In this article I’m going to attempt to add some clarity to what story points are, what they aren’t, and how they should be used in agile project.
I’ve been hearing a lot lately about how HTML5 is going to kill Silverlight. I hear that Microsoft has admitted that it is going with HTML5 in favor of Silverlight. And I hear that Silverlight is a doomed technology.
Here’s the problem: this is all untrue. Microsoft has not said anything of the sort, and is in fact investing quite a bit of resources in advancing the technology. Secondly, the road to HTML5 is far from smooth.
In this post I hope to examine the current state of HTML5 and Silverlight, the facts around Microsoft’s position with both of them, and offer some opinions on where things are going.