SCRUM
-
I am afraid of superstar developers!
I now think that choosing roman numerals to represent parts in my series of posts about agile was a bad idea. It is not very scalable! This post, while related to agile, is not part of the series anyways. A few months ago, I read blog posting about agile development. I think it was called…
-
Being Agile… Part IV: Falsify me, please
My reference to Adam Savage in Part III was not just incidental. I think it is a very profound one, especially in software development. Adam Savage, in a later podcast (unfortunately, I was unable to find it) explains how the phrase “Failure is always an option” represent a fundamental fact about scientific enquiry. Unlike we…
-
Being Agile… Part III: Failure is always an option!*
So we are TDD. We proudly announce the number of unit tests and the percentage coverage as part of the scrum achievements. We make demands on minimum coverage (for a brief while when we had TFS, it was a check-in constraint). But, what do we actually gain by testing? Is there a law of diminishing…
-
Being Agile… Part II: Never stop changing
The point I stop reading an article about agile development is when it starts quoting from the agile manifesto. No, I do not have any qualms with the manifesto; I think it is an excellent minimalist document. However, when people starts to preach about it, I tune out. Same is the case when someone brings…
-
Being agile… Part I
The noise level about agile software development is deafeningly high these days. May be it has already peaked, which is probably a good thing. My real encounter with agile development in a production environment happened in 2003, when the company I am working for decided to adopt agile practices. We were playing with Fish philosophy…
The Salim Nair Band 